Merge WordPress 5.0 in the 1.0 version #149
Probably almost nothing, but it is better to merge often to keep the GIT history in sync otherwise when you want to merge later you get hard to resolve merge conflicts.
From the actual code POV, I will need to look at what is the recommended way to detect gutenberg and classic editor, and how 2019 handles it, and make sure that the relevant APIs will work for calmPress and report "classic" all the time. This is for theme and plugin compatibility.
Yes, it is going to be a CMS oriented and developer and site admin friendly, not a web based front page replacement aimed at people that miss the good old days of geocities :) Definitely not just a stripped down version of WordPress, but stripping down is a must as there is no way to move forward with the legacy baggage WordPress carries.…
On Thu, Oct 25, 2018 at 7:46 AM Στέφανος ***@***.***> wrote: In other words, calmPress is a stripped down version of WordPress? I thought this fork would follow a different direction than WordPress's. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#149 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABJnmtFmezbkqtVg9CFaCu65paroaEmcks5uoUINgaJpZM4XjGYR> .
…tructure but nothing more #149