writefreely / writefreely/documentation
Document Link Parsing Limitations
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 18
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
Currently, and according to issue #80 on the writefreely repo, in the future, the post rendering function does not allow data URI images (by default).
That behavior isn't "standard," as much as I see a standard applying, and so it should be documented along with the rest of information about post/link rendering.
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 issue #80 in the writefreely repository and find the existing documentation about post and link rendering. Document that data URI images are not allowed by default; the work is done when this limitation appears alongside the other rendering behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100