On-the-fly Style Guide for Hyperledger Publications

Hyperledger Style Guide for Publications

  • Last updated September 23, 2019 

“I put together this style guide on-the-fly while working on publications for Hyperledger. When I encounter an inconsistency or a questionable term, I decide which way seems to make the most sense. I personally dislike the Chicago Manual of Style because it so often says ‘either approach is acceptable.’ I’m not saying these decisions are perfect and must stand forever, but I have followed these guidelines in the first four or five white papers I’ve revised and in several case studies I’ve written over the past year.”Gordon

White Paper Standards

USE CASES STANDARDS


COURSES AND ED X CHAPTER GUIDELINES


GITHUB BASICS


GRAPHIC SET STANDARDS


WEBINAR STANDARDS


Creating a Template


CII Best Practices


INSTRUCTOR LED TRAINING FORMATS
PRESENTATIONS GUIDELINES
RFP Standard Documentation

SELF PACED TRAINING FORMATS


 Developing Standards AND COLLECT CURRENT DOCUMENTATION 


To exit incubation, as project must have Sufficient user documentation
The project must including enough documentation for anyone to test or deploy any of the modules.

Requirements for BEST PRACTICE BADGE :

Best practices 

Project Checklist



Software documentation types