Project Update

Published on: Nov 24. 2014

About the author

Where Were We?

We do apologize that we haven't been writing, but we will change this, starting from today. We have been working really, really hard and lot's of interesting things has happened and we would like to share some of them with you. 

If you can spare 5 minutes on this blog post, you will get a an update on where the project is going, where are we currently and what are the next steps. If not, well, here is a brief overview:

  1. The website has been redesigned
  2. Webiny Framework launched
  3. Everything is open sourced on GitHub
  4. Next step: Webiny Platform

Website Redesigned

We have decided to create a new design with several landing pages that really address what Webiny is, and what it will become. The website now mostly communicate towards designers and developers, for whom we are building our platform. We hope you like it and will spend some time going through the content.

If you have any feedback on the new design, feel free to leave it down in the comments. 

New PHP Framework

For the past six months we have been working hard on finalising the first stage of our plan, which was the release of our framework.  It's available for a free download on our GitHub repository, All our releases are now available under the MIT license. Any star or follow is much appreciated and will give us additional confidence to make it even better and easier to use in future releases.  

Why another PHP framework?

In our conversations with other developers we would sometimes encounter the question, why are we creating another PHP framework, why don't we just use Symfony or Laravel or even Zend? In some cases, also a question like, why is your framework better?

To give a good answer, first you need to understand that we are creating a Platform. If you check our homepage, you will see the three promises, in short, they are speed, ease of use and quality. To address those, we cannot rely on 3rd party software, at least not for the foundation for our platform. 

Main reasons around that are:

  1. We cannot easily control releases of new code and versions
  2. We cannot control how some fixes are made and deployed
  3. We cannot guarantee that things are not going to break

Referring back to the three promises, these are really important for us, and for our future users. We want stand confidently behind them and not to stress if the next update will break the system and if we would need to spend couple of months implementing the patches and similar.

We couldn't see any framework, that would provide this security, and the rock solid foundation, for our platform in the years to come. That's why we choose to create our own, also share it with all of you.

Next steps

We are currently working the on architecture for Webiny Platform. The architecture is a combination of Javascript (React and ES6) and PHP. About 70%/30% in favour of Javascript. 

In parallel to that, we are working on our HTPL template engine. The first RESS template engine (REsponsive Server Side). We see that current template engines simply don't match requirements of responsive web, especially when it comes to performance.

Anyways, stay tuned for many more updates and previews. Follow us on our GitHub, and if you wish to stay up to date, subscribe to our newsletter (down in the footer). 



Header image by Nomadic Lass


Lastest from our blog:

The Power of the Community

In the focus of recent feedback that I got, I think there is a need for me to justify some of the decisions we made while developing Webiny Framework.

Share & subscribe: