Separate out the case study template

It has an extensive extra 'project details' section.

It also doesn't (currently) have authors, which is optional on others
for the sake of blogs
This commit is contained in:
benjamin melançon 2018-11-17 17:17:44 -05:00
parent 7e2296a40c
commit d04edfc23b

View file

@ -0,0 +1,143 @@
{#
/**
* @file
* Theme override to display a node.
*
* Available variables:
* - node: The node entity with limited access to object properties and methods.
* Only method names starting with "get", "has", or "is" and a few common
* methods such as "id", "label", and "bundle" are available. For example:
* - node.getCreatedTime() will return the node creation timestamp.
* - node.hasField('field_example') returns TRUE if the node bundle includes
* field_example. (This does not indicate the presence of a value in this
* field.)
* - node.isPublished() will return whether the node is published or not.
* Calling other methods, such as node.delete(), will result in an exception.
* See \Drupal\node\Entity\Node for a full list of public properties and
* methods for the node object.
* - label: The title of the node.
* - content: All node items. Use {{ content }} to print them all,
* or print a subset such as {{ content.field_example }}. Use
* {{ content|without('field_example') }} to temporarily suppress the printing
* of a given child element.
* - author_picture: The node author user entity, rendered using the "compact"
* view mode.
* - metadata: Metadata for this node.
* - date: Themed creation date field.
* - author_name: Themed author name field.
* - url: Direct URL of the current node.
* - display_submitted: Whether submission information should be displayed.
* - attributes: HTML attributes for the containing element.
* The attributes.class element may contain one or more of the following
* classes:
* - node: The current template type (also known as a "theming hook").
* - node--type-[type]: The current node type. For example, if the node is an
* "Article" it would result in "node--type-article". Note that the machine
* name will often be in a short form of the human readable label.
* - node--view-mode-[view_mode]: The View Mode of the node; for example, a
* teaser would result in: "node--view-mode-teaser", and
* full: "node--view-mode-full".
* The following are controlled through the node publishing options.
* - node--promoted: Appears on nodes promoted to the front page.
* - node--sticky: Appears on nodes ordered above other non-sticky nodes in
* teaser listings.
* - node--unpublished: Appears on unpublished nodes visible only to site
* admins.
* - title_attributes: Same as attributes, except applied to the main title
* tag that appears in the template.
* - content_attributes: Same as attributes, except applied to the main
* content tag that appears in the template.
* - author_attributes: Same as attributes, except applied to the author of
* the node tag that appears in the template.
* - title_prefix: Additional output populated by modules, intended to be
* displayed in front of the main title tag that appears in the template.
* - title_suffix: Additional output populated by modules, intended to be
* displayed after the main title tag that appears in the template.
* - view_mode: View mode; for example, "teaser" or "full".
* - teaser: Flag for the teaser state. Will be true if view_mode is 'teaser'.
* - page: Flag for the full page state. Will be true if view_mode is 'full'.
* - readmore: Flag for more state. Will be true if the teaser content of the
* node cannot hold the main body content.
* - logged_in: Flag for authenticated user status. Will be true when the
* current user is a logged-in member.
* - is_admin: Flag for admin user status. Will be true when the current user
* is an administrator.
*
* @see template_preprocess_node()
*
* @todo Remove the id attribute (or make it a class), because if that gets
* rendered twice on a page this is invalid CSS for example: two lists
* in different view modes.
*/
#}
{% set title_paragraph_index = null %}
{% set has_title_paragraph = false %}
{% if content.field_body_paragraph %}
{% for i, paragraph in content.field_body_paragraph if i|first != '#' %}
{% if content.field_body_paragraph['#items'][i].entity.type.0.entity.id == 'title' %}
{% set has_title_paragraph = true %}
{% set title_paragraph_index = i %}
{{ paragraph }}
{% endif %}
{% endfor %}
{% endif %}
{% if not has_title_paragraph %}
{% set classes = [ 'hero', 'hero-' ~ node.bundle|replace({"_": "-"}) ] %}
{% if node.bundle != 'blog' %}
{% set classes = classes|merge(['is-dark']) %}
{% endif %}
{# Header hero region #}
<section{{ attributes.addClass(classes) }}>
<div class="hero-body">
<div class="container">
<h1 class="title is-2">{{ label }}</h1>
<p class="byline is-mono">Written by </p>
</div>
</div>
</section>
{% endif %}
<section class="section" data-headerbg="light">
<div class="container">
<div class="flow content">
{% if content.field_body_paragraph %}
{% for i, paragraph in content.field_body_paragraph if i|first != '#' %}
{% if i is not same as(title_paragraph_index) %}
{{ paragraph }}
{% endif %}
{% endfor %}
{% endif %}
{# No, i do not understand why content doesn't print the paragraphs but only
content.content does that #}
<div class="flow_full">
<div class="titlebar titlebar-bigborder content">
<div class="titlebar_title">
<h3 class="subtitle is-mono is-4">Project Details</h3>
</div>
</div>
<div class="columns">
<div class="column">
{{ content.field_case_study_client }}
{{ content.field_case_study_year }}
{{ content.field_case_study_status }}
</div>
<div class="column">
{{ content.field_technologies }}
{{ content.field_services }}
</div>
<div class="column">
{{ content.field_case_study_team }}
{{ content.field_case_study_partners }}
</div>
</div>
</div>
{{ content|without('content', 'field_body_paragraph',
'field_case_study_client', 'field_case_study_partners', 'field_case_study_status',
'field_case_study_team', 'field_case_study_year', 'field_technologies',
'field_services', 'uid', 'created'
) }}
</div>
</div>
</section>