standard-readme - Standard Readme Style

  •        60

Standard Readme is designed for open source libraries. Although it’s historically made for Node and npm projects, it also applies to libraries in other languages and package managers. Standard Readme started with the issue originally posed by @maxogden over at feross/standard in this issue, about whether or not a tool to standardize readmes would be useful. A lot of that discussion ended up in zcei's standard-readme repository. While working on maintaining the IPFS repositories, I needed a way to standardize Readmes across that organization. This specification started as a result of that.



Related Projects

apex-mdapi - Apex Wrapper for the Salesforce Metadata API

  •    Apex

In addition to the documentation in this README, the following blogs also cover the library. This API mirrors as much as possible the API types and operations described in the standard documentation. The behaviour and functionality provided is also as described in the Salesforce documentation, in terms of what metadata is available and accessable via the specific operations.

hana - Your standard library for metaprogramming

  •    C++

You can browse the documentation online at The documentation covers everything you should need including installing the library, a tutorial explaining what Hana is and how to use it, and an extensive reference section with examples. The remainder of this README is mostly for people that wish to work on the library itself, not for its users. After issuing this, doc/html will contain exactly the same static website that is available online. Note that doc/html is automatically ignored by Git so updating the documentation won't pollute your index.

grip - Preview GitHub Markdown files like Readme locally before committing them.

  •    Python

Render local readme files before sending off to GitHub. Grip is a command-line server application written in Python that uses the GitHub markdown API to render a local readme file. The styles come directly from GitHub, so you'll know exactly how it will appear. Changes you make to the Readme will be instantly reflected in the browser without requiring a page refresh.

readme-checklist - A checklist for writing READMEs

  • is a checklist to help you write a README file that helps readers feel confident about your project. If you write a README by following the checklist, then your readers may more easily identify, evaluate, use, and engage with your project. Unlike README templates, this checklist helps you write the most important things first, not only what appears first in the file. You can use the checklist for both closed- and open-source projects. For more about how this checklist was created and its use, see the talk I gave at Write the Docs NA 2016, Write the Readable README.

rubber-docker - A workshop on Linux containers: Rebuild Docker from Scratch

  •    Python

Use the provided slides while advancing through the levels, adding more features to your container. Remember to go over each level's readme, and if things get rough - you can always find the solution for level N in the level N+1 skeleton. Not all the necessary system calls are exposed in python's standard library. In addition, we want to preserve the semantics of the system calls and use them as if we were writing C. We therefore wrote a python module called linux (take a look at linux.c) which exposes the relevant system calls. Have a look at the module documentation for more info.

feedmereadmes - Free README editing+feedback to make your open-source projects grow


Go here for relevant articles, talks, and projects that we find inspiring. Add your own favorites via pull request. Even if you don't agree with Preston-Warner, you can still make your READMEs user-friendlier. Feedmereadmes is here to help. We define "user" to include non-developers and aim to tell compelling stories. "[C]ode isn't self-documenting" is one of our mantras, as per Mike Jang's 2015 OSCON talk offering Ten Steps to Better READMEs.

the-turing-way - Host repository for The Turing Way: a how to guide for reproducible data science

  •    TeX

This file in also available in Dutch (README-Dutch), French (, German (, Indonesian (README-Indonesian), Italian (README-Italian), Korean (README-Korean), Portuguese (README-Portuguese), and Spanish (README-Spanish) (listed alphabetically). The Turing Way is a lightly opinionated guide to reproducible data science. You can read it here: You're currently viewing the project GitHub repository where all of the bits that make up the guide live, and where the process of writing/building the guide happens.

hall-of-fame - :trophy: Show some love to your contributors! A widget for your repo README

  •    Python

Hall-of-fame helps you show some love to your contributors. It automatically highlights your new, trending, and top contributors, and updates every hour. You can put this widget anywhere inside your README, e.g. to "Contributing" section. No maintenance is required. Every hour, Hall-of-fame looks into recent commits of your repo using GitHub API. It then selects three categories of contributors: new (those who made their first commit to your repo in the last 7 days), trending (those with most commits in the last 7 days), and top (those with most commits of all time). It then selects up to three new contributors, up to 4 trending contributors, and if total is less than 7, it fill up the remaining spots with top contributors.

subhask - Type safe interface for working in subcategories of Hask

  •    Haskell

SubHask is a radical rewrite of the Haskell Prelude. The goal is to make numerical computing in Haskell fun and fast. The main idea is to use a type safe interface for programming in arbitrary subcategories of Hask. For example, the category Vect of linear functions is a subcategory of Hask, and SubHask exploits this fact to give a nice interface for linear algebra. To achieve this goal, almost every class hierarchy is redefined to be more general. SubHask is a work in progress. This README is intended to be a "quick start guide" to get you familiar with the current status and major differences from standard Haskell.

rio - A standard library for Haskell

  •    Haskell

NOTE This code is currently in prerelease status, and has been released as a tech preview. A number of us are actively working on improving the project and getting it to a useful first release. For more information, see the description of goals and the issue tracker for discussions. If you're reading this file anywhere but Github, you should probably read the Github version instead, which will be more up to date. You're free to use any subset of functionality desired in your project. This README will guide you through using rio to its fullest extent.

agda - Agda is a dependently typed programming language / interactive theorem prover.

  •    Haskell

Note that this README is only about Agda, not its standard library. See the Agda Wiki for information about the library.

node-coveralls - lcov posting to

  •    Javascript support for node.js. Get the great coverage reporting of and add a cool coverage button ( like the one above ) to your README. This script ( bin/coveralls.js ) can take standard input from any tool that emits the lcov data format (including mocha's LCov reporter) and send it to to report your code coverage there.

libsass-python - A straightforward binding of libsass for Python

  •    Python

This package provides a simple Python extension module sass which is binding LibSass (written in C/C++ by Hampton Catlin and Aaron Leung). It's very straightforward and there isn't any headache related Python distribution/deployment. That means you can add just libsass into your's install_requires list or requirements.txt file. Need no Ruby nor Node.js. libsass requires some features introduced by the recent C++ standard. You need a C++ compiler that support those features. See also libsass project's README file.

tui.editor - πŸžπŸ“ Markdown WYSIWYG Editor. GFM Standard + Chart & UML Extensible.

  •    TypeScript

TOAST UI Editor provides Markdown mode and WYSIWYG mode. Depending on the type of use you want like production of Markdown or maybe to just edit the Markdown. The TOAST UI Editor can be helpful for both the usage. It offers Markdown mode and WYSIWYG mode, which can be switched any point in time. Today CommonMark is the de-facto Markdown standard. GFM (GitHub Flavored Markdown) is another popular specification based on CommonMark - maintained by GitHub, which is the Markdown mostly used. TOAST UI Editor follows both CommonMark and GFM specifications. Write documents with ease using productive tools provided by TOAST UI Editor and you can easily open the produced document wherever the specifications are supported.

Read: a "GNU Make"-like utility for viewing Readme files

  •    C

Read is a simple program to easily load and read README files on a UNIX-compliant system. It works in a similar way to GNU Make by searching a directory for a compatible file, in this case a Readme file, and loading it for reading using a text editor or viewer.

We have large collection of open source products. Follow the tags from Tag Cloud >>

Open source products are scattered around the web. Please provide information about the open source projects you own / you use. Add Projects.