I’m just about to embark on developing a self hosted repository plugin for ClassicPress and will be using the F(X) Updater as the starting base.
In the first phase I’m going to add in a front end (display) functionality i.e. a listing of themes plus a listing of plugins with associated single view. I then hope to start hacking even further to add functionality to both the backend and frontend to enhance user experience.
Raising it here for the sole purpose of checking if (a) the core team or (b) any other member developer is already working on a similar project. Simply trying to minimise duplication and time wasted
There are a lot of security features we’ll need in the directory that mean the backend of this is unlikely to be directly relevant, but if we can get some insight into what’s required on the presentation side - especially around dependencies - that’d be really useful.
I know the directory is sloted for a later date and towards the release of CP V2 but, is there a roadmap somewhere that can give pointers (esp on security and design)?
If not, then can one be set up and be iterated upon as we gear towards the release goal please?
Lots of discussion around specific points in this subforum also.
Thanks for starting on this @anon63659058, the design is looking good so far! As Wade says, if you’d like to transfer this over to a repository under ClassicPress Research · GitHub, let me know and we’ll get that set up.
If you start with the WP code, it might be easier than writing from scratch. You can see the wp-content folder and all that is there.
Plugins that manage the data: