Skip to content

Creating Content

Jump to bottom
Anas Ismail Khan edited this page Aug 5, 2016 · 7 revisions

Posts

Any file that is present in "content/posts" is considered a single, independent post. And all content within the file, except for the metadata(if any), is going to be displayed in the post body. Danvers supports posts created using HTML, Markdown and Textile.

Obviously, the file extension is very important here.

  • HTML files must end in .html or .HTML
  • Textile files must end in .textile or .TEXTILE
  • Markdown files must end in .md or .MD or .markdown or .MARKDOWN

All posts need to be named according to this convention:

YYYY-MM-DD.Post Title.MARKUP

So naturally, a post about your pet beagle that you created on 29th February 2016, using markdown, would be named:

2016-02-29.Moi Awesome Beagle.md

All posts would be automatically listed in the blog feed, and any post is individually accessible as a page at example.com/?post=post-title So in my demo, a post titled "First post" is accessible at http://anasismail.com/others/Danvers/?post=First%20post

Pages

Any file that is present in "content/pages" is considered a single, independent page. And all content within the file, except for the metadata(if any), is going to be displayed in the page "container". Danvers supports pages created using HTML, Markdown and Textile.

Obviously, the file extension is very important here.

  • HTML files must end in .html or .HTML
  • Textile files must end in .textile or .TEXTILE
  • Markdown files must end in .md or .MD or .markdown or .MARKDOWN

All pages need to be named according to this convention:

Page Name.MARKUP

So a page named "About" that is created using textile would be named:

About.textile

Danvers is about as case-sensitive as the operating system it is hosted on. It is safe to assume that in most cases page/post names would be case-sensitive

about.html is NOT the same as About.html and certainly not the same as about.HTML.

Clone this wiki locally