-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Comments
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). |
Is there no way to customize the admin UI in a nice way, own routes/views with own logic? |
Not yet @larsha, it's one of the big things after 0.4 is finally out that we want to get to! |
Here is an example of the first task (as middleware). |
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" |
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! |
+1 |
Just reiterating Max for those who have asked since he replied. This is still a high priority task for after 4 is released. |
any update here? |
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, |
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 |
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:
API related issues:
keystonejs/keystone#1705
keystonejs/keystone#1713
keystonejs/keystone#1714
The text was updated successfully, but these errors were encountered: