MacDownApp / MacDownApp/macdown
Consider supporting the CommonMark Spec
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
(Updating this so that people don't have to read the whole thread...)
http://commonmark.org/
I have already suggested this to Hoedown (https://github.com/hoedown/hoedown/issues/119), so if they implement this it will take care of your renderer, but I don't know if supporting this standard also requires changes to your editor/interface.
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
Read the CommonMark specification and the linked Hoedown issue first. Determine whether implementing support requires changes to the renderer, the editor, or the interface; completion would mean the relevant MacDown behavior conforms to the chosen CommonMark scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100