decaporg / decaporg/decap-cms

Add 'Singles' type alongside 'Collections'

Open
#535 13 comments 29 reactions 0 assignees View on GitHub
area: configuration area: ui/collection kind: discussion kind: feature pinned
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.

![screen shot 2017-08-16 at 5 19 00 pm](https://user-images.githubusercontent.com/1312538/29390721-0a647fa4-82a7-11e7-88b4-7aa39e369d88.png)

Contributor guide

Open the contributing 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.