Key Messages - graphitefriction/oscon-2013-docs-workshop GitHub Wiki
On this page, we’ve identified the key messages, in the form of phrases, quotes and facts, that we want communicate in the workshop.
Everything you type in a terminal is eventually a task you don’t have to do, because it can be automated.
The website layout should conform to the content (and its look and feel), which adheres to the document as a first-class citizen principle.
Every minute an editor spends managing presentational tweaks is one they can’t spend on critical stories.
— Jeff Eaton
When Editors Design
When Editors Design
Common article elements such as call-out warnings and captioned images were too complex for the WYSIWYG editor’s built-in array of buttons and styles. Conscientious editors tried to duplicate the precise markup used by the website’s CSS but often made errors. Others gave up and tried to duplicate the appearance of those styles with the WYSIWYG editor’s table, font-color and image-embedding tools.
— Jeff Eaton
When Editors Design
When Editors Design
I do not believe that on-page, in-context editing should be the primary edit mode of a CMS.
— Deane Barker
on Twitter
on Twitter
[E]very piece information is too valuable to hinder its educational spreading by choosing the wrong distribution format. To reach a maximum of spread by the minimum of effort you’ll have to use a great creational pattern. And that is where AsciiDoc hits the bull’s eye. The combination of easily understandable consistent markup and merely endless formatting power provide a perfect base format for every content distribution channel you can imagine.
And THAT … is AsciiDoc.
— Alexander Heusingfeld