What awaits us in Joomla 3.0
So, recently I wrote about what awaits us in the new Joomla framework. Now it became known what awaits us in the new Joomla CMS itself under version 3.0 (which seems to be coming out in September).
In the last article in the comments, they scolded the Joomla developers or all the PHP writers for inventing bicycles instead of doing useful things. The Joomla team also decided that you are not sure to invent big ones, you need to take something ready for the interface. kyle.ledbetter offered to take “ready” Twitter Bootstrap 2.0. There was a heated discussion on 6 pages, as a result of which they decided to take the bootstrap.
Accordingly, you can see the concept of the site on Joomla 3.0.
The second change is admin. Admin (as seen from the previous example) at the top of the page with a ribbon. It is not clear whether the usual admin panel will remain or not, but for the time being they write this:
')
Next is compatibility. As you know, Twitter Bootstrap is written using LESS, HTML5 and jQuery. Joomla is also compatible with HTML4, and uses Mootools (on this occasion, a lot of copies were broken on the forums). Now the developers are going to include jQuery instead of / along with Mootools, which again, can not but rejoice.
If you have been using Joomla for a long time, you might have noticed that for some developers, their extensions and components look different. The community currently has no uniform standards for a graphical interface. One of the tasks on the way to the new version is the creation of a set of uniform graphic elements that can be used in the development of components, modules and other extensions. Such a thing will be called JUI (Joomla User Interface).
And, at the end, I will cover topics that have come from Joomla at GSOC:
1) JGoogle package for using Google API
2) Joomla Workflow . As I understand it, this is something like a business process description. That is, you can say that "the user must go here, fill it in, then he will have to send a letter, and allow him to go here and press that red button."
3) Installer languages . I don’t know what the old one didn’t suit them, but probably with blackjack and whores.
4) Package JMediaWiki - can, for example, download the category of articles from the wiki and put it like articles on the Joomla site.
5) Compress javascript / css on the fly. That is, the programmer writes everything as usual, and Joomla itself compresses (and maybe combines files) and sends.
6) Project to add a RESTful API to Joomla,
7) Package for integration into social networks. Google, Facebook, likes, comments, and more. VKontakte and Odnoklassniki unfortunately (or fortunately?) Is not expected.
In the last article in the comments, they scolded the Joomla developers or all the PHP writers for inventing bicycles instead of doing useful things. The Joomla team also decided that you are not sure to invent big ones, you need to take something ready for the interface. kyle.ledbetter offered to take “ready” Twitter Bootstrap 2.0. There was a heated discussion on 6 pages, as a result of which they decided to take the bootstrap.
Accordingly, you can see the concept of the site on Joomla 3.0.
The second change is admin. Admin (as seen from the previous example) at the top of the page with a ribbon. It is not clear whether the usual admin panel will remain or not, but for the time being they write this:
, . . . , , , . , . "" . .
')
Next is compatibility. As you know, Twitter Bootstrap is written using LESS, HTML5 and jQuery. Joomla is also compatible with HTML4, and uses Mootools (on this occasion, a lot of copies were broken on the forums). Now the developers are going to include jQuery instead of / along with Mootools, which again, can not but rejoice.
If you have been using Joomla for a long time, you might have noticed that for some developers, their extensions and components look different. The community currently has no uniform standards for a graphical interface. One of the tasks on the way to the new version is the creation of a set of uniform graphic elements that can be used in the development of components, modules and other extensions. Such a thing will be called JUI (Joomla User Interface).
And, at the end, I will cover topics that have come from Joomla at GSOC:
1) JGoogle package for using Google API
2) Joomla Workflow . As I understand it, this is something like a business process description. That is, you can say that "the user must go here, fill it in, then he will have to send a letter, and allow him to go here and press that red button."
3) Installer languages . I don’t know what the old one didn’t suit them, but probably with blackjack and whores.
4) Package JMediaWiki - can, for example, download the category of articles from the wiki and put it like articles on the Joomla site.
5) Compress javascript / css on the fly. That is, the programmer writes everything as usual, and Joomla itself compresses (and maybe combines files) and sends.
6) Project to add a RESTful API to Joomla,
7) Package for integration into social networks. Google, Facebook, likes, comments, and more. VKontakte and Odnoklassniki unfortunately (or fortunately?) Is not expected.
Source: https://habr.com/ru/post/145511/
All Articles