Pagekit has been on the market for more than a year now and we are still very happy with how it turned out. It was received well and thanks to you guys we were even able to bring home a CMS Critic Award last year. Now we need your help again for this year’s award nominations. Please vote for Pagekit in the following category:

• Best WordPress Alternative

All you need to do is go to the CMS Critic Award website and nominate Pagekit as your favorite CMS in the category above. It's also helpful to state the reasons why you chose Pagekit to be considered.

The deadline is August 27. Don't miss it, every vote counts and is important to us!

Many thanks to you all!

To strengthen our community and also to meet some of you face to face, we organized the first Pagekit meet-up a while back.

With Pagekit 1.0 out in the wild for a few months, and the community steadily growing and becoming stronger, we were thrilled when some of you had asked us about the possibility of a meet-up. After gathering interest on Twitter and other channels, we were happy to welcome some of you to our offices in Hamburg.

In May part of our team travelled to beautiful Barcelona and attended the JandBeyond conference. Luckily, we even had the chance to present Pagekit to the audience. Our developers Malte and Florian prepared the talk What's cool about Pagekit, which was targeted both at people who had never heard about our CMS, but also at those who are familiar and interested in developing with Pagekit.

The conference was a lot of fun. We met old friends, made new ones and had nice conversations both in the sunshine and later at the bar. Of course, the talk has been recorded and is now available on YouTube.

Today four new themes find their way into the Pagekit Marketplace. To those who have been using YOOtheme products in the past, these might seem familiar. To demonstrate the wide range of possibilities that Pagekit offers to theme developers, we have decided to create themes based on Avion, Avanti, Aurora and Dolce Vita for Pagekit!

About a month ago we released the first stable version of Pagekit. After four years of development, this was an incredibly exciting day for us. Pagekit got a lot of attention on social media, like Twitter and Facebook, and a number of magazines published articles on the release. So, after collecting some data and working continually on further improvements, it is now time for the next roundup.

We are incredibly happy to release Pagekit 1.0 today. It was a tremendous undertaking to get Pagekit to this point and we are beyond excited to have finally made it.

Since our completely rewritten Beta release last summer, we've improved Pagekit piece by piece and added the last missing features. Many users, web designers and developers have already taken the chance to try and use Pagekit during the beta phase. 2.400+ Stargazers on Github, 450+ users in our community chat and 20.000+ registered users at pagekit.com indicate great interest and we can see a lot of active engagement on our open source channels. Thank you, community!

Say hello to the new Pagekit release 0.11.0. It comes with improved semantic markup and an even more simplified installer. These are the main changes among many other, making Pagekit increasingly suitable for your next website project.

With today’s Pagekit release we are getting very close to Pagekit 1.0. It brings great improvements to the user experience in the admin area, as well as better performance of the Pagekit installer and marketplace. All Symfony components have been updated to Symfony 3. In addition, there are a lot of bugfixes and improvements in this release. Find the list of all changes in the changelog.

Pagekit comes with a powerful user system that you can use in a flexible way. In this post, we will give you a quick overview of everything you need to know.

You can enable public user registration or create accounts from the admin interface. Either way, it is important to understand the concepts of permissions and roles. As a developer, you can also work with user accounts inside the code of your extension.

Today’s Pagekit release improves session handling in the admin area, so that you never lose your work again. We have also improved the debug toolbar and included various smaller fixes. Find the list of all changes in the changelog.

To build the Pagekit admin area, we explored the vast landscape of JavaScript frameworks. A rather fresh candidate turned out to be the right choice for us: Vue.js, a library with a simple but powerful API. We fell in love with it and hope you will as well.

When building your own screens for the admin area, you can use any library you are used to. But as Pagekit comes with Vue.js included, it makes sense to look into it and see if it's the right choice for you as well.

In this post, we will be introducing the basic concepts of working with Vue.js inside Pagekit. The completed example extension can be found on Github.

With Vue.js reaching its final 1.0 release, we have worked through Pagekit’s JavaScript code and all components of the admin area to make sure things are running smoothly. With today’s 0.10 release, that migration is finished. Pagekit is now running with Vue.js 1.0.

What’s new

From a user point of view, nothing new has been added. This is a big release, but everything happens under the hood. The biggest change for developers is the availability of Vue.js 1.0. You can (and should) now build your extensions for the new version of Vue. Extensions still using an old Vue version can and will probably break.

In the past few articles, we have looked at the basics of modules and routing. However, our first controller only returned simple strings. This week, let us look at actual view rendering.

With the basic structure of an extension set up, a common task is to register your own controllers and add your own menu items to the admin area. For that, we will look at some additional properties that you can add to the module definition in your index.php.

As a developer, you can easily extend what Pagekit already offers. Whether you want a custom theme or an extension for additional functionality, both are built following the same approach. In this post and the accompanying video, we will introduce what a package and what a module is - both central concepts of Pagekit.

In the past few weeks, we have been busy revamping our documentation for the Pagekit Beta version. This week, we've made it available in the new Documentation section.

Some of you have already noticed our work on Github. If you haven't had a look at it yet, don't worry. Everything is now available right here on the Pagekit website.

Documentation is a living thing. There are still sections which will see improvement in the upcoming weeks. Still, you'll now find everything to get you started with Pagekit development. Many advanced topics are already covered, others will follow soon.

We frequently update the website from Markdown files. So if you find a mistake or have ideas for improvement, please head over to the Documentation on Github. Any contribution with issues or pull requests is welcome. Thanks!

When you get started using Pagekit, it is important that you know your way around the file structure. As Pagekit has a very clear separation of core code and third party files, this shouldn't be a big deal.

In this post, we give you an overview of the essential files and folders. We also have another video prepared for you.

One month after the Beta release it is nice to see how Pagekit is growing. Developers are adopting the new Beta version, the first extensions appear in the marketplace and new Pagekit releases are coming up. To keep track with all that's happening, we're trying to write up regular roundups.

This October SymfonyLive takes place in Berlin and we are happy to support the conference as Gold sponsors. Last year we had the chance to present Pagekit for the very first time to the audience. Now, one year later we are even prouder to give first insights into Pagekit's Beta version. Join our lightning talk on Thursday or just meet us and grab some Pagekit stickers at our booth in the sponsor area.

Today we are happy to introduce the first Pagekit Beta version. You guys have been very patient, but believe us when we tell you: it was worth the wait. The reason this took a while is simple: Pagekit has been revised entirely. To name just the most fundamental changes, here is a small overview:

1. A new user interface
2. A site tree to manage everything in one place
3. A new default theme, called One
4. An even more modular architecture
5. Data-reactive components with Vue.js
6. Package management using Composer

To us this Beta release feels more like a sort of Pagekit 2.0. We changed and reworked Pagekit, iteration by iteration to create the best possible experience for end users and developers. Now, let's take a closer look at all the new stuff.