https://github.com/jcs/no_color

Website data for no-color.org
https://github.com/jcs/no_color

Last synced: about 1 month ago
JSON representation

Website data for no-color.org

• Host: GitHub
• URL: https://github.com/jcs/no_color
• Owner: jcs
• Created: 2017-08-25T21:00:41.000Z (over 7 years ago)
• Default Branch: master
• Last Pushed: 2024-11-19T13:01:24.000Z (about 1 month ago)
• Last Synced: 2024-11-19T14:18:53.111Z (about 1 month ago)
• Language: HTML
• Homepage: https://no-color.org
• Size: 391 KB
• Stars: 264
• Watchers: 11
• Forks: 150
• Open Issues: 6
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# `NO_COLOR`

For information on the `NO_COLOR` standard, see

[no-color.org](http://no-color.org).

## Adding software

To add or update software on the `no-color.org` website, clone this Git

repository and update `index.md` with a line under the appropriate section,

keeping entries in alphabetical order.

The line must be formatted as:

```

For libraries:

| [Software Name](URL) | Short description | Language(s) | [YYYY-MM-DD / X.X.X](URL) |

For general software:

| [Software Name](URL) | Short description | [YYYY-MM-DD / X.X.X](URL) |

```

For the third/fourth field (the date and version number), the value should

refer to the first release of the software available with `NO_COLOR` support,

with a link to the release notes for that version.

If a version is not available, just include a date and link to the commit when

`NO_COLOR` support was added.

Make the description as short as possible, avoiding superfluous adjectives like

"the best ..." or "an all-new ...".

Once your entry is complete, commit your changes, push to your cloned repo, and

then submit a pull request to this repository.

If you do not have a GitHub account, e-mail your diff to

[[email protected]](mailto:[email protected]).

Once your change is merged, the `no-color.org` website will be automatically

rebuilt within a few minutes.

## Testing changes

If you are making extensive changes to the output and want to verify them in a

browser before committing, you can setup a Jekyll environment with:

	no_color$ bundle install

	no_color$ bundle exec jekyll serve

And then visit

[http://127.0.0.1:4000/](http://127.0.0.1:4000/).