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

Plugin Architecture #1898

Closed
7 tasks
ericelliott opened this issue Dec 2, 2015 · 11 comments
Closed
7 tasks

Plugin Architecture #1898

ericelliott opened this issue Dec 2, 2015 · 11 comments

Comments

@ericelliott
Copy link
Contributor

It would be great if KeyStone users could do most of their custom development on a plugin architecture.

Plugin architectures provide several major advantages. One huge advantage is that new features can be developed as plugins, and we can provide a mechanism to toggle features on and off in production. Ideally, most new KeyStone development should be possible to do in plugins, rather than in the core.

Here are some plugin extensibility points worth consideration:

  • Adding middleware to or pre-built routes to the express stack
  • Adding custom field types
  • Adding pre-built models
  • Replacing some or all of the management UI for certain lists
  • Adding components to Lists in the Admin UI (probably in the sidebar but could sit around or in the form as well)
  • Adding custom views to the Admin UI
  • A more fleshed-out API will help with this.

API related issues:
keystonejs/keystone#1705
keystonejs/keystone#1713
keystonejs/keystone#1714

@stkrzysiak
Copy link

This sounds great, how do we get something like this approved and on the road map @JedWatson & others? I was actually a bit surprised to see that this doesn't exist yet for keystone(been a yr since I looked it over).

@larsha
Copy link

larsha commented Feb 3, 2016

Is there no way to customize the admin UI in a nice way, own routes/views with own logic?

@mxstbr
Copy link
Collaborator

mxstbr commented Apr 29, 2016

Not yet @larsha, it's one of the big things after 0.4 is finally out that we want to get to!

@SharadKumar
Copy link

Here is an example of the first task (as middleware).
https://github.com/ForestAdmin/keystone-demo

@JedWatson

@ghost
Copy link

ghost commented Apr 17, 2017

Is there any news on this? The admin interface refactoring has been out for a year now and I still can't find the new admin UI plugin architecture. All I see is a not very specific reference in the wiki which says: "Subsequent releases (...) Create a Plug-in architecture"

@henrypip
Copy link

henrypip commented Jun 14, 2017

Just echoing @Fogetti, it'd be great to know when a plugin architecture is being planned, right now editing the Keystone source code isn't something we're keen on doing, but we love Keystone so want to stay with it!

@pinussilvestrus
Copy link

+1

@Noviny
Copy link
Contributor

Noviny commented Sep 22, 2017

Just reiterating Max for those who have asked since he replied. This is still a high priority task for after 4 is released.

@zilveer
Copy link

zilveer commented Oct 6, 2017

any update here?

@PTZ2002
Copy link

PTZ2002 commented Nov 8, 2017

Hello,

I'm interested if the plugin system is build in the version 4.0.0-beta5 or if there is any method or way to develop custom plugins for keystone?

Best regards,
Tamas

@gautamsi
Copy link
Member

Keystone 4 is going in maintenance mode. Expect no major change. see #4913 for details.

There is initial discussion to have plugin/extension in v5 keystonejs/keystone-5#842, contribute there if you want Plugin architecture in v5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests