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.