Content Creation

The Proposal

Author(s)

Reviewer(s)

Publisher(s)

Create a Mardown file

Review a Mardown file

Add Media Assets

Review Media Assets

Ask for Changes

Approve the final version

Adapt the content

Create a PR

Modify the PR

Schedule publication

The process

• Transparency 🎯 
  Who did what? Who reviewed? What is pending? → Git
• Automation (CI) ⚡
  Notifications, linters, checks, deployments → GitHub Actions
• Semantic content 📝
   plain text + Semantic → Markdown
• Same tools ⚙️
  Same workflow as coding (IDE, Git) or directly GitHub UI
• All in one 📌
  Content backlog + updates after publication → GitHub Issues & Projects

• Cultural shift 👥
  Adapting to new tools and workflows (Git, Markdown, PRs)
• Website automation gap 🔄
  Need to configure pipelines to publish content automatically (optional).
• Semantic content 📝
  Markdown is powerful, but less visual than WYSIWYG editors (iframes, etc...).
• Binary files limitation 📂
  Not ideal for large assets like PDFs, videos, or heavy images.

Markdown 101

• Plain text format 📝 – Easy to read & edit without special software.

• Lightweight syntax ⚡ – Few symbols for formatting (#, *, []()).

• Portable & future-proof 🔮 – Can be converted to HTML, PDF, Word, etc.

• Focus on content 🎯 – Write without distractions from styling.

• Developers love it 👩‍💻 – Same format used in READMEs, docs, wikis.

• Works anywhere 🌍 – Supported by GitHub, GitLab, blogs, static site generators.

Key Takeaways

Resources

• Complete list of github markdown emoji markup
• Basic writing and formatting syntax
• Markdown Cheatsheet
  
• Learn GitHub-Flavored Markdown Syntax and Formatting – With Examples
• GitHub Flavored Markdown Spec

Real-World Examples

Node.js

Example PR#7675

YEOMAN

Example PR#858

Express

Example PR#1940

DEMO TIME!