Publican v0.10.2 and StaticSearch v0.4.0 updates

By Craig Buckler

309 words, 2-minute read

search
Image courtesy of Elijah Mears

Publican v0.10.2 and StaticSearch v0.4.0 were released on .

There should be no breaking changes.

Publican string replacement issue #

Publican allows you to define content string replacements. Previous releases would run the replacement twice when content was rendered inside a template. This didn’t normally cause a problem:

publican.config.js excerpt

publican.config.replace.set('Hi', 'Hello');

However, it would matter when the replacement included the search string:

publican.config.js excerpt

publican.config.replace.set('Hi', 'Hi there');

Hi becomes Hi there which then becomes Hi there there!

Version v0.10.2 fixes this so string replacement occurs once.

StaticSearch v0.4.0 updates #

The following features have been added or improved:

  1. Document indexing has been improved so content can be identified even when a page does not have a <main> element.

  2. You can set a log verbosity level.

  3. When no search directory is set (--searchdir), it defaults to a search sub-directory in the build directory (--builddir).

  4. An issue was fixed where pages were not indexed because a noindex reference was found inside minified HTML even though it was outside a <meta name="robots"> tag.

  5. The README now points to the comprehensive Publican.dev StaticSearch documentation.

Get started #

The Publican documentation provides a quick start guide, a detailed set-up guide, API references, and common recipes you can use and adapt for your own projects.