added a blog

Author: cmroanirgo

config.ergo.js

@@ -17,6 +17,15 @@ module.exports = {
 			  layout: "article.html"
 			  , path: "articles"
 		  }
+		, blog: {
+			layout: "post.html"
+			, default_fields: {
+				"author_image": "author.jpg"
+				, "author": "craig"
+				, "author_nick": "cmroanirgo"
+				, "author_website": "https://github.com/cmroanirgo"
+			}
+		}
 		, page: {
 			  layout: "article.html"
 		  }

source/_layouts/homepage.html

@@ -1,3 +1,3 @@
-{include:header.inc.html}
+{include:header.inc.html extracss:'home'}
 {content}
 {include:footer.inc.html}

source/_layouts/post.html

@@ -0,0 +1,10 @@
+{include:header.inc.html extracss:'post'}
+<h1><a href="/{uri}">{!:longtitle}{title}{else}{longtitle}{end}</a></h1>
+{content}
+</div>
+<div id="sidebar">
+	<p><img id="author_img" src="/images/{author_image}" /></p>
+	<p><a href="{author_website}" id="author">{author}</a></p>
+	<p><a href="{author_website}" id="author_nick">{author_nick}</a></p>
+	<p>{date.formatted}</p>
+{include:footer.inc.html}

source/_partials/footer.inc.html

@@ -1,10 +1,10 @@
-		</div>
-	</div>
+</div>
+</div>
 </div>
 
 
 <div id="footer" class="s">
-	<div class="c">∴ ergo-cms is the official site for <a href="https://github.com/ergo-cms/">∴ ergo</a> - a <i>beautiful</i> cms. | <a href="/rss.xml">Feed</a> | <a href="/sitemap.xml">Sitemap</a></div>
+	<div class="c"><a href="https://ergo-cms.github.io">∴ ergo-cms</a> is a <i>beautiful</i> cms. | <a href="/rss.xml">Feed</a> | <a href="/sitemap.xml">Sitemap</a></div>
 </div>
 
 </body>

source/_partials/header.inc.html

@@ -23,7 +23,7 @@
 	</div>
 	<h1 id="title"><a href="#content"><b>∴</b> {title}</a></h1>
 </div>
-<div class="s">
-	<div class="c">
-		<div id="content">
+<div class="s {extracss}">
+<div class="c">
+<div id="content">
 

source/_partials/menu.tex

@@ -1,3 +1,4 @@
 * "home":/
 * "articles":/articles.html
+* "blog":/blog.html
 * "about":/about.html

source/about.tex

@@ -17,30 +17,33 @@
 At one point I gave some notion to refactoring a lot of the code and got 99% of the way, but realised it was all spectacularly ill-designed. It wasn't production ready, and my websites have limped along since then.
 That code exists still, but is horrible and clunky and not extensible.[1]
 
-Seeing the rise and rise of various static generators, I was dismayed to see them not satisfy the abovementioned points.[2]
+Seeing the rise and rise of various static generators, I was dismayed to see them not satisfy the above-mentioned points.[2]
 
 So, this project is the 4th generation of something that has never otherwise seen the light of day.
 
 
-This is what ergo-cms is:
+h2. What ergo-cms is
 
 * A _very_ lightweight cms. I was shocked to discover than an install of Ghost currently clocks in at around 185MB! Ergo doesn't use _anyone_ else's fancy modules, unless it's vital. Hence there's no mustache, less, or any of that stuff here. (plugins for those will come, however).
 * Very extensible. If you like you _can_ use mustache, or less, etc.
 * Database-less. It uses flat files. It natively supports Markdown (for those who haven't seen the light), and Textile (for those that have). Being very extensible, it can support a whatever you can dream up.
 * Great at creating static websites. 
 * Great at publishing minimal changes to your webserver (using rsync, or git)
+* Supportive of things Javascript. There will be plugins for heaps of native javascript solutions: less, jsuglify, etc.
 
+h2. What ergo-cms isn't
 
-What ergo-cms isn't:
+* A Jekyll, WordPress, or _<insert your cms name here>_ replacement. Each platform has it's own idiosyncrasies, due to it's own feature set. As such, there may be features in those other platforms that don't match well here.
+* A web server. Although there's the ability to view your files in a locally hosted server (http:localhost:8181), it's nothing more than a simple file server & it's not production hardened. Since ergo-cms is a flat file generator, there's no reason for such a thing.
+* Supportive of ruby-esque things. There's a huge swell of support for things ruby, including it's many offshoots, such as YAML or SCSS. To me though, it's is one of the most crazy things I've ever seen emerge. If it requires _you_ to tell _me_ how good it is, and then get frustrated when I remain unconvinced, then it's a sure sign, _you're_ suffering fan-boi-isms. I've seen lots of it.
+* Supportive of _<flavour of the month markups>_, or _<too lazy to write a brace? use X>_, like coffee script. It seems that people who love coffee script love ruby and have an aversion to commas and curly braces. If you want to write a plugin for _<insert your markup language here>_, by all means, it'll work nicely - but I won't write it. I'm not a fan of fan-boi-itis. By supporting markdown, I believe I've supported enough of all of _that_ kind of craziness, & won't go a step further... unless it's LaTeX -- I've heard good things with it. So, I might write a LateX plugin. 
 
-* A Jekyll, WordPress, or _<insert your cms name here>_ replacement.
-* A web server. Although there's the ability to view your files in a locally hosted server (http:localhost:8181), it's nothing more than a simple file server & not production hardened. There's no reason for such a thing, with a flat file generator.
-* Supportive of ruby-esque things. YAML is one of the most crazy things I've ever seen. But people like coffee script too. If you want to write a plugin for _<insert your markup language here>_, by all means, it'll work nicely - but I won't write it. I'm not a fan of fan-boi-itis. By supporting markdown, I believe supported enough of all of _that_ kind of craziness, & won't go a step further... unless it's LaTeX -- I've heard good things with it. So, I might write a LateX plugin. I won't write an scss plugin though (because it's a ruby thing).
 
-What it will (eventually) do:
 
-# Have two admin interfaces: one running on php that uses ergo-cli (ie, with node installed on the server), and another that uses express (or something) so that you can just serve it - as is.
-# Have an offline editor. This will be a 'distraction free' app, with very minimal toys. It will probably run with "Electron":http://electron.atom.io/ and be _beautiful_ to behold (because sometimes you need to be inspired when writing, I've found). A mobile app will use "Cordova":http://cordova.apache.org/ and/or a touch of "Ionic":http://ionicframework.com/. 
+h2. What ergo-cms will (eventually) do
+
+# Have two admin interfaces: one running on php that uses ergo-cli (ie, with node installed on the server), and another that uses express (or something) so that you can just serve it - as is. As you can expect, they'll be simple things.
+# Have an offline editor for both desktop and mobile. This will be a 'distraction free' app, with very minimal toys. It will probably run with "Electron":http://electron.atom.io/ and be _beautiful_ to behold (because sometimes you need to be inspired when writing, I've found). A mobile app will use "Cordova":http://cordova.apache.org/ and/or a touch of "Ionic":http://ionicframework.com/ -- probably -- maybe. 
 #* They'll require some comms extensions (DAV/SFTP/rsync/convoluted git hook/custom) to be figured out first.
 # Have a slew of plugins that can be downloaded and configured easily. I was thinking something a bit 'npm-ish', like: @ergo install plugin-name@. The actual mechanics of this will be ironed out later.
 # Have a Theme repository. n00bs love this stuff. Designers avoid them, except to sell them, of course ;). At the moment, I'll ship a few skeleton projects that should solve the 99% of websites. Hopefully.
@@ -52,7 +55,7 @@
 
 fn1(small). I actually wrote it on a Galaxy Tab 2 7" while backpacking through Spain, on a rooted Android with a debian/xfce platform & jacked in with a mini keyboard attachment. Fun times.
 
-fn2(small).  The continued use of ruby dismays me still. Ruby and I don't get along. We never have. I tried. But I started with assembler (motorla/intel) and didn't see the need for such a language. If you love it, great. I don't, and I never will.
+fn2(small).  The continued use of ruby dismays me still. Ruby and I don't get along. We never have. I tried. But I started with assembler (motorla/intel) and didn't see the need for such a language. If you love it, great. I don't, and I never will. Assembler doesn't need hours of frustration to get started. Ruby, in my experience, does.
 
 
 

source/articles.tem.html

@@ -1,5 +1,7 @@
 {include:header.inc.html}
 
+
+<h1>Articles</h1>
 More articles coming soon!
 
 <dl>

source/articles/ANDF v1.tex

@@ -0,0 +1,110 @@
+{
+	title: "ANDF v1.0 Spec [draft]"
+	, miscdesc: "Specifications for A New Dawn Format, v1"
+}
+
+
+Here's a table of what I suggest for the 'A New Dawn Format', and what I'll be using for "ergo-cms":https://ergo-cms.github.io. This spec will be updated here (or links to updated spec). The javascript implementation shall be the final arbitrar of ambiguity (unless there's a clear fault in it).
+
+A Javascript implementation and this spec will be available at "https://github.com/cmroanirgo/andf":https://github.com/cmroanirgo/andf.
+
+h2. Specification
+
+In all cases @\n@ should be treated as @\r?\n@, to be line-endings agnostic.
+
+The use-case of this specification is to produce a hierarchical data structure similar to that of JSON, or more specificially a Javascript object. Note however, that the format should be able to be searched for a value, just like an .INI file, without needing to decode and load the whole file.
+
+Errors are to be expected in the file. They should _*never*_ generate an assert in production code, but is acceptable behaviour in test cases only. So, a prime use-case is to feed the deocder absolute junk (eg an image file). It will return an object, with nothing in it. This is an _error last_ approach. It is up to the rest of the code to decide that an empty object is acceptable or not.
+
+h3. Natural Names & Section Names
+
+We define a @natural-name@ as a regular expression: @[\w\-\.\/]*[\w]@. This a normal word (a-zA-Z0-9 & _) & '-', '/' & '.', but generally not ending with the symbols (except _). These are valid:
+
+* SomeKey
+* Some__--..//key2
+* ../some/key_
+
+These are NOT valid:
+
+* key/../
+* #key
+* key-
+* some key
+
+A @section-name@ is the same as a @natural-name@ except that spaces are allowed when used in the @[section name]@ blocks. See below.
+
+h3. Embeded Code
+
+The specification allows for code to be entered. The actual language of this code is up to the implementation, so a Perl implementation may render the code blocks as Perl. The Javascript implementation will render as Javascript and return a Javascript Object.
+
+h3. The Rest
+
+Where @section@ is: @/\n\s*\[(natural-name)\]\s*(?:\n)/@. @$1@ contains the section name. The one caveat is that a section name in @[ ]@ can also contain spaces.
+
+Where @comment@ is: @/\n[#;].*?@
+
+Where @key@ suits the regular expression: @/\n\s*(natural-name)\s*(?:\=\s*)/@. That is, a natural-word start at or near the start of a new line, with an equals sign after it. There need NOT be a value to the right of the equals. @$1@ contains the key
+
+Where @line-starters@ is either a comment, key, or section: @/(?:comment|key|section)/@
+
+Where @code-value@ suits the regular expression: @/\=\s*(\{ (.*)?\})\s*$/@. A code value continues to the end of a line. This may need ironing out a little more, to weigh security vs usability. This should always ONLY be a single line match, to encourage simplicity. @$1@ contains the 'code'.
+
+Similarly, @value@ suits the regular expression: @/\=\s*([\s\S]*?)(?:line-starters|$)/@. Matches all text until the next 'key =', [section], #comment, or end. @$1@ contains the value.
+
+Where @default-value@ is: @/\s*([\s\S])*\s*(?:line-starters|$)/@. Similar to @value@, but without need for the @\=\s*@ at the start. @$1@ contains the value.
+
+A @escaped-value-block@ suits the regular expression: @/-{3,}\s*\n([\s\S])*\s*\n(?:-{3,}|$)\s*/@. A block with --- and --- surrounding it. @$1@ contains the value.
+
+
+
+<pre style="min-width:860px"><code>title = Welcome to my homepage                               ; key + value
+uri = index.html                                                        ; key + value
+date={   (new Date()).toString + " OK"; }                               ; key + code+value
+metakeys = Some keys,other keys                                         ; key + value
+metadesc =                                                              ; key + ...
+I like writing blogs and learning                                       ;     ... continues
+about myself. Trailing spaces are                                       ;     ... continue
+eaten                                                                   ;     ... value
+
+[section1]                                                              ; section
+content = This is the content for some magical 'section 1' that exists. ; key + ...
+It keeps going until another '[section]' is found (on it's own line),   ;     ... continues
+or a 'key=' is met. Having a newline above [section] is optional.       ;     ... value
+extracss = green                                                        ; key + value
+
+#This is a comment. It needs to start with a "#" or                     ; comment
+; a ";"                                                                 ; comment
+
+section2.content = Another sections, using 'dot' notation.              ; key + ...
+These are also valid: [section.sub.subsub], section.sub.subsub.key =    ;      ... value
+
+[main content]                                                          ; section
+extracss = orange                                                       ; key + value
+
+Each section can also have it's own text. It must have a blank line     ; default-value 
+above it, OR be directly beneath a [section] mark                       ; ...(for main.content)
+And keeps on going until a valid [section], #comment, [section] or 
+key= is reached.
+
+[footer content]
+-------------                                        ; escaped-value-block, for 'footer content' default
+#This is footer content. This is NOT a comment
+;This is NOT a comment
+not-a-key = NOT a value
+
+All of this text is a 'default-value-block' (for footer.content). It is OK
+to forget the 3 dashes below, if the end of the file is reached.
+---
+
+[final.footer]
+some.key =                                           ; key (+ an empty value)
+---                                                  ; escaped-value-block, for 'final.footer' default
+This is the last block of text. 
+This is valid.
+</code></pre>
+
+
+
+
+
+

source/blog.tem.html

@@ -0,0 +1,11 @@
+{include:header.inc.html}
+<h1>Blog Posts</h1>
+<dl>
+  {begin:blog}
+	<dt><a href="{uri}">{title}</a></dt>
+	<dd>{metadesc}</dd>
+  {end:blog}
+</dl>
+
+<p>&nbsp;</p>
+{include:footer.inc.html}