jmapio / jmapio/jmapio.github.io
(JMAP) [@!RFC8620] markup exposed
Open
Nobody has claimed this yet.
- Dominant language
- Liquid
- Stars
- 11
- Forks
- 29
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 7
Description
(JMAP) [@!RFC8620] and [@?RFC3501] links are displayed with exposed markup and do not link to anything on https://jmap.io/spec-mail.html
(maybe this is for https://github.com/jmapio/jmap/blob/bdb932e26c0d729cbb351acde090b4903e28252a/spec/mail/message.mdown I don't know)
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 inspecting the rendered links on jmap.io/spec-mail.html and compare them with the possible source file, spec/mail/message.mdown, mentioned in the issue. Trace how the RFC markup is processed, then verify that the exposed references render as working links on the page.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100