Genry Leyva González @genrylg www.linkedin.com/in/genrylg [email protected] Ops Team at 

DOCs as Code 

User’s Manual Install Manual README Administration Manual Contribution Guide API Specification 

No content

No content

 Poor Collaboration  Lack of versioning  Documentation at the end  Different cadence between release and doc  Developers not involved  Difficult to obtain different file formats 

DOCs as Code 2007 2008 2009 … 2014 2015 2016 collaboration developers involved review & merge testing & publishing semantic versioning 

Next In Progress … UAT Pending for Doc Being Documented Doc Ready Staging feature feature feature feature feature feature feature feature feature feature feature feature feature Documentation Stages 

Next In Progress … Dev Done Pending for Doc Being Documented Doc Ready Staging feature feature feature feature feature feature feature feature feature STEP 1 STEP 2 STEP 3 STEP 4 STEP 5 feature feature feature feature Every feature is documented as part of a delivery process Definition of DONE 

Create feature branch for a new feature / user story Write new or edit existing documentation Create pull request Automatic Testing Review Merge to the develop branch Regenerate documentation files Merge Trigger of CI plan to publish CREATION PROCESS 

Branch by feature Git on Gitlab Continuous Integration 

Semantic Versioning 

lightweight markup language plain text formatting it can be converted to many formats 

PANDOC IN: more than 20 OUT: more than 30 CLI 

Doc Proyects in Gitlab 

No content

 Simple way of writing documents  Collaboration  Writers have a similar workflow to developer 

 Based on developers' infrastructure  Ops team as enablers  Documentation delivered along with a product 

No content

genrylg genrylg DOCs as Code