/classic-guide

A guide moving forward from hardfork to freedom

Primary LanguagePython

source/img/ethereum-classic-documentation-logo.png

Classic-Guide

Gitter readthedoc

The Ethereum Classic Guide is the reference documentation accompanying the hard-fork of the Ethereum project.

Hosted on ReadTheDocs

HOW YOU CAN HELP

Classic Documentation Initiative

It doesn't matter if you are a beginner or an expert, there are many ways to help.

Write Content to the Guide

Help transfer and update content from the Ethereum Wiki, Ethereum Frontier Guide, the Ethereum Stack Exchange, Ethereum Homestead Guide or any other reputable source to relevant pages of the Classic guide. Alternatively, write your own content for the guide based on experience.

Make sure the documentation you are porting over is still accurate and follows our guidelines for the Classic docs. (http://ethereum-classic-guide.readthedocs.io/en/latest/about.html)

Review What Has Been Written

Have a look at our guide and give us feedback by visiting our Gitter Chatroom (https://gitter.im/ethereumclassic/classic-guide) or submit a pull request or issue to this repo. Too EZ.

What's In It For Me?

Your name will forever be immortalized, both in my heart and on the Contributors page in the guide. As a side effect, you may also get those good feels that you get when you help improve documentation :-)

GETTING STARTED

This project uses Sphinx (http://www.sphinx-doc.org/en/stable/index.html) to build html that is published to Read the Docs. To run this documentation on your computer, you should do the following:

Prerequisites

  • Python 2.6 or later
  • git

Install Sphinx, etc

For OSX/Linux users (based on instructions here: https://read-the-docs.readthedocs.org/en/latest/getting_started.html)

  • From command line: sudo pip install sphinx

For Windows users:

Get source code

Build and view html

  • In a terminal window, go to your classic-guide directory.
  • make html
  • cd build/html
  • open index.html (open in web browser)
  • Tip: each time you run make html, just reload your browser to view changes

RESOURCES

Classic

Homestead and legacy docs

Read the Docs and Sphinx

Directory structure

homestead-guide
  build    - workdir, not commited to repo
  source   - actual content in rst
    conf.py - sphinx configuration
  old-docs-for-reference (Frontier era stuff)
    wiki    - the legacy wiki
    gitbook - the legacy gitbook resources (converted to rst)
  make.bat - windows command to build docs
  Makefile - platforms with make to build docs

Roadmap for Classic Guide

  • fork homestead guide from ethereum
  • compile/deploy on readthedocs
  • include cheatsheat, rst/sphinx/readthedocs resources
  • reach out to community reddit - classic documentation initiative
  • allocate chapters to people (ideally author and reviewer)
  • migrate old wiki under frontier/wiki (all md files converted to rst)
  • migrate old frontier-guide content under frontier/gitbook (all md content converted to rst)
  • script to annotate entire wiki with legacy warning

Strategy for migrating old Homestead-guide content (Old)

  • temporaritly include resources about the documentation project within the book itself * rst cheatsheet * rst/sphinx/readthedocs resources * compilation/deployment instructions * link to issues and process * style guide, conventions
  • include the rst conversion of the wiki
  • include the rst conversion of the gitbook