Mirrors/httpstatuses
1
0
Fork 0
mirror of https://github.com/rmaake1/httpstatuses.git synced 2024-07-05 11:36:37 +02:00
Code Issues Packages Projects Releases Wiki Activity
Mirror of: https://github.com/rmaake1/httpstatuses
81 Commits 1 Branch 1 Tag 730 KiB
SCSS 35.6%
Pug 32.4%
JavaScript 25.1%
Shell 6.9%
e81084ffcf
Go to file
Samuel Ryan e81084ffcf Merge pull request #28 from citricsquid/metalsmith 
Version 2
2015-11-07 14:58:48 +00:00
contents Emphasises opening paragraph and separates from further information with border 2015-11-07 14:55:32 +00:00
templates Fixes missing title tag from layout 2015-11-06 23:29:42 +00:00
.gitignore Listens to the master branch for deploys 2015-11-07 14:55:55 +00:00
bower.json builds site using Metalsmith 2015-11-06 20:40:58 +00:00
build.js Adds (ugly, ugly) favicon 2015-11-06 22:29:11 +00:00
circle.yml Listens to the master branch for deploys 2015-11-07 14:55:55 +00:00
deploy.sh Adjusts file permissions to allow deploy to run 2015-11-06 22:07:30 +00:00
LICENSE Removes old project files 2015-11-01 18:09:40 +00:00
package.json Adds asset revisioning 2015-11-06 21:36:13 +00:00
README.md Adds contribution guidelines to the README 2015-11-07 06:25:30 +00:00
Vagrantfile Adds development environment using Vagrant 2015-11-01 18:32:59 +00:00

README.md

httpstatus.es

httpstatus.es is an easy to reference database of HTTP Status Codes with their definitions and helpful code references.

Contributing

All contributions are welcome! If you have an idea to improve the website please submit a pull request or create an issue, or provide your thoughts on any open issues.

Each status code lives in a Markdown file at contents/codes, the easiest way to submit changes is via the GitHub editor. When contributing changes to the status codes please be mindful of the following:

  • Soft line length of 80 for Markdown
  • Markdown links should be used as references instead of inline
  • If an RFC or external document is referenced, make the reference a link
  • Source information on a status code from the most recent standards available (Status Code standards directory is available on iana.org)
  • The opening paragraph of a status code should describe the meaning, following paragraphs can describe implementation
  • Don't edit the meaning of descriptions, but formatting and structural changes are a-okay
  • Don't double-space after a period, and remove any examples of it
  • If the description references a section in the current RFC, always add the RFC identifier. For example "Section 6.6" should become "RFC1234 Section 6.6"