More up to date plugin and theme compatibility - hopefully such code will check if 'blocks` are available bit we cannot do much to protect again poor plugin / theme code.That said, the benefits of fast-forwarding may well help us play catch up to WordPress to take advantage of: There are around 1400 files (PHP, CSS and JS) in src alone so reworking is no small task. I’m about 200 files in and have suspected further work while we discuss the subject. It seems clear that the CP community really like CP, but really have very little understanding of the work involved in some of the features suggestions / requests that are made - comments like “make CP PHP 8.1 compatible” are all well and good but the aspiration of that change and the work involved are not in the same conversation.Īs Viktor has said, I took WordPress develop and am doing a manual compare to current CP develop. I think the poll and thread so far are interesting. This also begs the question, who is willing to put in the time/work to help move ClassicPress forward and succeed?Ģ023 will be a great year for ClassicPress with your help! Matt has done some work forking WP’s develop branch, changing over 200 files, to see how hard it can be.Alvaro’s fork WP-CMS can be a good start, it removes Gutenberg code and is up-to-date.The big question is, how do we proceed with the fork? This also applies to tests, when we introduce certain changes WP tests may need to be changed so they can pass. We need to review WPCS and see if we want to stick with it or continue with our custom WPCS rules, which may need additional changes. Alvaro mentioned his fork uses WPCS and tests, and everything is working. Petitions widget needs to be rewritten to use GitHub data, so for now it can be left out.Documentation URLs should point to ClassicPress documentation if available.All API endpoints must use ClassicPress APIs as in v1.x.Privacy-oriented changes should be kept (anonymizing data CP sends to APIs).Security page, post ID column, and customizing login page banner can be left out.In addition, we need to figure out what changes were introduced by ClassicPress in v1.x that we would like to keep in the re-forked version. These are items off the top of my head, there are more so please share what you know. If I’m not mistaken, code_potent rewrote installation screen/steps, unless there’s something specific for CP, we can probably let that go and keep WP’s code.We also need to keep a list of any new changes that ClassicPress may introduce that deviate from WordPress core.Possibly automate replacement/rewriting of dockblocks as needed.Automate the replacement of WordPress with ClassicPress.Automate the replacement of static strings such as API endpoints in the code.For example, as suggested by Daniele, we can stop prefixing WordPress versions in docblocks with wp- and instead do that for CP versions.The re-fork gives us an opportunity to do certain things differently and improve the processes. We need to be our own community while leveraging WordPress core, we can’t let commercial interests controlling WordPress control ClassicPress.įor example, and this is my personal example, WEBP generation should be disabled by default. We have to make the right decisions for the ClassicPress community even if that means deviating from WordPress core at times. WordPress has shown a lack of care for the needs of the community more than once since Gutenberg was introduced. As the core team grows, we can always explore the possibility of splitting away from WP but at this point in time, it’s simply not feasible.īut, we’re also not going to be WordPress without Gutenberg. The only way to do that is to leverage all the work that’s done by WP contributors. With a small core team, we have to find ways to be more efficient, to get more done with less. There are simply not enough developers to make progress without backporting code from WP to move away from WP.Īn almost even split in the poll suggests the best option might be a hybrid one, find a compromise solution that will satisfy both sides. The goal of this discussion is to find a way forward.ĬlassicPress can’t be WordPress without Gutenberg, but it also can’t be its own CMS with a small core team at this time. The option to re-fork has 20 votes while continue-as-is has 18. Keeping this discussion on the forum, instead of Slack, ensures everyone can participate in the discussion without timezone limitations over the course of a few days/weeks. It’s limited to core contributors ( and will be kept private. This discussion will focus on the results of the poll and users’ feedback.
0 Comments
Leave a Reply. |