I'd like to contribute a bit to this since at the moment there is not even a start page for the D8/Twig theming guide.
But in order not to rush ahead and create half-empty pages that people will not like I think I better ask first.

What we could quickly to is at least explain that Twig is the new engine and link to the Twig theme guide for the time being. As I am trying to create a D8 theme now, I guess this could help a lot since I could write down my findings from a beginners perspective:

  • How to start a D8 theme
  • How to use templates
  • Maybe a quick rundown on the most important changes from D7.

I do not shoot for completeness, e.g. the normal page about the .info file is rather lenghty. http://drupal.org/node/171205
Just entering some changes in D8 and properly highlighting them (following the way it is done now) would not be too much work, though.

Maybe the Docs people tell me what level of completeness is required to start this, so I do not add the aforementioned half-empty pages but still do not need too much work to get things started.

Comments

eigentor’s picture

eigentor commented

O.K. I discovered this might be a bit early because there is a lot of template conversion to do #1757550: [Meta] Convert core theme functions to Twig templates, maybe too many other moving pieces. I'll still leave the issue open till there is a basis to start on.

leehunter’s picture

leehunter commented
Issue tags: +d8docs

Currently we have section for Theming D6 and D7. It might be possible to simply update this section to add D8 content but I suspect that this is going to be far too messy with all the differences between the three versions so yeah, we'll probably need a new section called "Theming Drupal 8".

Because we still lack a method for single sourcing content, we'll again have to figure out how to handle the content which would be the same in both the D6/7 and D8 sections. Either fork the generic content (i.e. from d6/7 section to the d8 section) or pull it out into a separate section. Both options are ugly. It's generally a bad idea to have two disconnected versions of the same content (as opposed to displaying one source in two locations) but pulling the generic content out into a separate section is also problematic because it loses its context.

We'll probably need a number of other issues for the Theming Guide and perhaps make this the meta issue.

eigentor’s picture

eigentor commented

Oh yeah, single sourcing. You say the word. Probably a system like multilingual might be the most feasible, even if it would force every article to be rewritten for every Drupal version. I imagine a "version switcher" like a language switcher. But then again, that is another issue and who are the poor docs people who would have tu update all the content to that system...

leehunter’s picture

leehunter commented

Actually for a basic single source model, very little content, mostly overview topics, would need to be rewritten. It's partly the lack of a single source model that places a heavy burden on the doc team and leaves us with guides that are a confusing jumble of content from different versions.

eigentor’s picture

eigentor commented

@LeeHunter could you write or draw how that would look and work?

leehunter’s picture

leehunter commented

In the Theming Guide we have:

  1. Generic content
  2. D6-only topics
  3. D7-only topics
  4. Topics with a mix of D6 and D7 info
  5. D8 topics

Probably we'd start out single-sourcing with two versions of the theme guide: a D6/D7 guide that looks pretty much the same as the existing guide (1, 2, 3 and 4) and a much slimmer and less confusing D8 guide (1 and 5).

In this model it's just a matter of mapping the nodes to the right version using the existing metadata (which would still need to be checked and updated where necessary). Also we might decide that some content should be mapped to both the theme guide and the developer guide.

If we wanted to get really fancy we also might want to have the ability to mark up individual paragraphs as belonging to a particular version. So the node itself displays in both versions of the Theme Guide but an extra bit of information can be displayed or hidden depending on which version the reader wants to view.

leehunter’s picture

leehunter commented
Status: Active » Fixed

Marking this as fixed since there is now a bit of content on D8 theming.

I've also created a related issue re. the larger structure of the Theming Guide and how it's impacted by D8 #2066017: Evaluate Theming Guide content for Drupal 8

Automatically closed -- issue fixed for 2 weeks with no activity.

Anonymous’s picture

(not verified) commented
Issue summary: View changes

Added some formatting.