MacDownApp / MacDownApp/macdown
Separate themes project?
Open
Nobody has claimed this yet.
- Dominant language
- Rich Text Format
- Stars
- 9.8k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
Would it be worth extracting the themes into a separate project?
The thinking is that it would allow people who want to focus on themes to contribute there, instead of trying to understand the code base here and it could be leveraged by other Markdown projects, on other platforms.
Contributor guide
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
The issue proposes extracting themes into a separate project, but names no files, tests, or entry points. Define the project boundaries, how themes would be shared with MacDown and other Markdown projects, and the criteria for a complete extraction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100