SSWConsulting / SSWConsulting/SSW.Website
Tina - Store Content in a seperate repo
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 14
- Forks
- 10
- Avg merge
- 13h 51m
- Merged PRs (30d)
- 38
Description
This is now possible in Tina CMS 1.1.4
See https://tina.io/guides/tinacms/separate-content-repo/guide/
It might make sense to do this when switching to SSWs Tina Cloud account
Images are an issue - where do they go?
### Tasks
- [ ] Investigate if this is worth implementing
- [ ] Create new repo
- [ ] Implement
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 with the Tina CMS 1.1.4 separate-content-repository guide linked in the issue, then inspect the repository's current Tina content and image handling. Resolve whether moving content to a separate repository is worthwhile, where images should live, and define the new repository and implementation scope before coding; no files or tests are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, nextjs
- Domain
- content, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100