Reference Resources

Awestruct + Asciidoctor Blogs & Tutorials

• Getting Started with Awestruct (official guide)

• Awestruct with Asciidoctor on Windows with JRuby

• Setting Up an Awestruct-based Blog

• What is AsciiDoc? Why do we need it?

• AsciiDoc Syntax Quick Reference

• Why AsciiDoc over Markdown?

Structured Content

• Adapting Ourselves to Adaptive Content (video) a must see!

• When Editors Design: Controlling Presentation in Structured Content (good content can also be found in the comments)

• Don’t Let Paper Paradigms Drive Your Digital Strategy

• Inline Editing and the Cost of Leaky Abstractions

• Comments by Alexander Heusingfeld about AsciiDoc promoting reusable content

Web Publishing

• The Limitations of GitHub for Writers (multi-part series)

• GitHub as a Blogging Platform

• Princeton Academics Form GitHub Book Club

• Writing an O’Reilly book with AsciiDoc and GitHub (video)

• GitHub Flow in the Browser

• Why We Open Sourced Our Documentation (and other related posts)

• How To Use GitHub Pages To Make Web Sites While Learning Code

Layout, Design and Readability

• Twitter Bootstrap vs Foundation 4: Which one is right for you?

• More Meaningful Typography

• The 100% Easy-2-Read Standard

• Responsive Typography, The Basics

• Practical Typography

Insights on Documentation

• A Beginner’s Guide to Docs

• GitHub Documentation Study (specifically Dan’s response)

• 13 Things People Hate About Your Open Source Docs

• PlDoc version 2 online and in GIT
  Commentary on why it’s important to have well-specified documentation languages, not just simpler syntax.

• Best. Docs. Ever. 6 Tips to Writing Documentation

Communities

• Static Site Generators - Google+ Community

Books

• Content Strategy for Mobile by Karen McGrane

• Content Strategy for the Web by Kristina Halvorson and Melissa Rach

• Content Everywhere by Sara Wachter-Boettcher

Setup

• Fedora Gemfile Checker - Compare a Bundler Gemfile to the Fedora Ruby Stack

Other Tools

• Shit For Making Websites

Concepts

Editing form != final appearance

killing the idea that the "editing form" should be a perfect reflection of the content’s final appearance.

WYSIWYM

assistive editing tools that save semantic markup rather than visual/presentation oriented markup.