This site progressively records aspects of Drupal8 that may be of use to other Drupal CMS and PHP developers. It is not, and will never be, a complete guide to Drupal8. It is offered in the hope that it may be of some use to others.
The D8 Module Tracking report provides an overview of the readiness/usability of some of the more popular and useful contributed modules for Drupal8. The versions listed indicate the version that was assessed, tested, or in some cases just briefly inspected. A "D8 wishlist" is provided for modules that Webel IT Australia has found useful on previous Drupal7 sites, but for which there is no usable D8 equivalent yet.
Now that the Taxonomy term reference field has been removed in favor of Entity reference it begs the question how one is supposed to specifically target taxonomy term reference fields in Twig templates and in your CSS.
The following (which currently involves checking for the existence of a particular method) may not be very pretty, but it works.
In software engineering, don't repeat yourself (DRY) is a principle of software development aimed at reducing repetition of information of all kinds, especially useful in multi-tier architectures. The DRY principle is stated as "Every piece of knowledge must have a single, unambiguous, authoritative representation within a system." ..
When the DRY principle is applied successfully, a modification of any single element of a system does not require a change in other logically unrelated elements. Additionally, elements that are logically related all change predictably and uniformly, and are thus kept in sync.
Drupal code (and note I don't blame PHP here), both core and contributed, breaks the DRY principle so often, so constantly, so annoyingly repetitively, that it actually makes me (otherwise used to nicely coded object-oriented Java or C++ with model-driven support through graphical UML) feel like this:
This web site and Webel's OOE = Object Oriented Examples = One Of Each module were in part created to discourage further repetition of .. well nearly everything that is repeated in Drupal code, like those strings used as keys of structured arrays that have no intelligence other than documented key conventions (spread all over the place because there are no getters/setters to document), instead of intelligent objects.
You may have noticed that on some pages on this site, the type of a node page (both in page displays and teaser displays) appears in the title in brackets like this:
[module] Admin Toolbar
In this example, we demonstrate how this is achieved using Drupal8 theming preprocessor functions to create a convenient
type variable available to selected Twig templates.