The reasons that I deprecated 15+ of my plugins are:
- It makes no sense in Kirby 3 that may come out this year.
- It will be integrated in Kirby 3.
- The plugin is not that good.
I guess some of you still use these plugins, so I just moved them here:
- GitHub - kirby-deprecated-plugins/kirby-panel-prevnext: A Kirby CMS plugin for panel siblings navigation
- GitHub - kirby-deprecated-plugins/kirby-snippetfield: Structure field with snippet instead of entry.
- GitHub - kirby-deprecated-plugins/kirby-serp: Kirby Serp SEO plugin for Kirby CMS
- GitHub - kirby-deprecated-plugins/kirby-plugin-manager: If you have a lot of plugins, it can be useful to groups them.
- GitHub - kirby-deprecated-plugins/kirby-blueprint-reader: Kirby Blueprint Reader for Kirby CMS
- GitHub - kirby-deprecated-plugins/kirby-logic-field: For custom panel stuff; Instead of building a field from scratch every time, use a snippet.
- GitHub - kirby-deprecated-plugins/kirby-headline-jump: Kirby Panel headline helper plugin for Kirby CMS
- GitHub - kirby-deprecated-plugins/kirby-hidden-fields: Hidden fields field for Kirby CMS Panel
- GitHub - kirby-deprecated-plugins/kirby-boiler-field: Boilerplate for Kirby form fields
- GitHub - kirby-deprecated-plugins/kirby-plugin-installer
- GitHub - kirby-deprecated-plugins/kirby-bricks: Group your files as modules - Plugin for Kirby CMS
- GitHub - kirby-deprecated-plugins/kirby-boiler-plugin: Plugin boilerplate for Kirby CMS
- GitHub - kirby-deprecated-plugins/kirby-hooks-debugger: Debug Kirby Panel hooks
- GitHub - kirby-deprecated-plugins/kirby-file-explorer: File explorer field for Kirby CMS
- GitHub - kirby-deprecated-plugins/previewer
- GitHub - kirby-deprecated-plugins/kirby-sideswitch
Most of the plugins has a MIT license so feel free to build something own with them.
The reasons behind the plugins I don’t deprecate are:
- They are easy to port to Kirby 3.
- They may get a major rewrite for Kirby 3.
In conclusion: Plugins that only make sense for Kirby 2 is now deprecated.