nextcloud / nextcloud/collectives
Folder structure that turns `Page.md` into `Page/Readme.md` is confusing
Open
Nobody has claimed this yet.
design call
discuss
enhancement
prio::2
ui/ux
- Dominant language
- JavaScript
- Stars
- 195
- Forks
- 51
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 48
Description
In GitLab by @blacktav on Jul 10, 2021, 23:14
Creating a sub-document for an existing document converts the document to become a Collective with contents of the original document becoming a Readme.md in the new collective. This creates some strange behavior
- If the original document had a link from another document, the link continues to work
- but now creating a cross-link to the new Collective cannot be done i.e. Collectives cannot be linked to
- new Collectives created in this way cannot be reverted (versions)
- contents of a collective cannot be moved outside of its collective making problems above impossible to correct
- see also issue #174
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
No files, tests, or entry points are named in the issue. Start by reading issue #174 and the discussion here to establish the intended behavior for links, reverting a Collective, and moving its contents; done requires an agreed resolution for the Page.md-to-Page/Readme.md conversion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- content
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100