nextcloud / nextcloud/text

Feature request: Add option for automatic heading numbering

Open
#9,193 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
JavaScript
Stars
659
Forks
133
Avg merge
1d 20h
Merged PRs (30d)
110

Description

Is your feature request related to a problem? Please describe.
When writing longer documentation, meeting minutes, or structured notes (especially when using Collectives), numbering sections is common practice to easily reference sections across the team. Currently, you have to number headings manually, which makes it quite tedious to keep everything consistent. Whenever an earlier chapter is inserted, deleted, or moved, all subsequent numbers (1.1, 1.2, etc.) have to be adjusted by hand.

Describe the solution you'd like
It would be awesome to have an option for automatic, hierarchical heading numbering (e.g. 1., 1.1, 1.1.1) in the editor and table of contents.

Describe alternatives you've considered
Currently, the only option is updating the numbers manually every time something changes, or skipping numbering altogether (which makes referencing specific sections in team discussions harder).

Additional context
Nextcloud Text is awesome. :)

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

Start by tracing the editor's heading handling and table-of-contents generation; the issue provides no file or test entry point. Done means an option produces hierarchical numbering such as 1., 1.1, and 1.1.1 consistently in both the editor and table of contents.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.