Differences

This shows you the differences between two versions of the page.

--- misc:zola_tips [2022/12/25 01:57] – [Marking a menu item as active] mithat
+++ misc:zola_tips [2022/12/25 22:57] (current) – [Sections and _index.md] mithat
@@ Line 16: / Line 16: @@
 <WRAP center info 80%>
-This whole setup seems like it's more complicated than it needs to be.
+This scheme seems like it's more complicated than it needs to be.
 </WRAP>
@@ Line 23: / Line 23: @@
 ''_index.md'' has special access to information about the section's sub-pages. The typical use case for this is listing blog entries. Also, ''_index.md'' files can (should? must?) specify not just the template they will use but also the (default?) template page used by sub-pages.
-If you don't have a ''_index.md'' file in a folder, Zola does not formally consider it a section, but the pages defined in it are still accessible. You can define an ''index.md'' file in a folder if you don't need the abilities of a section.
+You don't need to have a ''_index.md'' file in a folder (except the root---see below). If you don't, Zola does not formally consider it a section, but the pages defined in it are still accessible. You can define an ''index.md'' file in a folder if you don't need the abilities of a section.
 You can nest sections.
@@ Line 48: / Line 48: @@
   {% endif %}
 </title>
+</code>
+**Better yet**, use the following idiom to set ''current'' to the current context, either ''section'' or ''page'':
+<code twig>
+{% set current = section | default(value=page) %}
+{{ current.title }}
 </code>
@@ Line 111: / Line 118: @@
 ===== Marking a menu item as active =====
-:?: :?: :?:
+There may be a better way to do this, but selectively adding a class if the relative path matches seems to work.
+<code twig>
+<ul class="nav navbar-nav navbar-right">
+  {# for each of the menu entries, if the relative path leads matches the page, add class="active" #}
+  {% set current = section | default(value=page) %}
+  {% set rpath = current.relative_path %}
+  <li {% if rpath == "_index.md" %} class="active"{% endif %}><a href="/">Home</a></li>
+  <li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown">Products <span class="caret"></span></a>
+  <ul class="dropdown-menu" role="menu">
+    <li {% if rpath == "products/_index.md" %} class="active"{% endif %}><a href="/products">Overview</a></li>
+    <li {% if rpath == "products/upcycled.md" %} class="active"{% endif %}><a href="/products/upcycled">Upcycled amps</a></li>
+    <li {% if rpath == "products/classic.md" %} class="active"{% endif %}><a href="/products/classic">Classic amps</a></li>
+  </ul>
+  </li>
+  <li {% if rpath == "about.md" %} class="active"{% endif %}><a href="/about">About</a></li>
+  <li {% if rpath == "contact.md" %} class="active"{% endif %}><a href="/contact">Contact</a></li>
+</ul>
+</code>
+No doubt, there are opportunities to stuff some of this into macros and/or partials and/or similar.
 ===== Breadcrumbs =====
-See this [[https://zola.discourse.group/t/breadcrumb/509/3|forum post]].
+See this [[https://zola.discourse.group/t/breadcrumb/509/3|forum post]], reproduced and re-formatted here in case it goes away:
+<code twig>
+{% block breadcrumb %}
+<div class="breadcrumb-container">
+  <a class="breadcrumb-path" href="/">Home</a>
+  {% set current = section | default(value=page) %}
+  {% for ancestor in current.ancestors %}
+    {% if loop.first %}
+      {% continue %}
+    {% endif %}
+    <span class="breadcrumb-separator">/</span>
+    {% set section = get_section(path=ancestor) %}
+    <a class="breadcrumb-path" href="{{ section.permalink }}">{{ section.title }}</a>
+  {% endfor %}
+  <span class="breadcrumb-separator">/</span>
+  <a class="breadcrumb-path active" href="{{ current.permalink }}">{{ current.title }}</a>
+</div>
+{% endblock breadcrumb %}
+</code>