Merge pull request #141 from ipfs/feature/toc

Add Table of Contents to long files

Author: RichardLitt

README.md

@@ -4,11 +4,21 @@
 [![](https://img.shields.io/badge/project-IPFS-blue.svg?style=flat-square)](http://ipfs.io/)
 [![](https://img.shields.io/badge/freenode-%23ipfs-blue.svg?style=flat-square)](http://webchat.freenode.net/?channels=%23ipfs)
 
-- [About](#about)
-- [Meetups](#meetups)
-- [Calendar](#calendar)
-- [Swag](#swag)
-- [People](#people)
+  - [About](#about)
+  - [Meetups](#meetups)
+    - [Berlin](#berlin)
+    - [Bratislava](#bratislava)
+    - [Copenhagen](#copenhagen)
+    - [Lisbon](#lisbon)
+    - [London](#london)
+    - [Paris](#paris)
+    - [Portland](#portland)
+    - [San Francisco](#san-francisco)
+    - [Seattle](#seattle)
+  - [Calendar](#calendar)
+  - [Swag](#swag)
+  - [People](#people)
+  - [Events calendar](#events-calendar)
 
 ## About
 

code-of-conduct.md

@@ -12,6 +12,18 @@ Towards this end, certain behaviors and practices will not be tolerated.
 - Abusive behavior is never tolerated.
 - Violations of this code may result in swift and permanent expulsion from the IPFS community.
 
+## Table of Contents
+
+- [Scope](#scope)
+- [Friendly Harassment-Free Space](#friendly-harassment-free-space)
+- [Reporting Violations of this Code of Conduct](#reporting-violations-of-this-code-of-conduct)
+- [Copyright Violations](#copyright-violations)
+- [Consequences](#consequences)
+- [Addressing Grievances](#addressing-grievances)
+- [Contact Info](#contact-info)
+- [Changes](#changes)
+- [Credit and License](#credit-and-license)
+
 ## Scope
 
 We expect all members of the IPFS community to abide by this Code of Conduct

contributing.md

@@ -15,15 +15,17 @@ helping us improve our community.
 
 ### Topics
 
-* [Security Issues](#reporting-security-issues)
-* [Reporting Issues](#reporting-issues)
-* [Dive Right In](#dive-right-in)
-* [Protocol Design](#protocol-design)
-* [Implementation Design](#implementation-design)
-* [Contribution Guidelines](#contribution-guidelines)
-* [Community Guidelines](#community-guidelines)
-* [Community Improvement](#community-improvement)
-* [Helping in other ways](#helping-in-other-ways)
+- [Topics](#topics)
+- [Security Issues](#security-issues)
+- [Dive Right In](#dive-right-in)
+- [Reporting Issues](#reporting-issues)
+- [Protocol Design](#protocol-design)
+- [Implementation Design](#implementation-design)
+- [Contribution Guidelines](#contribution-guidelines)
+- [Community Guidelines](#community-guidelines)
+- [Community Improvement](#community-improvement)
+- [Translations](#translations)
+- [Helping in other ways](#helping-in-other-ways)
 
 ### Security Issues
 

contribution-guidelines.md

@@ -1,5 +1,27 @@
 # Contribution Guidelines
 
+## Table of Contents
+
+- [Discuss big changes as Issues first](#discuss-big-changes-as-issues-first)
+- [Pull Requests always welcome](#pull-requests-always-welcome)
+- [Conventions](#conventions)
+  - [Go](#go)
+  - [JavaScript](#javascript)
+  - [Git](#git)
+  - [Commit messages](#commit-messages)
+    - [Subject line should not be more than 80 characters long](#subject-line-should-not-be-more-than-80-characters-long)
+    - [A "License" and a "Signed-off-by" trailers are required](#a-license-and-a-signed-off-by-trailers-are-required)
+    - [Commit message examples](#commit-message-examples)
+  - [Code](#code)
+  - [Tests](#tests)
+  - [Documentation](#documentation)
+  - [Pull Requests](#pull-requests)
+  - [Code Review](#code-review)
+  - [Rebasing](#rebasing)
+  - [Merge Approval](#merge-approval)
+  - [Labels](#labels)
+- [Credits](#credits)
+
 ## Discuss big changes as Issues first
 
 Significant improvements should be documented as GitHub issues before anybody starts to code. This gives other contributors a chance to point you in the right direction, give feedback on the design, and maybe point out if related work is under way.