Geeklog Plugins: Current Status and Development Priorities #4
hostellerie
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Geeklog Plugins: Current Status and Development Priorities
I reviewed the main plugins available for Geeklog, including the public repositories from the Geeklog-Plugins organization and the plugins historically distributed with Geeklog.
The objective was to identify:
Main findings
The Geeklog ecosystem already covers many important needs:
The main issue is not the lack of features. It is the age and maintenance status of many plugins.
Several plugins were last updated before PHP 8 became widely used. Even when a plugin is listed as compatible with PHP 8.0, this does not guarantee compatibility with PHP 8.1 or PHP 8.3.
Each plugin therefore needs to be tested with:
E_ALLerror reporting;utf8mb4.Highest development priorities
The following plugins appear to provide the greatest value to the Geeklog community.
Critical
These plugins cover essential security, publishing, navigation, SEO, community and media-management features.
High priority
These plugins support modern publishing, privacy, engagement, analytics and content discovery.
Medium priority
These plugins remain useful, but they address more specific use cases.
Plugins that should probably be retired or replaced
Some plugins rely on obsolete technologies or external services that have changed significantly:
Bad Behavior 2 may also be less relevant when modern hosting protection, ModSecurity or a web application firewall is already available.
Duplicate or overlapping plugins
Before investing development time, the community should decide which plugin should become the preferred solution when several projects cover similar needs.
Examples include:
Maintaining one strong implementation may be more useful than maintaining several incomplete alternatives.
Recommended development process
A common validation standard should be applied to every plugin:
utf8mb4.E_ALL.Suggested roadmap
Phase 1: platform stability
Phase 2: modern publishing and SEO
Phase 3: community and engagement
Phase 4: specialist plugins
Community feedback
This inventory is intended as a starting point.
Feedback would be useful on the following questions:
The goal is to build a clearer, maintainable and documented plugin ecosystem around Geeklog 2.2.2.
Geeklog Plugin Inventory
This document summarizes the main Geeklog plugins identified in the community, the public repositories of the Geeklog-Plugins organization, and the plugins historically distributed with Geeklog.
Priority levels
Plugin summary
All reactions