Releases: rsdoiel/mkpage
A decomposed content system for static site generation
Pretty much all you need to host a static website and build it from Markdown content. mkpage started as a single tool but now has friends.
+mkpage - render content from various sources (files, string, URL) in various formats (JSON, Markdown) using Go's template language
- mkslides - like mkpage but for rendering HTML based slide presentations
- mkrss - generate RSS from Markdown files
- titleline - extract titles from Markdown files
- byline - extract bylines from Markdown files
+slugify - turn a title into a URL/Path friendly string - reldocpath - calculate relative paths for use in templates and scripts
- sitemaper - generate sitemaps for your website
- ws - a nimble static file web serer that will not reveal your dot files and directories
introducing mkslides and slugify
This release merges in slugify and mkslides. It also include bug fixes.
integration of rsdoiel/cli and rsdoiel/tmplgn
Bug fixes, integration of a more standardize cli interface, integration of common template functions from rsdoiel/tmplgn. Updated docs and recipes.
Refinements, bug fixes and a companion utility called reldocpath
This release is primarily refinements, bug fixes and an additional companion utility called reldocpath.
reldocpath is helpful for calculating relative paths to assets when using a common template for content rendered to differing levels of subdirectories.
See the README.md for details.
automatic markdown rendering
The "use markdown" option was removed. If a string is hinted as markdown, e.g. "markdown:this is important" the string will be run through the markdown processor. Likewise files that end in the ".md" extension will always be run through the markdown processor. Likewise if the "content-type: text/markdown" header is found in the URL response then the markdown processor will be invoked. This brings markdown processing in line with how JSON is handled in mkpage.
Better JSON support
JSON decoding now handles for 'json:' type strings, files ending in .json as well as URLs returning content types "application/json".
Added support for multiple templates
Go v1.6 provides for template blocks as a common mechanism to split your complex templates into separate parts and combine them in the final document. This release adds experimental support for that.
Improved JSON content integration with templates
If a URL resource returns a header of Content-Type: application/json then the content will be unpacked as a map[string]interface{} and passed to the template. This lets you pick out specific results from a JSON API in your template. Examples updated.