Add 'Singles' type alongside 'Collections'
- Dominant language
- JavaScript
- Stars
- 19.4k
- Forks
- 3.1k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 9
Description
Original idea as outlined by @erquhart
### Idea:
Allow for a 'Singles' content type, designed for one-off, often publicly-published pages such as 'About', 'Contact', etc. Anything that would not be appropriate as a repeatable object template in the way that 'folder' type Collections work in the CMS today.
This allows for the distinction in the 'Content' interface of these different content types. Collections allow for (+) buttons, Singles do not, as they are one-off. This is largely represented in the 'file' Collection type available in the CMS today.

Contributor guide
Research direction
Start by tracing the Content interface and examining how the existing 'file' Collection type is represented in the CMS. Determine where content types are defined and how the interface renders (+) buttons. Done means a distinct Singles type supports one-off pages and does not show collection creation controls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- content, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100