Quick Save

TODO.md

@@ -6,9 +6,16 @@
 + [ ] After April 17, 2018 use the new NOAA weather API for example in help and README.md (or replace with a new example)
 + [x] Copyright year needs updating in source files
 + [x] Need to handle Toml, JSON front matter based on their respective start/end delimiters
++ [ ] **sitemapper** needs to respect the 50K/50MB url and size limits per spec, see https://www.sitemaps.org/protocol.html
 
 ## Next (road to v1.0.0)
 
++ [ ] **byline** should pickup a by line from front matter OR the regexp
++ [ ] **titleline** should pickup a title from front matter OR the regexp
++ [ ] **mkslides** should be depreciated in favor of **mkpage** using front matter to indicate an output format of slides.
++ [ ] **sitemapper** should consider front matter in deciding the structure of sitemap.xml, also should allow for more than once sitemap.xml to be generated (E.g. a blog might have its own sitemap, see https://www.sitemaps.org/protocol.html
++ [ ] **frontmatter** needs to handle the YAML vs. TOML issues between Hugo/Assemble style YAML front matter and Mmark style TOML front matter, this should be done via a command line option and possibly by file extension
++ [ ] **mkpage** defaults should be configurable including treating .md as MMark verus .mmark only as MMark file with requiring specifying front matter
 + [ ] Read in mkpage.toml, mkpage.json or mkpage.yaml for mkpage config
 + [x] Evaluate switching from Blackfriday to GoMarkdown
 + [x] Add support for [Go Markdown](https://github.com/gomarkdown/markdown)

index.html

@@ -40,11 +40,7 @@ <h1>mkpage</h1>
 <a href="http://handlebarsjs.com/">Handlebars</a>. It is also similar to <a href="https://gohugo.io">Hugo</a>&rsquo;s template markup.   <em>mkpage</em> has been easier for us to support when compared with
 more established static site generators like <a href="https://jekyllrb.com/">Jekyll</a> <a href="https://gohugo.io">Hugo</a> and <a href="http://assemble.io/">Assemble</a>.</p>
 
-<p><em>mkpage</em>&rsquo;s minimalism turns into an advantage when you combine <em>mkpage</em> with the standard suite of text
-processing tools available under your typical Unix/Posix like operating sytems. This makes scripting a
-<em>mkpage</em> project using languages like Bash and Python relatively straight forward.  Each <em>mkpage</em> utility
-is independent. You can use as few or as many as you like as you when you script the website creation
-process that best fits your needs.</p>
+<p><em>mkpage</em>&rsquo;s minimalism turns into an advantage when you combine <em>mkpage</em> with the standard suite of text processing tools available under your typical Unix/Posix like operating sytems. This makes scripting a <em>mkpage</em> project using languages like Bash and Python relatively straight forward.  Each <em>mkpage</em> utility is independent. You can use as few or as many as you like when you script your website creation process. You wind up with a workflow and build process that best fits your needs.</p>
 
 <p>The following command line tools come with <em>mkpage</em></p>
 

mk-website.py

@@ -13,6 +13,8 @@
 }
 
 md_fragments = [
+    "t1.md", 
+    "t2.md",
     "nav.md",
     "copyright.md"
 ]