By Craig Buckler
314 words, 2-minute read
- Why create a utility library?
- Why not add them to Publican?
- Should they be separate libraries?
- Get started
Publican.lib v0.1.2 was released on . It’s a common set of template and utility functions that help you generate static websites with Publican.
See the Publican.lib documentation…
Why create a utility library? #
I’ve used Publican to generate various static sites. Most use similar functions to create navigation, feeds, formatting, etc, so I found myself duplicating them into every project. Publican.lib is a common set of utilities I can update in one place and deploy anywhere.
Why not add them to Publican? #
Publican allows you to craft HTML as you desire and that remains ideologically important. Publican.lib provides opinionated functions such as:
- site navigation menu components using
<menu>,<details>, and<summary>elements - string replacements that substitute HTML
styleattributes for CSSclassreferences - an event hook that adds a Publican
<meta name="generator">tag into the head of every HTML page
You may like them all. You may like some but not others. You may hate everything about it. A separate library allows you to use what you want.
Should they be separate libraries? #
Perhaps, but given the whole library contains 20Kb of code, it’d possibly be over-engineering at this stage. We’ll see how it grows.
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.
Comments
Nothing yet. Say the first thing.
Sign in to join the conversation.