I learned today that I have to write a blog about Drupal 8. Thanks to Dr Google, and Mr Wiki, you can find all the answers you need from Drupal 1 to 8. And my first step as any other lazy reader was checking up FAQ from Drupal.org YES! Drupal 8 is available! https://www.drupal.org/project/drupal Whether you consider yourself an early adopter or a bit more conservative, choose Drupal 8 when its maturity aligns with your sense of investment and your project’s life cycle. Most people will rely at least a little bit on core usage statistics to help them choose the right time: https://www.drupal.org/project/usage/drupal An important thing to remember is that Drupal 8 is still Drupal. The open source content management system is so flexible that it is used by everyone from hobbyists and small non-profit organizations to large government entities and Fortune 500 companies. Drupal 8 has more than 200 improvements that will bring new capabilities and efficiencies to virtually any type of implementation, large or small On February 24, 2016, Drupal 6 will reach end of life and no longer be supported. After that, the community will shift its focus to versions 7, 8, and 9. While that shift in focus doesn’t necessarily mean your Drupal 6 site will be, for example, vulnerable to security threats, seriously consider moving away from Drupal 6 before February 24. Drupal.org doesn’t recommend starting a new project with Drupal 6 now. Well what about Drupal 7? You may be a Drupal 7 user and wonder about the benefits of Drupal 8 over Drupal 7 Here is a list from DigitalBungalow.com that may help you make that decision: 1 - OOP? Drupal 8 will officially enter the world of object oriented programming with the introduction of some core Symfony components. Symfony, a PHP framework developed by SensioLabs, enforce the use of the namespaced PHP classes instead of global functions—a development methodology commonly referred to as object oriented programming (OOP). This allows programmers to create dynamic relationships between these objects and adds the advantage of not having to change modules when a new type of object is added. More importantly, when done right this means code that is more maintainable, has fewer bugs, and requires less rework. 2. The default template engine will migrate to using Twig with Drupal 8. Twig provides a greater separation between logic and display, and marries well with Symfony’s class-based approach to programming. It also helps lower the barrier of entry for front-end themers trying to get into a Drupal project on the ground floor. Gone are the bad old days of embedded PHP logic scattered around numerous template files. 3. Inline Editing Drupal 8 will support inline content editing by using the Spark project. The Spark project was introduced in Drupal 7 and acted as an “incubator” for Drupal 8, spearheading the advancement of the platform’s authoring experience. With these refinements in place, Drupal is setup to directly compete with players such as Sitecore and CQ5, platforms that are known for their streamlined publishing and editing experiences. 4. A new toolbar will be introduced in Drupal 8. Also a product of the Spark project, the toolbar will be responsive, extensible and more concise. Top-level items include: Home, Menu, Shortcuts, and Users. For mobile, textual labels will be replaced with visual icons saving screen real estate and providing a cue for usage. 5. Views will be integrated as one of Drupal’s new core modules. “Views is the #1 most-used contributed module, installed on nearly 70% of all Drupal websites,” explains Dries Buytaert. The module provides a graphical user interface that allows you to organize and show your content any way you could imagine with out a single line of code. After its proven success, views will finally be brought into the Drupal core. 6. Drupal 8 will be the most accessible version of Drupal to date, specifically benefiting visually impaired users. The new internal method “Announce,” will give module developers the ability to create direct output to screen readers. Another Drupal object called Tabbing Manager will constrain tabbing to unneeded elements providing a functional workflow for those users. 7. Content creation…Simplified By default, CKEditor will be available as a replacement for the default Drupal 7 WYSISYG. If you’re unfamiliar with CKEditor it’s an open source application for HMTL text editing that simplifies web content creation. 8. REST and relax RESTful web services in Drupal 8 serves as a major sea change for the platform. Drupal content entities can now be interacted with via a REST (representational state transfer) interface allowing for the design of more tightly networked web applications. As the web eco-system becomes more co-dependent, relying on more and more third party integrations, having a standard interface with which to interact with your users and content will be paramount to allow for growth – REST gets this done. 9. Hablas Espanol? Building a multilingual website gets a lot easier with improvements to language maintenance options, site translations and easier-to-customize settings. This will benefit both end users and developer and reach greater audiences on both sides. Drupal 7 will be supported long after Drupal 8 is officially released. But if there’s a new or improved feature in Drupal 8—like fully translatable admin interfaces, or native schema.org markup—that you think could make your work better, take advantage of it. What ever version you decide, enjoy,and good luck Druappling away!