I am shifting this to a real meta issue about the Drupal 8 version, further discussion should happen in sub-issues. I have made an initial commit for Drupal 8 and cut a development release. Here is a transcript of the release notes:
Development release for Adpativetheme Drupal 8.
The D8 version of Adaptivetheme is a total re-write of the core theme and sub-themes. The admin theme has been removed also.
You MUST enable AT Core first
This theme uses PHP Classes and autoloading, however that will fail in Drupal 8 if the base theme is not enabled. If you enable a sub-theme without first enabling AT Core you will get a fatal error. At the moment this is a limitation of Drupal 8, hopefully by the time Drupal 8 ships sub-themes will be able to force base themes to be a dependancy, but right now we cannot.
I'm hoping like hell this beta blocking critical issue will fix this problem and we can all sleep easier:
Everything is treated as a Block
NOTE: this current version anticipates the commit to Drupal 8 of the "convert everything to a block" patches. This means that if you enable this theme you will not see things like the Logo, Site name or slogan, Page titles, Tabs, Actions links etc etc. The one page level variable I have included as a legacy support feature is the Messages variable, because we really need that during development. When the D8 patches are finally committed this will be removed.
I have created this module to use for testing: https://drupal.org/sandbox/jmburnz/2122067 it includes page title, site name, slogan, logo, messages and action links as blocks.
Please see these issues and help out if you can:
Drupal 8 will ship block configuration files in the themes config directory - this will tell Drupal to enable certain blocks when the theme is enabled. Currently there are patches against Drupal 8 for Bartik to achieve this, and Adpativetheme will of course do the same.
Its still early days for Drupal 8, we are still many months away from release so we have a lot of time to discuss and expand, develop and hone the ideas presented in this theme - they are radical and far reaching, I make no apologies for that. Time to move forward with new ideas about how we can improve theme building, how we can make theme building faster and easier.
The core theme provides just one front facing capability - a sub-theme generator that you can use to create new sub-themes. Enable the AT Core theme and visit it's setting page to generate a new sub-theme. There are two sub-theme types - a minimal sub-theme and a standard sub-theme. Documentation in included within the AT Core Appearance settings under the Help tab.
I would like to personally thank kingfisher64 for making this feature request and inspiring the development of the sub-theme generator, I hope new Drupal users find this easy to use (it is). It really does take the difficulties out of creating new themes.
The long term goal is to replicate these options in Drush, which is a high priority.
The biggest change for sub-themes a complete new layout system and does not include a GUI for manipulating layout values, instead you can select precomposed layouts or build your own. A "layout" is akin to a layout plugin however they have no templates. Page template code and region declarations are generated from definitions in the layouts yml file.
There is extensive help included within the theme itself. All sub-themes have a Help tab with many pages of help on the various new systems within the theme.
The primary reason for these changes is to allow themers much more control over their layout, and for me to be able to provide many more layouts well beyond what the AT7 version was ever able to support (mainly due to the complexity of the old AT D7 page layout plugins). The new layout plugins are extremely simple, and while they require you to provide the CSS layout there are many more options for doing so.
UI Kit based themes will have a fairly distinct aesthetic design out of the box, however because of the extensive use of SASS variables and the overall structure of the files and variables you can change this very easily and quickly.
Right now the UI Kit is in development/prototyping stage.
Extensions have been added back in:
- Images alignment and captions
- Touch Icons
- Markup overrides (varying options, mostly the same)
Fonts will undergo a major re-write to simplify all aspects, including a new, easier way to add Google fonts and likely deprecate support for @font-your-face since this was the least used feature of the fonts system.
Image alignment and captions can now be configured per content type and per display mode - so you have very granular control over image field alignment.
Touch icons is the same.
Markup overrides is pretty much the same although don't expect everything to work at this stage :)
In the first commit all extensions have been removed. This is pending a full review of all extensions, how they are being used by real users, and what might be applicable to D8. For example some extensions may be removed because D8 now supports the option natively, or that a module has risen to prominence that can now be relied on to provide the same capability without overloading the theme with features and code. It is highly likely that a large number of extensions will be shipped with the theme, however it is not yet decided how this will work or which ones these will be, most likely to be included are the Fonts extensions, Title styles and something similar to the Image Alignment and Captions extensions. Some of the Markup Overrides will make it but some will be removed simply because the theme works differently now and some we don't need anymore due to D8 changes.
Code Reviews and Testing:
Really what we need are user tests and deep code reviews.
Testing: on all levels from all types of users. Where do you get stuck, what is hard to understand, hard to use? Are there concepts or features that are conceptually hard to or worse impossible to understand? What is your overall feeling towards the new system?
Code Reviews: many new ideas are being introduced here and I will not hide the fact this is my first real crack and doing Object Orientated PHP. There are some new classes and I have tried to understand the usage of classical patterns and leverage Drupal core where applicable. I would surely appreciate deep code reviews, ideas and improvements from experienced OO developers and patches are of course very welcome. I am looking for constructive criticism and ways to improve the code, performance of the code, extensibility and probably some more abstraction where that might make sense.
CSS and SASS reviews are also welcome. In particular if you use Susy Next (which all the shipped layouts and the new ELF layout system uses).