SSWConsulting / SSWConsulting/SSW.Rules
✨ TinaCMS - Create Twitter Embed Template Component
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 26
- Forks
- 17
- Avg merge
- 14h 39m
- Merged PRs (30d)
- 2
Description
CC: @bradystroud @adamcogan
Description
Develop a Twitter Embed component in TinaCMS that allows users to embed individual tweets directly into the site content. By adding this component, content creators can easily include Twitter content by providing a tweet URL or ID, which will be rendered in an embedded format on the front end.
Acceptance Criteria
-
Create a Twitter Embed component (recommend React-Tweet) in TinaCMS with the following field:
- Tweet URL/ID: Input field for entering the URL or ID of the tweet to be embedded.
-
Ensure the embedded tweet is responsive and matches the styling of the site, adapting to different screen sizes.
-
Validate that the component handles invalid URLs or IDs gracefully, providing a fallback message or error indication in TinaCMS if the tweet cannot be displayed.
-
Test the component on different pages and devices to ensure consistent display and functionality.
-
Document the Twitter Embed component’s usage, including instructions on how to obtain a Tweet URL or ID, in the project’s documentation.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the TinaCMS component entry point and review the recommended React-Tweet integration. The work is complete when the component accepts a Tweet URL or ID, renders responsively, handles invalid input with a fallback, works across pages and devices, and has usage documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, react, typescript
- Domain
- documentation, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100