All Projects → livioribeiro → Cargo Readme

livioribeiro / Cargo Readme

Licence: other
Generate README.md from docstrings

Programming Languages

rust
11053 projects

Labels

Projects that are alternatives of or similar to Cargo Readme

Readme styles
Minimal README.rst and README.md template for Github projects.
Stars: ✭ 60 (-68.59%)
Mutual labels:  readme
Goreadme
Generate readme file from Go doc. Now available with Github actions!
Stars: ✭ 113 (-40.84%)
Mutual labels:  readme
Markdown readme
Markdown - you can mark up titles, lists, tables, etc., in a much cleaner, readable and accurate way if you do it with HTML.
Stars: ✭ 146 (-23.56%)
Mutual labels:  readme
Readme Md Generator
📄 CLI that generates beautiful README.md files
Stars: ✭ 9,184 (+4708.38%)
Mutual labels:  readme
Awesome Readme
A curated list of awesome READMEs
Stars: ✭ 10,895 (+5604.19%)
Mutual labels:  readme
Readme Model
💾 A beautiful readme model for you to put in your projects.
Stars: ✭ 131 (-31.41%)
Mutual labels:  readme
Iampavangandhi
Hey 👋, Glad to see you here! Check out this repository to learn more about me 🤓. You can also use it to make your awesome GitHub README ✨ (Don't Just Fork, Star Too 😅)
Stars: ✭ 51 (-73.3%)
Mutual labels:  readme
Ios Readme Template
README.md template for your iOS open-source projects. Inspired by @dbader's readme-template
Stars: ✭ 170 (-10.99%)
Mutual labels:  readme
Rebecca
Rebecca is a readme generator for Go
Stars: ✭ 91 (-52.36%)
Mutual labels:  readme
Recruitment
Kyashの採用応募者向けの公開情報をまとめたリポジトリ
Stars: ✭ 146 (-23.56%)
Mutual labels:  readme
Readme Template
A Readme Template For Tomorrow's Opensource
Stars: ✭ 69 (-63.87%)
Mutual labels:  readme
Jsdoc To Markdown
Generate markdown documentation from jsdoc-annotated javascript
Stars: ✭ 1,199 (+527.75%)
Mutual labels:  readme
Bornmay
Awesome Github Profile Readme. Github ReadMe Github Profile Readme Dynamic Github ReadMe Dynamic Github Profile ReadMe. Please Star and Fork
Stars: ✭ 140 (-26.7%)
Mutual labels:  readme
Awesome Readme
A guide to writing an Awesome README. Read the full article in Towards Data Science.
Stars: ✭ 65 (-65.97%)
Mutual labels:  readme
Generator Standard Readme
Scaffold out a Standard Readme
Stars: ✭ 150 (-21.47%)
Mutual labels:  readme
Feedmereadmes
Free README editing+feedback to make your open-source projects grow. See the README maturity model to help you keep going.
Stars: ✭ 1,064 (+457.07%)
Mutual labels:  readme
Verb Generate Readme
Generate your project's readme with verb. Requires verb v0.9.0 or higher.
Stars: ✭ 127 (-33.51%)
Mutual labels:  readme
Novatorem
Dynamic realtime profile ReadMe linked with spotify
Stars: ✭ 176 (-7.85%)
Mutual labels:  readme
Awesome Github Profile Readme Templates
This repository contains best profile readme's for your reference.
Stars: ✭ 163 (-14.66%)
Mutual labels:  readme
Svg Banners
Styled banners for your Readme made with html/css in SVG !!
Stars: ✭ 145 (-24.08%)
Mutual labels:  readme

Crates.io Workflow Status

cargo-readme

Generate README.md from doc comments.

Cargo subcommand that extract documentation from your crate's doc comments that you can use to populate your README.md.

Installation

cargo install cargo-readme

Motivation

As you write documentation, you often have to show examples of how to use your software. But how do you make sure your examples are all working properly? That we didn't forget to update them after a breaking change and left our (possibly new) users with errors they will have to figure out by themselves?

With cargo-readme, you just write the rustdoc, run the tests, and then run:

cargo readme > README.md

And that's it! Your README.md is populated with the contents of the doc comments from your lib.rs (or main.rs).

Usage

Let's take the following rust doc:

//! This is my awesome crate
//!
//! Here goes some other description of what it is and what is does
//!
//! # Examples
//! ```
//! fn sum2(n1: i32, n2: i32) -> i32 {
//!   n1 + n2
//! }
//! # assert_eq!(4, sum2(2, 2));
//! ```

Running cargo readme will output the following:

[![Build Status](__badge_image__)](__badge_url__)

# my_crate

This is my awesome crate

Here goes some other description of what it is and what is does

## Examples
```rust
fn sum2(n1: i32, n2: i32) -> i32 {
  n1 + n2
}
```

License: MY_LICENSE

Let's see what's happened:

  • a badge was created from the one defined in the [badges] section of Cargo.toml
  • the crate name ("my-crate") was added
  • "# Examples" heading became "## Examples"
  • code block became "```rust"
  • hidden line # assert_eq!(4, sum2(2, 2)); was removed

cargo-readme also supports multiline doc comments /*! */ (but you cannot mix styles):

/*!
This is my awesome crate

Here goes some other description of what it is and what is does

```
fn sum2(n1: i32, n2: i32) -> i32 {
  n1 + n2
}
```
*/

If you have additional information that does not fit in doc comments, you can use a template. Just create a file called README.tpl in the same directory as Cargo.toml with the following content:

{{badges}}

# {{crate}}

{{readme}}

Current version: {{version}}

Some additional info here

License: {{license}}

The output will look like this

[![Build Status](__badge_image__)](__badge_url__)

# my_crate

Current version: 3.0.0

This is my awesome crate

Here goes some other description of what it is and what is does

## Examples
```rust
fn sum2(n1: i32, n2: i32) -> i32 {
  n1 + n2
}
```

Some additional info here

License: MY_LICENSE

By default, README.tpl will be used as the template, but you can override it using the --template to choose a different template or --no-template to disable it.

License

Licensed under either of

at your option.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].