Core Docs: Sentencing WordPress to 11-years-to-life

25
CORE DOCS: SENTENCING WORDPRESS TO 11-YEARS-TO-LIFE

description

Core docs extend far beyond maintaining dated Codex pages and writing inline comments. In fact, even the way core code is written is a contributor to core documentation. And in all the ways we contribute docs, we need to ensure they stand the test of time. This talk takes a stroll through the docs roadmap devised Summer 2013 and how that’s progressing. We’ll examine the diminished role the Codex will take going forward, as well as highlight some exciting initiatives coming into the fold — including the handbooks, code reference, and more.

Transcript of Core Docs: Sentencing WordPress to 11-years-to-life

Page 1: Core Docs: Sentencing WordPress to 11-years-to-life

CORE DOCS: SENTENCING WORDPRESS

TO 11-YEARS-TO-LIFE

Page 2: Core Docs: Sentencing WordPress to 11-years-to-life

WHAT IS CORE DOCUMENTATION?

• The Codex

• Inline docs/commenting

• The code itself

• Docs as “developer experience”

Page 3: Core Docs: Sentencing WordPress to 11-years-to-life

CINCINNATI 2013

Page 4: Core Docs: Sentencing WordPress to 11-years-to-life

CINCINNATI MEETUP

• Survey analysis

• Brainstorming

• Roadmap

Page 5: Core Docs: Sentencing WordPress to 11-years-to-life

CODEX SURVEY

• Incomplete, outdated, wrong

• Tutorials and examples

• StackExchange/StackOverflow

Page 6: Core Docs: Sentencing WordPress to 11-years-to-life

LIKE DON’T LIKE

Page 7: Core Docs: Sentencing WordPress to 11-years-to-life

CODEX != SUSTAINABLE

Page 8: Core Docs: Sentencing WordPress to 11-years-to-life

ROADMAP

http://make.wordpress.org/docs/2013/06/19/docs-sprint-results-and-roadmap/

Page 9: Core Docs: Sentencing WordPress to 11-years-to-life

ROADMAP

• Constrain the scope of docs to the core project

• Reduce and refine

• Separate developer from user documentation

Page 10: Core Docs: Sentencing WordPress to 11-years-to-life

1. DEVELOPER HUB

Page 11: Core Docs: Sentencing WordPress to 11-years-to-life

1. DEVELOPER HUB

• Code Reference

• Standards/Parser

• Hook Docs

• Code Reference Theme

Page 12: Core Docs: Sentencing WordPress to 11-years-to-life

CODE REFERENCE

Page 13: Core Docs: Sentencing WordPress to 11-years-to-life

EXAMPLE EXAMPLE

Page 14: Core Docs: Sentencing WordPress to 11-years-to-life

+

2. HANDBOOKS

Page 15: Core Docs: Sentencing WordPress to 11-years-to-life

2. HANDBOOKS

• Plugin, theme developers

• Polyglots, users, etc.

• Rewrite, focus the content

• Reorganize

Page 16: Core Docs: Sentencing WordPress to 11-years-to-life
Page 17: Core Docs: Sentencing WordPress to 11-years-to-life

3. SUPPORT HUB

Page 18: Core Docs: Sentencing WordPress to 11-years-to-life

3. SUPPORT HUB

• Getting Started, task-based guides

• Knowledge base

• Identifying cross-over content

Page 19: Core Docs: Sentencing WordPress to 11-years-to-life

4. DISMANTLING THE CODEX

Page 20: Core Docs: Sentencing WordPress to 11-years-to-life

4. DISMANTLING THE CODEX

• Migrate remaining content to inline docs and explanations

• Massive 301 redirect

Page 21: Core Docs: Sentencing WordPress to 11-years-to-life

WHAT’S NEXT

Page 22: Core Docs: Sentencing WordPress to 11-years-to-life

SHINY THINGS

• Examples voting

• Explanations

• Hook aliases

• Documenting default arguments

Page 23: Core Docs: Sentencing WordPress to 11-years-to-life

SHINY IDEAS

• Adopt the JSDoc3 standard

• Parsed JavaScript docs

• Extended references

• and …

Page 24: Core Docs: Sentencing WordPress to 11-years-to-life
Page 25: Core Docs: Sentencing WordPress to 11-years-to-life

Drew Jaynes | @DrewAPictureSlides: http://drewf.us/wcnyc