The Open Source Writing Stack
summary
Practical tool recommendations and workflow details decide whether to watch: real claims about what actually gets used and why, not abstract rhetoric. Notes show Markdown + Sublime Text for docs and blogs, pushes to GitHub and Read the Docs, or WordPress with Jetpack and Jekyll; version control (git) is mandatory; long projects use Google Docs for editors then layout via Scribus or LaTeX to produce PDF/Epub; don’t build a custom CMS.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:47Write
- 1:31Overview
- 2:25Documentation
- 5:04WordPress
- 6:54Version Control
- 10:49The dirty secret
- 12:15Adding images
- 13:50Resumes
- 15:52Open Source Tools
- 18:31Open Source in Writing
- 19:49The Big Wins
- 21:42Summary
related talks
41mMarkdownEditor: The Next Step in Working with Text
39mDesign Reviews, capturing context at speed
26mOpen Source Design: A Call to Arms
43mDocumentation is UX! - Change my mind
32mNarrative Infrastructure: Storytelling to Grow Open Source
27mBuilding a Markdown Editor from a design perspective
40mDocumentation as User Experience
54mOpen Source Design Contributions for Your OSS Project