WYSIWYG Editor
Open
Nobody has claimed this yet.
✨ enhancement
needs investigation
- Dominant language
- TypeScript
- Stars
- 2.4k
- Forks
- 333
- Avg merge
- 1h 2m
- Merged PRs (30d)
- 1
Description
During the internal onboardings, a lot of people asked about WYSIWYG Editor. Some ideas:
- Is there any other channel to update and note apart from updating GitHub, or using the Obsidian interface? Any consideration for channels that allow sporadic action, channels like browser plugin editor, etc.?
- Eg. stackedit.io is a editor that have a lot of features for writing and rendering markdown documents in a WYSIWYG way
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 names no files, tests, or entry points. Start by locating the current GitHub and Obsidian editing flows, then clarify which sporadic-editing channels and WYSIWYG Markdown features are in scope; done requires an agreed channel and feature scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown
- Domain
- content, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100