Is Pagekit dead?

  • that's really disappointing... 2018 is almost over...

    I would love to see Pagekit progressing...

    Will we do a Fork? Or is there one already?

    Well I guess the most of us would like to see it progressing but unfortunately the ceo of yootheme thinks that pagekit is in a good shape.


    For own fork we need way more programming man / woman power as time that's would be awesome but I guess actually it is not enough of people around who can and would like to write code for a fork.


    Regards


    Fossy

  • My last five cents here:

    • Pagekit is a great product. I consider myself a technical literate and have worked with quite a few CMS in the past, be it Websitebaker (really tiny) to Wordpress and Joomla. All of these systems had their drawback, from being too simple (Websitebaker) to non-intuitive (such as Joomla and to some extent also October). What I like about Pagekit is that you install it, log in and it is more or less clear who you get the content in and have a very simple site up and running in a couple of minutes.
    • For the past 9 months, I have been quite active with Pagekit. What I missed is the wealth of Extensions and Themes in the Marketplace as other CMS have it. I initially started writing Extensions and now Themes. What I realized is that the respective documentation and examples on the Pakekit homepage are simply "not good enough" to get people attracted to writing Extensions. If you asked me for a wish list, I would like to have a proper documentation and sample Extensions that have to typical stuff in, such as (i) system and page attributes (incl. the php code to write them back to the database); (ii) examples how to access system-related variables, such as the root of Pagekit, its Storage folder, ...; (iii) a script that I can run with parameters, such as mercator/myplugin and it changes all the variables in the examples, so it becomes "my" plugin.
    • Themes are actually not that difficult - but you need to code in PHP, even if you just want to arrange your building blocks in a certain way. I would have appreciated if Pagekit would make this easier. It would actually be quite straight-forward to implement a template you can adequately parameterize (I will probably do that over the next couple of weeks). People could then focus on the CSS-related definitions, for which we also would need something that is easily customizable. Probably, this could be done with an Extension that is good enough for many people, who just want to get a personal homepage with limited customization. While this is not good enough for professional sites, it might be good enough for many users.
    • While writing Extensions and Theme is often about fun as opposed to making money, I would appreciate a "Payable Marketplace" as well as the option to have people buy a plugin from a self-hosted website, which then can pull updates from a self-hosted repository.

    It is all about simplicity and making it easier for people to develop would attract more programmers and agencies. If I had the time and all relevant skills (such as Vue and UIKit), I would probably fork Pagekit and start it from there. As I said at the beginning, designing a new CMS is a real art (or science) and you need the right skillset, which is hard to find on the market.

  • My last five cents here:

    • Pagekit is a great product. I consider myself a technical literate and have worked with quite a few CMS in the past, be it Websitebaker (really tiny) to Wordpress and Joomla. All of these systems had their drawback, from being too simple (Websitebaker) to non-intuitive (such as Joomla and to some extent also October). What I like about Pagekit is that you install it, log in and it is more or less clear who you get the content in and have a very simple site up and running in a couple of minutes.
    • For the past 9 months, I have been quite active with Pagekit. What I missed is the wealth of Extensions and Themes in the Marketplace as other CMS have it. I initially started writing Extensions and now Themes. What I realized is that the respective documentation and examples on the Pakekit homepage are simply "not good enough" to get people attracted to writing Extensions. If you asked me for a wish list, I would like to have a proper documentation and sample Extensions that have to typical stuff in, such as (i) system and page attributes (incl. the php code to write them back to the database); (ii) examples how to access system-related variables, such as the root of Pagekit, its Storage folder, ...; (iii) a script that I can run with parameters, such as mercator/myplugin and it changes all the variables in the examples, so it becomes "my" plugin.
    • Themes are actually not that difficult - but you need to code in PHP, even if you just want to arrange your building blocks in a certain way. I would have appreciated if Pagekit would make this easier. It would actually be quite straight-forward to implement a template you can adequately parameterize (I will probably do that over the next couple of weeks). People could then focus on the CSS-related definitions, for which we also would need something that is easily customizable. Probably, this could be done with an Extension that is good enough for many people, who just want to get a personal homepage with limited customization. While this is not good enough for professional sites, it might be good enough for many users.
    • While writing Extensions and Theme is often about fun as opposed to making money, I would appreciate a "Payable Marketplace" as well as the option to have people buy a plugin from a self-hosted website, which then can pull updates from a self-hosted repository.

    It is all about simplicity and making it easier for people to develop would attract more programmers and agencies. If I had the time and all relevant skills (such as Vue and UIKit), I would probably fork Pagekit and start it from there. As I said at the beginning, designing a new CMS is a real art (or science) and you need the right skillset, which is hard to find on the market.

    First of all, thanks for your contribution and feedback. From my point of view, the pagekit community should have a joint approach and communication towards YOOtheme. There are still a lot of people who like this CMS very much or have setup nice projects. Sad to see, that we are only waiting for nothing.


    SPQRInc Fosphatic Duke  

  • Is the community around Pagekit still alive?


    I was looking for a clean, fast and stylish CMS for a long time but nothing met my expectations - until I found Pagekit.


    It really impressed me but then I read an article by accident, saying that Pagekit is no longer supported. Then I found this community which seems to confirm the same.

    Are there still any guys working with this nice Pagekit? Still any fork ideas?


    I hope it‘s not the end, otherwise I have to keep searching for a similar system.

  • For devs maybe less interesting, but for end users, I can highly recommend Publii CMS. It's just as easy as pk and much faster. Ideal for smaller websites. I have created my company page with it and until very satisfied.


    Before i used pagekit over 2 years. Its a pity that it wasnt developed further but life goes on