SSWConsulting / SSWConsulting/SSW.Rules
✨ Update Markdown Compatibility for TinaCMS Migration
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 26
- Forks
- 17
- Avg merge
- 14h 39m
- Merged PRs (30d)
- 2
Description
Requested by: @PothieuG via YakShaver.ai 🦬
cc: @Aibono1225, @PothieuG, @uly1, @Marxoz, @Freego1783
Hi Team!
🟥 Watch the video (1 min 23 sec)
Url from screen share: https://chatgpt.com/g/g-cOxvRnEzl-ssw-rules-writer/68f0b1df-f938-8330-abaa-ee275939afbc
Pain
Update the SSW rules writer to ensure the markdown it generates is compatible with the new TinaCMS migration standards.
Acceptance Criteria
- The SSW rules writer should generate markdown that is fully compatible with TinaCMS.
- All existing markdown generated by the SSW rules writer should be reviewed and updated to meet the new standards.
- Ensure that the integration with TinaCMS is seamless and does not break existing functionalities.
Screenshot
Figure: Old markdown format incompatible with TinaCMS migration
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 by locating the SSW rules writer and reviewing the linked video, screenshot, and existing generated markdown. Compare the output with the new TinaCMS migration standards, then verify that all existing markdown is compatible without breaking current functionality; the issue does not identify specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown, nextjs, typescript
- Domain
- content, documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100