This site has been archived. To learn more about our current products Ibexa Content, Ibexa Experience, Ibexa Commerce head over to the Ibexa Developer Portal
By
Tuesday 08 July 2014 4:37:06 pm
Today, we are happy to open the PlatformUIBundle git repository on Github. To be honest, it’s also a great personal achievement for me since it’s the result of exactly one year of work!
As its name suggests, this bundle provides the user interfaces which will replace the good old legacy admin interface. It actually provides the Platform UI Application which is divided into two different parts
The Platform UI is build around some key concepts and goals:
The Platform UI Application is based on the YUI Library and especially on the YUI App framework. We chose YUI because it provides a full set of consistent and high quality components.
As written before, the PlatformUIBundle provides an application which is executed by the browser and is divided into two different parts with two different strategies in the way they build the pages:
You probably wonder why we are implementing two different ways of building pages. On the admin part, we wanted to reuse some code that was produced in a very early prototype that was build in a more traditional way. In addition, as a great side effect, having the base components to include an AJAX response transparently in the application will allow any developer to extend it without a deep knowledge of the complete JavaScript stack. In other terms, in some use cases, extending the Platform UI application might be as simple as writing a Symfony controller and a very small amount of JavaScript code!
You can login in the application, browse the content through the content tree, display and edit content (depending on its field types), and, in the admin interface, access a system info page, the list of sections and their details. Most of those features are presented in the following screencast:
As you can see a lots of features are missing, like displaying sub-items, a complete version management UI, almost everything in the admin part, and some blanks need to be filled there and there ;-) At a lower level, we need to think and to implement a proper l10n/i18n system, the handling of the user’s policy, the extensibility points, ...
So this public opening is a great milestone but it’s only a small steps in a long journey. As usual, your feedback is more than highly welcome, be it as a comment here, issues in JIRA or as code through a pull request!