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

Control panels #29

Open
8 of 14 tasks
robgietema opened this issue Apr 27, 2017 · 8 comments
Open
8 of 14 tasks

Control panels #29

robgietema opened this issue Apr 27, 2017 · 8 comments

Comments

@robgietema
Copy link
Member

robgietema commented Apr 27, 2017

Create all control panels. The rest api doesn't provide most of the calls for this yet.

  • Addons
  • Discussion
  • Theming (not needed for headless)
  • Syndication
  • TinyMCE (not needed for headless)
  • Contentrules
  • Content settings
  • Dexterity content types
  • Users and groups
  • HTML filtering
  • Errors
  • Maintainance
  • Configuration Registry
  • Resource Registry (not needed for headless)
@tisto
Copy link
Member

tisto commented Apr 27, 2017

True. Though, we have a registry endpoint that allows setting registry settings. Since all control panels are based on the registry now, the question is if we need specific endpoint or if providing a schema for the control panels is sufficient.

@robgietema
Copy link
Member Author

For most I think providing a schema would be enough. There are some custom ones though, like users for example.

@robgietema robgietema added this to the Future milestone Apr 27, 2017
@robgietema
Copy link
Member Author

All controlpanels using the registry are implemented. Missing controlpanels are:

  • Addons
  • Discussion
  • Theming (not needed for headless)
  • Syndication
  • TinyMCE (not needed for headless)
  • Contentrules
  • Content settings
  • Dexterity content types
  • Users and groups
  • HTML filtering
  • Errors
  • Maintainance
  • Configuration Registry
  • Resource Registry (not needed for headless)

@avoinea
Copy link
Member

avoinea commented Mar 19, 2020

Any work in progress on this? Especially Dexterity content types?

@tisto
Copy link
Member

tisto commented Mar 19, 2020

@avoinea not really. It is hard to find clients who are willing to pay for control panels. Therefore this is something we have to do via the community or via sprints IMHO. The Dexterity content types control panel is indeed a biggy and it would be great if we could find someone who wants to pick this up. I'd be more than happy to help with advice if needed.

@avoinea
Copy link
Member

avoinea commented Mar 19, 2020

@tisto Then I suppose I'm the right guy at the right place :).

I can take The Dexterity content types control panel

Where should I start? I suppose plone.restapi.

@tisto
Copy link
Member

tisto commented Mar 20, 2020

@avelino awesome! Yeah, I guess we need to create the rest api endpoints first, then move on to the frontend implementation. Do you want to create an issue on the plone.restapi issue tracker?

@avoinea
Copy link
Member

avoinea commented Mar 20, 2020

@tisto What about this one plone/plone.restapi#355

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Status: Backlog
Development

No branches or pull requests

10 participants