28 Commits

Author	SHA1	Message	Date
Alan Orth	acde63b34f	layouts/_default/baseof.html: Make sidebar logic more robust ... Check if the params.sidebar is defined before checking to see if params.sidebar.hide is true or false. New sites might not have their config set up properly, so this avoids an error in the case that params.sidebar isn't defined yet.	2016-09-22 09:19:20 +03:00
Alan Orth	9bb8294089	Add RSS feed for posts to base layout ... Not sure who uses RSS anymore but Hugo automatically generates the feed so we might as well advertise it.	2016-09-19 10:00:28 +03:00
Alan Orth	72d5c94cc5	Add basic sharing icons to the bottom of posts ... By default they are on, but you can disable them by adding the following configuration value: [params.sharingicons] hide = true If this parameter is undefined (or "false") then the icons will be shown. Furthermore, you can disable specific icons by setting their value to "false", ie: [params.sharingicons] facebook = false Any icons not named will be shown. Currently there a four icons configureg: facebook, googleplus, linkedin, and twitter.	2016-09-18 17:11:08 +03:00
Alan Orth	731af8c564	layouts: Add basic support for OpenGraph and Twitter card metadata ... Uses basic data like title, description, author, and date that we are using with existing vanilla meta tags, but extends them to OG and Twitter Card tags. See [0] and [1]. For the Twitter summary cards specifically, you can optionally add attribution for your username by adding something like this to your configuration: [params.social] twitter_username = "@mralanorth" ... and for posts with images, you can specify an "image" in the post's front matter like so: image = "/2016/09/IMG_20160916_174409.jpg" And then the theme will opt to use Twitter's "large" summary card. [0] http://ogp.me/ [1] https://dev.twitter.com/cards/getting-started	2016-09-17 18:05:22 +03:00
Alan Orth	4427040041	layouts/_default/baseof.html: Enumerate non-post pages in header nav menu ... Still need to figure out how to determine which page we're on so we can set the "active" class accordingly (for Home we have the IsHome variable the we can check).	2016-09-14 23:43:26 +03:00
Alan Orth	d31626c5a3	layouts/_default/list.html: Check for page type instead of "section" ... Both work effectively the same for my use case, but the "type" is more obvious when looking at the code. See the documentation for Hugo's page variables for more info[0]. [0] http://gohugo.io/templates/variables/#page-variables	2016-09-14 23:39:39 +03:00
Alan Orth	42c06c260c	layouts: Only list posts on front page and sidebar ... We don't want to list other top-level pages like "About" here, they will be enumerated in the header.	2016-09-14 16:35:04 +03:00
Alan Orth	2bb9509bbb	layouts/_default/baseof.html: Add "active" class to nav if page is home ... Not sure how to do this for other pages yet, but I'll solve that once I start enumerating pages into the nav.	2016-09-14 14:55:29 +03:00
Alan Orth	e8ee0c68b7	layouts/_default/baseof.html: Smarter meta author tag ... Use the post's author from frontmatter, or else use the author from the site's config. You MUST have one of these set or else you will get an error during site generation. I think it's better to force the user to define an author tag rather than only printing it if it is defined because it is a good practice to help bots understand content.	2016-09-14 14:05:36 +03:00
Alan Orth	c5bacecad6	layouts/_default/baseof.html: Smarter meta description ... Use the post's meta description if it exists, otherwise use the one from the site's config. Set them using the "description" key in frontmatter or site config. Note: this means there is no way to NOT have a description. You must have *at least* a site-wide description and *optionally* a description for each page/post's front matter.	2016-09-14 13:45:34 +03:00
Alan Orth	cd3e327553	layouts: Use HTML5-compatible datetime format for posts ... The W3C validator was complaining. See: https://validator.w3.org See: https://html.spec.whatwg.org/multipage/semantics.html#the-time-element	2016-09-14 13:12:27 +03:00
Alan Orth	8c4b423173	layouts/_default/summary.html: Fix W3C validation error ... The validator[0] says: Element nobr not allowed as child of element a in this context. ... so I'll just remove it. [0] https://validator.w3.org	2016-09-14 12:39:40 +03:00
Alan Orth	d37e111ff4	Adjust header levels for post summary and page ... The W3C's HTML5 documentation says that header strength (h1–h6) is only important per section, but their validator[0] recommends only using one h1. [0] https://validator.w3.org/	2016-09-14 12:28:15 +03:00
Alan Orth	c94335a193	Make site header text clickable (to home) ... This is a pretty standard convention in blogs.	2016-09-14 12:24:38 +03:00
Alan Orth	2bb33145db	Allow optional addition of Google Webmaster Tools verification string ... Add to the site's configuration like so: [params] google_verify_meta = "BAi69DROASu2b2mkVNA_EyUsobfH7Mq8BmSg2Rn-Zp4"	2016-09-13 16:26:30 +03:00
Alan Orth	ba25b91d94	Allow site description to be Markdown	2016-09-07 16:47:59 +03:00
Alan Orth	f7b4f0a819	Allow configuration of how many posts to show on the homepage ... You can set this property in your site's config to override: [params] num_recent_posts = 7 Defaults to five (5) if unset.	2016-09-03 20:21:40 +03:00
Alan Orth	47b200578e	Use HTML5 header tag for blog header ... Makes it easier for computers to understand content by using tags that have explicit meaning. See: http://diveinto.html5doctor.com/semantics.html	2016-09-02 15:56:40 +03:00
Alan Orth	1f0799b9f1	Use H1 headers in <article> sections ... Headers are a semantic element that help computers understand the content. In general, header tags should follow rank order, but the most important is that the first header inside a section will serve as the title in a table of contents, etc, but since article sections stand alone as independent documents, I like the idea of explicitly starting with H1 tags. See: http://diveinto.html5doctor.com/semantics.html	2016-09-02 10:12:36 +03:00
Alan Orth	54ba5518d2	Use HTML5 <header> tags in articles ... The HTML5 <article> tag represents a complete, or self-contained, composition in a document. Headers are a semantic HTML5 element that helps computers understand the content.	2016-09-02 10:09:17 +03:00
Alan Orth	9b9226ca99	Use "|" for title separator instead of ndash ... A survey of a handful of websites shows that this is a more common separator of article and site title than the ndash.	2016-09-01 23:08:39 +03:00
Alan Orth	412cc18cf9	Start using Go 1.6's blocks ... Partials are nice, but blocks are a better base construct. Right now there is basically only layouts/_default/baseof.html that is doing most of the work. See: https://gohugo.io/templates/blocks	2016-09-01 17:37:27 +03:00
Alan Orth	4c68cf71b0	Move summary layout to posts ... The only content type we have is posts, so the summary type should be there.	2016-08-30 11:39:03 +03:00
Alan Orth	fb9376d24b	layouts: Move _default/single.html template to post archetype ... For now the only singles we need are posts, so it makes sense to move this there. I can make another single template for pages later.	2016-08-30 00:33:06 +03:00
Alan Orth	b164ceb53c	Add common HTML tags to head and footer so we can re-use them	2016-08-30 00:31:01 +03:00
Alan Orth	ea1da4a69e	Use HTML5 article tag for blog post summaries ... See: https://developer.mozilla.org/en/docs/Web/HTML/Element/article	2016-08-29 16:24:14 +03:00
Alan Orth	f76b5a069a	layouts: Improve usage of datetime ... Use the date format from the config, and print it in a time tag. See: https://golang.org/pkg/time/	2016-08-28 22:15:16 +03:00
Alan Orth	2bb1d6ecc0	First commit with initial theme ... Some file are empty (created by `hugo new theme`), but I've left them for reference later.	2016-08-28 16:22:32 +03:00