Drupal 8

Theming in Drupal 8 - Conversion of themes to Twig

Drupal 8 is coming, and with it the biggest changes yet. One of them is a new theming engine. You can still use phptemplate. But if you want to switch, read Erstellt von Luca Stockmann post:

This post adds to the successful and popular "Theming in Drupal 8 with Twig?" (Part 1, Part 2) series from Steffen. It deals with converting Drupal phptemplate themes to use the new Twig template engine, like we recently did with our Busy theme. This is all for Drupal 8, so this might not be helpful to you just yet, but if you wanna get a headstart on converting your phptemplate theme to Twig, nothing's holding you back from starting right now!

Drupal 8 API freeze

Dries has announced the Drupal 8 API freeze.

I'm very excited about how Drupal 8 is shaping up; it will be a much more powerful and easier to use Drupal. While there is a lot of work ahead of us, I feel good about moving forward with the next phase of the Drupal 8 development cycle.

...

Currently, Drupal 8 includes backwards compatibility layers that support Drupal 7 APIs while we complete conversions of core modules to the new Drupal 8 APIs. An example is the routing support in hook_menu(), which will replaced by the Drupal 8 routing system. The Drupal 7 APIs are being marked deprecated in phpDoc, and contributed module developers should not use them because they will be removed prior to the Drupal 8 release.

The reason of the API freeze is that contributors can work on their modules, knowing the rug won't be pulled away under them.

Drupal 8 Module Development, Part 1: Getting Started

With Drupal 8 now in alpha release, LevelTen writes about Drupal 8 module development:

The old method of using .info files to initialize your module is going away in Drupal 8 and will be replaced with Symfony YAML(.yml) files. Old .info files will now become .info.yml files, and will look slightly different.

There are a lot of changes in Drupal 8. Probably the biggest disruption in Drupal for a very long time. But they are all welcome, and will solve some real world pains.

Thresholds, Code Freeze, Getting Features into Drupal 8, Criticals and Majors in Drupal

Cathy Theys blogs some important numbers on Drupal 8's status:

What are the threshold numbers? We want to be below 15 critical bugs, 100 major bugs, 15 critical tasks, 100 major tasks

There is the possibility for new features, when issues are under these counts:

How to Prepare Your Website for Drupal 8

Kevin Basarab mentions five things to do to be ready for the Drupal 8 upgrade, such as:

Preparing for a new core version of Drupal shouldn’t be the time to start looking at security updates. Core and module security updates should be part of your regular maintenance of a site.

Two items on his list of five are already taken care off if you host with Xplain Hosting!

The Mysterious Drupal Entity

The latest Lullabot podcast is on Drupal entities:

We explain what entities are, why we have them, and what the future may hold for them in Drupal 8.

An indefinite guide to Composer in Drupal 8

Geoffrey goes over some interesting new functionality in Drupal 8: composer. Used by many other projects, now coming to a Drupal near you:

Composer is a dependency manager. It’s not like a package manager, which downloads a specific version of a specific package and applies it throughout the system. It handles packages on a local basis, different for each individual project it works with. In this sense, it resembles Ruby’s Bundler gem much more closely than it resembles traditional package managers like apt, yum, MacPorts, Homebrew, or PEAR.

He continues with topics like why composer is in Drupal 8 and various ways to use it.

Drupal 8 code freeze and thresholds

Dries just posted about the Drupal 8 code freeze.

What happens now?

We now enter the "clean-up" phase of Drupal 8, where focus turns to refactoring of existing subsystems, better integrating features, and improving the consistency and coherence of the existing functionality. While APIs can and will still change as this coherence shapes up, contributed module authors are nevertheless encouraged to start porting their modules now, as there is still time to influence and fix APIs and the overall developer experience in Drupal 8. This will become much harder as we get closer to code freeze.

From Aloha to CKEditor

Recently Dries announced that Drupal 8 will not use Aloha, but ckeditor:

Since that announcement, CKEditor has caught up, and now offers feature parity to Aloha Editor when it comes to our needs. Frederico Knabben, creator of CKEditor, has reached out to offer whatever support he can to make CKEditor and Drupal work together better. They already prototyped a convincing alternative to Aloha Editor's killer "Blocks" system (which is an excellent match for Drupal's need to manage content within text content in a structured manner). In addition to that, we found that CKEditor is more mature in terms of APIs, documentation, and ecosystem around the project. Hence, after days of research and weeks of further discussion, the consensus is that CKEditor is now our best choice.

Inline Editing and the Cost of Leaky Abstractions

Jeff Eaton has a thoughtful post on inline editing and if this is such a good idea:

Many of the problems described above can be worked around by adding additional visual cues, exposing normally hidden fields in floating toolbars, and providing other normally hidden information when editors have activated Inline WYSIWYG. Additional secondary editing interfaces can also be provided for "full access" to a content item's full list of fields, metadata, and workflow states.

However, the addition of these extra widgets, toolbars, hover-tips, popups, and so on compromise the radical simplicity that justified Inline Editing in the first place. On many sites, a sufficiently functional Inline WYSIWYG interface -- one that captures the important state, metadata, and relational information for a piece of content -- will be no simpler or faster than well-designed, task-focused modal editing forms. Members of the Plone team discovered that was often true after adding Inline WYSIWYG to their CMS. After several versions maintaining the feature, they removed it from the core CMS product.