nextcloud / nextcloud/cookbook

Use the same Markdown parser as other NC apps

Open
#991 14 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug Frontend javascript
Dominant language
HTML
Stars
641
Forks
113
Avg merge
21h 31m
Merged PRs (30d)
26

Description

The currently used markdown core v-markdown-editor seems to no longer be maintained. We should switch to another markdown solution.

At best we would use a compatible code with other NC apps to have the same flavor.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue identifies v-markdown-editor as the current Markdown core but does not name files, tests, or a replacement. First compare Markdown implementations in other Nextcloud apps and determine which compatible parser provides the same flavor; done means Cookbook uses that shared solution without losing current rendering behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
markdown
Domain
frontend
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.