Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Quanta Content Type Chooser #54

Open
4 tasks
tisto opened this issue Apr 22, 2022 · 1 comment
Open
4 tasks

Quanta Content Type Chooser #54

tisto opened this issue Apr 22, 2022 · 1 comment
Labels
04 type: enhancement making existing stuff better 05 type: question discussing

Comments

@tisto
Copy link
Sponsor Member

tisto commented Apr 22, 2022

Quanta introduces a nice content type chooser that especially comes handy when your site has lots of different content types. It highlights the most important content types:

Screenshot 2022-04-22 at 12 32 56

Of course there are a few decisions that we have to make before we can move on.

  • do we ship with Folder?
  • what are the two most important content types? Page and XXX?
  • are those two most important content types supposed to be configurable (e.g. via config.json or maybe even via control panel)?
  • is the number of highlighted content types supposed to be configurable?
@tisto tisto added 05 type: question discussing 04 type: enhancement making existing stuff better labels Apr 22, 2022
@djay
Copy link
Member

djay commented Mar 1, 2023

@tisto
Castle had this better than this very Plone way of doing things. Plone has always assumed

  • you always want to add one thing at a time
  • you always want to edit something directly after you add
  • you always are in the place where you want to create the content when you click "add"
  • you don't want to upload instead of edit

Instead castle let you create the content as many times as you need, lets you name it, all before you edit it, or you can upload the content (without having to learn to find the hidden upload control in "contents")

This also solves the problem caused by plones insistence on allowing editing before the object is created (plone/volto#769)

The castle version is ugly but the idea is sound.

Screen Shot 2019-07-22 at 2 22 33 pm

Screen Shot 2019-07-22 at 2 17 02 pm

Screen Shot 2019-07-22 at 2 23 05 pm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
04 type: enhancement making existing stuff better 05 type: question discussing
Projects
None yet
Development

No branches or pull requests

2 participants