"BOSTON, MA--(Marketwired - Nov 19, 2015) - Today Acquia joins with the Drupal Association and a worldwide community of developers, businesses, and organizations in celebrating the general availability of Drupal 8, the new version of the world's most widely adopted, enterprise open source digital experience platform. Introducing hundreds of new breakthrough capabilities, Drupal 8 makes digital experiences extraordinary across all channels of customer interaction to deliver transformative business results." - Wallstreet Online.
Update: I have been working with Drupal 8 for months now, and it is awesome. I am sticking with Drupal. My latest article of Drupal 8 impressions.
I have just received a comment for my Should I upgrade my web site to Drupal 8... at all? article. I will quote this comment here, and this short article will be my response.
Drupal 8 is release and...
It is clearly a platform built for enterprises, without even trying to reach a general market. Development, blamed before for being expensive and time-consuming, got even worse. General market, working on shared-hosting-based environments can now kiss Drupal good bye. And good night might be even for Drupal as we know it.
Who's gonna participate in low-level tasks for Drupal? Wasn't this a OpenSource job for amateurs and not for enterprise-employees?
I can see the darkness in it. I'm working as a freelancer, using Drupal for most of my projects. Now I should really drop Drupal. I'm not working for enterprises, I don't want to pay expensive bills for hosting. I don't have projects of this magnitude. But where should I go?
Or the hosting market should change for Drupal? This is a shitty dilemma.
This comment does speak to me. It also echoes loudly across the internet. I myself have also been thinking about all this, and here are my thoughts below.
It has been about half a year since I last reviewed the progress of Backdrop CMS. Backdrop CMS is a fork of Drupal 7, that tries to introduce new and better functionality without breaking compatibility with Drupal 7 as much as possible. And I must admit, I have not been optimistic about the whole Backdrop CMS idea, though I understood the reasoning behind it. But now, after having revisited the issue again, BackDrop CMS does seem as a viable option to use, with some sweet sweet features (like it's new layout mechanism in core and the CMI). It is possible, that the Backdrop CMS will become a good alternative to Drupal 8 for smaller and cheaper sites. Here is a video - a bit outdated, but quite exciting.
After long years of labor on behalf of the Drupal community, Drupal 8 has been finally released!
Drupal 8 is built upon a better architecture, having Symfony as it's basis, and has tons of improvements in different areas, such as:
- Content Editing - in-place editing.
- Caching - more flixible and powerful selective caching.
- Architecture - pluggable OOP-friendly architecture.
- Theming - more powerful and themer-friendly theme layer based on Twig templating engine.
If you need to export your documents to pdf, ePub, and ppt (pptx), this article may come of handy. I have been in a project recently as a part a team working on an electronic educational web site, where educational materials were available online as articles, and also convertable from HTML to either a pdf document, an ePub document, or a Powerpoint pptx document. Then, it was required to render some articles into screenshots for presentations (mostly for PowerPoint). We have reviewed the libraries that were available, and came up with our choice of tools. And no, you don’t need expensive commercial solutions to do it!
How low is low? Yesterday I published my upsetting tests about the Drupal 7 to 8 RC1 performance. Clearly, 3 times drop of performance is not a nice thing to have in Drupal 8. Now, the question is, would that make me consider WordPress as the best alternative? We can safely say that Wordpress is the industry's standard. How does Drupal 7 and Drupal 8 performance compare to that of Wordpress?
After Wim Leer's article on the Drupal 8 enhanced cache, I decided to run a performance test comparing Drupal 7.39 and the new Drupal 8 RC1 performance. I had high hopes. However, the results for Drupal 8 are still not good. For anonymous users, Drupal 7 beats Drupal 8 as much as 3 times still. For logged in users, Drupal 7 beats drupal 8 as much as 2 times.
I did not want to build a copy of a New Relic but smaller. I needed a slightly different logic. When thinking of a tool to monitor multiple web sites, I wanted to create a type of alert for admins when it was necessary. The logic was to gather relevant data as unobtrusively as possible without taxing performance, and then, to tell an admin, whether everything was basically ok, or not.
When you are a small company that tries to establish long-term relationships with its customers, you want to provide as much integration with them after the launch as possible. This may include hosting or hosting reselling, a support and update plan, and a continuous growth/integration plan. This may also mean, that you will provide performance support as well. It is this last aspect of performance support that I have been thinking about recently, writing a proof-of-concept mechanism to implement it. I would like to bring out some thoughts into a wider community to discuss.
Now that we have had an anatomic overview of Drupal 8's Ban module, we can proceed further to have a closer look at it's code. In this second part, we will have a look at YAML, and the concepts of services, subclassing, autoloading, and the dependency injection.