31 Comments

  1. Coen Jacobs

    I wonder how far my daydreaming about BackPress was from reality. :)

    Report

  2. Ryan Hellyer

    I hope this comes to fruition. I’d love to have a lean mean core to build from.

    Report

  3. Marko Heijnen

    I did asked already myself if I could get commit access to it due to the fact that GlotPress needs changes badly. It’s a shame that the people who care about BackPress has almost nothing to say or do something about it.

    Report

  4. gregattoolstack

    It would be nice if they made their announcement in a public forum instead of a closed Facebook group :(

    Report

  5. Vann Digital Networks

    From what I read on BackPress, I hope it happens…

    Report

  6. Pete

    Whilst back press is a great idea. This makes no sense as a standalone project. Really core itself should look to back press itself.
    Wp core should choose a release (say 4.6) and as part of that release make itself properly modular and stick to being modular for all future releases.

    Report

    • guavaworks

      That won’t happen.. so we are looking at creating a solution that lives INLINE with WP development, but a little more modularized, taking what the good is from WP and removing all unnecessary. I think keeping it inline with WP development is going to be crucial for it to stay alive.

      Report

  7. Jeff Pederson

    Awesome project! I know it’s a big undertaking but once it’s updated it will be a great value.

    Report

  8. Matt

    It would probably be better to start from scratch, it’s not even close to up to date with current WP code it was meant to emulate.

    Report

    • guavaworks

      I think the takeaway from today is to decide what it is the dev community wants out of WP, and see if feature plugins are the way to go, or if there is some validity in building out this system (whatever it may be called) as what we hope can be re-integrated into core at some point. Whether that means taking backwards compatibility into account or not that has yet to be seen. The discussion will continue next week, same day, 1 hour later :) And we learned our G Hangout lesson.

      Report

      • Matt

        It’s a fun experiment regardless, especially if people don’t think of it as Official WordPress Policy or Future (which it isn’t).

        Report

      • guavaworks

        As long as you aren’t offended, then an experiment it is. One thing to consider is that 23%+ of the web isn’t the target demographic to be using something like this. It is the 1% of WP Developers those that want to build something and are facing limitations, even if it’s just the “one size fits all” admin. Instead of having them turn to Laravel, or another framework, why not use WP since they love it, but have it a bit more slim

        Report

      • Ryan (@modemlooper)

        +1

        Report

      • nekojira

        I realistically believe that a large % of that 23% of the web means also a large bulk of orphaned websites who probably still run WP 2.8 or something. The 1% Roy mentions is likely where the best WordPress can bring is. This 1% needs love because it’s where one can make a good argument in how WordPress can be a very decent platform.

        In the Hangout yesterday it was mentioned an important thing: it’s difficult to give contributions to core when it’s one single, fat application, not really OOP. It’s hard to tell what does what. It scares away people, especially newcomers, who might want otherwise to contribute and improve WordPress and instead go elsewhere. I remember Matt mentioning once that he would like too that new generations liked PHP a bit more than the older one; well current status of things certainly not helping.

        I think it’s very hard to see it happening, but I also think everyone would benefit from modularizing WordPress. BackPress, aside of the name and its past history, could be an event dispatcher library where one can attach the modules needed (the wp-admin is a module). The WordPress.org distribution would be just a packaged application that includes the modules that make WordPress as we know it today. However this would allow developers to repackage WordPress with their chosen modules or alternative modules. This can make each module more maintanable and rewritten, introduce dependencies between modules, use composer and so on.

        Report

      • Joey Kudish

        @nekojira the 23% (actually 24.1% as of this month) of sites is calculated by W3Techs using the top 10 million websites to avoid dead/spam/outdated sites.

        see http://w3techs.com/technologies/history_overview/content_management/all and http://w3techs.com/technologies for more details

        Report

  9. guavaworks

    @nekojira – I agree, I think in an ideal world if there is a need to build this experimental project, it would be 100% modular. Where you can choose to even initiate plugins at all. Bare Bones WP would maybe look like a collection of objects / classes that handle database, wrapped with WP common language (creating / getting a post type)

    Report

    • David Husnian

      I agree. Very much like you and I and others were saying in our AWP discussion of WordPress++.

      A collection of classes that can be glued together as needed but with one (or more) common ones already done.

      Report

  10. guavaworks

    If you want to Join in on the slack channel to discuss and be part of future hangouts join the #backpress channel (which may be renamed) on https://advancedwp.slack.com

    Report

  11. Ross Wintle

    I find this so baffling. For me the main positive of WordPress is the UI: it’s simple, well-known, well-made, easy to extend.

    The main downside of WordPress is the back-end: it’s SO limited in terms of the data model. You can’t relate objects properly. You can’t add meta to taxonomies. I hit the limits of it so often.

    Why would you remove all the WordPress goodness and leave yourself a highly-restricted framework?

    If you’re going to code yourself a front-end, why wouldn’t you just use Laravel or Ruby on Rails to build yourself a much more flexible and easier-to-customise back-end for it rather than have to bully WordPress’s puny data model and API’s into doing what you need it to?

    Report

    • guavaworks

      BackPress or the project as it is evolving, isn’t “lets get rid of the UI” its “lets rethink how WP is coded” So i agree, lots of the backend internals are not GREAT, but that is what we are trying to address… IF there is a need to create a sister project that addresses these, or if they can be made into feature plugins.

      Report

Comments are closed.

%d bloggers like this: