Hinode v2.0.0 released

[markdumay]

Hinode v2 is out! With 557 commits, 416 files changed, and almost 4 months passed, this has grown into a major overhaul.

The headline changes:

• New components — team, testimonials, approach, and featured content blocks
• Content blocks extracted — hero, contact, faq, menu, testimonial-carousel, and more are now a standalone mod-blocks module
• Dart Sass required — libsass is dropped; required for FontAwesome v7 compatibility
• Companion module bumps — mod-fontawesome v5, mod-flexsearch v4, mod-mermaid v4 (all with breaking changes)
• LLM-friendly Markdown output — new markdown output templates for structured content

The Hinode template is fully updated and serves as the reference implementation.

Full upgrade guide → https://gethinode.com/docs/migration/upgrading-hinode-v2/

Questions? Drop them below. Bugs? Use the issue tracker.

[chl33]

I've tried to update my blog to use Hinode v2.2.5. I've gotten almost everything to work. On the home page, I now see 3 columns: Projects and Posts (my two content types) and About. The projects and posts columns are blank however. As far as I can tell, the rest of my site looks fine. I've spent a while with gemini trying to figure out what is wrong and am stumped. Any suggestions? I reduced my content/_index.md to just title and author, and get the same result.

[chl33]

Thanks!! I reordered the module imports and then the home page immediately rendered as expected.

I had tried adding content blocks in content/_index.md and that had actually caused more content to disappear on the main page so that is why it was blank in the minimized asset. I'm sure now that with the import order fix it will work for me.

I moved my partials and shortcodes folders as you recommended.

[markdumay]

Great, glad it worked out!

[chl33]

I noticed one more minor issue. I noticed that the Hinode v2.4.0 version of my site no longer had a "search" box at the top. I found that if I switched "model = true" to "modal = false" in [navigation.search] in config/_default/params.toml, then the search box showed up. So for me at least, this logic is reversed.

[markdumay]

Hinode v2.3.0 fixed a bug with the search config. Previously navigation.seach.enabled was simply ignored. Hinode now has two settings that can be set in the params:

hinode/config/_default/params.toml

Lines 158 to 160 in 6f551ac

	[navigation.search]
	enabled = true
	modal = true

• enabled: toggles search on/off
• modal: renders an icon + modal popup instead of an inline search box (the default)

The modal popup is a style preference. I typically use a search box for content-heavy sites, such as documentation sites. I hope this clarifies it.

[chl33]

Ah, that makes sense. Thanks.

[mcsooks]

For our hinode-based website, we were able to update from v1.23.7, but it broke some custom code we had.

In some of our markdown files, we use shortcode within the header, for example:

## {{< icon "fas users" >}} How We Work With You

what happens is that the header link appends a temporary token that hinode assigns to it:
#hahahugoshortcode84s2hbhb-how-we-work-with-you

This would get displayed in the auto-generated toc (the one that is on the right-hand sidebar), but it is functional.

To deal with this, we added a custom code in layouts/_partials/assets/toc-parse-content.html to strip displaying the token (but keep it in the actual link; it appears handling the url rendering is lower-level).

   {{ $cleanTitle := replaceRE "HAHAHUGOSHORTCODE[0-9A-Za-z]+" "" $item.Title }}
.
.
.
    {{ $htmlAttr := "" }}
    {{ range $k, $v := $attrs }}{{ $htmlAttr = printf "%s %s=%q" $htmlAttr $k $v | safeHTMLAttr }}{{ end }}
    {{ $rendered := printf "<a %s>%s</a>" $htmlAttr $cleanTitle }} 
    {{ $result = $result | append $rendered }}

This works in hinode v1.23.7, but when we updated to hinode 2.x, it appears that the way these temporary tokens are generated and assigned has changed, such that the header link no longer matches the corresponding link in the right-sidebar link:

header link = #hahahugoshortcode84s2hbhb-how-we-work-with-you (ID is 84)
sidebar link = #hahahugoshortcode82s2hbhb-how-we-work-with-you (ID is 82)

Even if we do not modify displaying these temporary tokens for the shortcode, the right-sidebar links are still broken as they do not match the header link.

Where in the repo should I look to try and address this?

[markdumay]

Thanks for the elaborate example @mcsooks. The TOC rendering was indeed revised in Hunode v2 and now adapts Hugo's page fragments. I released a fix in Hinode v2.8.3 to better handle shortcodes that are nested in the page headers. A test page is available here: https://demo.gethinode.com/en/blog/first-post/. This a snippet from the Markdown page behind it:

## First paragraph {{< icon "fas users" >}}

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

### Nested paragraph {{< icon "fas link" >}}

Nam enim nulla, egestas et nunc non, elementum aliquet justo.

## {{< icon "fas globe" >}} Second paragraph

In ac lobortis diam.

Due to Hugo's rendering limitations, the icons are stripped from the sidebar TOC and mobile TOC. They are rendered on the main page though.

[mcsooks]

@markdumay thank you so much for the update to address this :) I tested and confirm that this fix works (at least for my hinode build). thank you again for this!

[mcsooks]

I'm noticing that in hinode v2.x, flexsearch now indexes _index.md pages, BUT it does not include nested _index.md files.

For example:

content/data-science/_index.md = included in flexsearch result
content/data-sicence/data-visualization/_index.md = NOT included

I can't figure out where in the mod-flexsearch or my config files that I can adjust to include these nested _index.md files. Is this even possible?

[markdumay]

Thanks for sharing @mcsooks. I've released a fix in mod-flexsearch v4.1.2.

[mcsooks]

I did a mod:update to pull this update into our build and confirm that nested _index.md content are now included in flexsearch results. Thank you so much for the quick response!