Releases: ripple/dactyl
v0.13.2
This release adds "hover anchors" and fixes two bugs with filters and frontmatter.
Bug Fixes
- Fixed a problem with the
export
values of filters not being loaded when those filters were enabled via frontmatter on some pages. - Fixed a problem where filters would not get imported if they were only listed in frontmatter sections and not in the main config file somewhere.
Hover Anchors
Added the option to enable "hover anchors" for linking directly to headers. These are little links that appear next to a header so that you can right-click and copy the link to get a URL directly to that header. To enable hover anchors, you need to make two changes:
-
In your Dactyl config file, add a
hover_anchors
field to the definition of the target(s) or page(s) you want to enable them on. Set the value to whatever text or HTML you want to represent the anchor. Some examples:Plain text octothorpe:
- name: some_target hover_anchors: "#"
FontAwesome 4 link icon:
- name: some_target hover_anchors: <i class="fa fa-link"></i>
-
In your stylesheet, add styles to show
.hover_anchor
elements only when headers are hovered. For example:CSS:
.hover_anchor { visibility: hidden; padding-left: 1rem; font-size: 60%; text-decoration: none; } h1:hover .hover_anchor, h2:hover .hover_anchor, h3:hover .hover_anchor, h4:hover .hover_anchor, h5:hover .hover_anchor, h6:hover .hover_anchor { visibility: visible; }
Or, SCSS, if you prefer:
.dactyl_content { // Hover anchors --------------- .hover_anchor { visibility: hidden; padding-left: 1rem; font-size: 60%; } h1,h2,h3,h4,h5,h6 { &:hover .hover_anchor { visibility: visible; text-decoration: none; } } }
v0.13.1
v0.13.0
This release adds built-in (compile-time) syntax highlighting to Dactyl. This syntax highlighting runs by default, but you can disable it with no_highlight
in your config file (at the global, target, or page level). The built-in templates now use the built-in highlighting at compile time instead of doing syntax highlighting browser-side.
This release also includes some documentation improvements.
v0.11.4
v0.11.3
This release fixes a bug in the link checker that caused it to fail with IsADirectoryError
when attempting to check a link that omits the trailing the /
from a directory index.
Additionally, this release contains minor adjustments to the default stylesheet and templates, and adds the template information from the v0.11.0 release notes to a README in the templates directory.
v0.11.2
This release fixes a bug where the link checker ignored "known broken links" when checking links with absolute paths. (Prior to v0.11.0, the link checker wasn't capable of checking these links at all, so it skipped them regardless of whether they were marked as known broken links.)
v0.11.1
This release introduces a simple HTTP server to aid development of sites that use absolute paths in links, and to work around some issues with absolute paths in PDF generation.
- Watch mode (
--watch
or just-w
) now starts a simple HTTP server athttp://localhost:32289/
by default. You can use this to test your site locally if it uses absolute links. - PDF mode now uses an HTTP server, by default, to pass the pages to Prince. This works around problems with Prince being unable to resolve absolute hyperlinks from one page to another page in the PDF.
When using either (or both) of the above options, you can specify a different port to use with the --http_port
commandline option. To disable the HTTP server, specify --http_port 0
.
v0.11.0 Release Notes
This release brings new template functionality and improvements to the link checker.
New Features
- New, more powerful built-in templates.
- You can now include or extend built-in templates.
- The link checker supports absolute paths.
- External Links filter.
- Various fixes and minor improvements, especially for handling absolute paths (sites with subdirectories or "pretty URLs").
For details, see the release notes