Yaml to html

.gitignore

@@ -60,3 +60,7 @@ Session.vim
 
 #********** IntelliJ files ******
 *.iml
+
+#********** Node JS ******
+package-lock.json
+node_modules

CONTRIBUTING.md

@@ -14,7 +14,6 @@ The way to contribute development effort and code to the project is via GitHub p
 
 Some general rules to follow:
 
--   [Fork](https://help.github.com/articles/fork-a-repo) the main project into your personal GitHub space to work on.
 -   Create a branch for each update that you're working on. These branches are often called "feature" or "topic" branches. Any changes that you push to your feature branch will automatically be shown in the pull request.
 -   Keep your pull requests as small as possible. Large pull requests are hard to review. Try to break up your changes into self-contained and incremental pull requests.
 -   The first line of commit messages should be a short (<80 character) summary, followed by an empty line and then any details that you want to share about the commit.

README.md

@@ -34,7 +34,7 @@ This page is used to plan and manage the work across the ga4gh-beacon repositori
 
 ## More information
 
-More information for developers is available on [our wiki](https://github.com/ga4gh-beacon/specification/wiki). A list of related tools and projects developed by the community is maintained on the [Resources](https://github.com/ga4gh-beacon/specification/wiki/Resources) page.  
+More information for developers is available on [our wiki](https://github.com/ga4gh-beacon/specification/wiki). A list of related tools and projects developed by the community is maintained on the [Resources](https://github.com/ga4gh-beacon/specification/wiki/Resources) page.
 
 ## Notify GA4GH of potential security flaw in specification
 

doc/README.md

@@ -0,0 +1,7 @@
+You can render the specification from YAML to HTML using
+
+	python yaml-to-html.py < ../beacon.yaml > beacon.html
+
+Open then `beacon.html` in your web browser.
+
+The output looks like a Swagger page.