Remove blockquote from short description

Closes #22
This commit is contained in:
Richard Littauer 2019-12-10 10:12:43 -05:00
parent 8c5f901d7e
commit 0211114475
7 changed files with 7 additions and 7 deletions

View File

@ -1,6 +1,6 @@
The MIT License (MIT) The MIT License (MIT)
Copyright (c) 2017 Richard Littauer Copyright (c) 2017-2019 Richard Littauer
Permission is hereby granted, free of charge, to any person obtaining a copy Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal of this software and associated documentation files (the "Software"), to deal

View File

@ -2,7 +2,7 @@
[![standard-readme compliant](https://img.shields.io/badge/readme%20style-standard-brightgreen.svg?style=flat-square)](https://github.com/RichardLitt/standard-readme) [![standard-readme compliant](https://img.shields.io/badge/readme%20style-standard-brightgreen.svg?style=flat-square)](https://github.com/RichardLitt/standard-readme)
> 标准 Readme 样式 标准 Readme 样式
README 文件是人们通常最先看到的第一个东西。它应该告诉人们为什么要使用、如何安装、以及如何使用你的代码。README 文件标准化能够使得创建和维护 README 文件更加简单。 毕竟,要写好一个文档不是那么容易的。 README 文件是人们通常最先看到的第一个东西。它应该告诉人们为什么要使用、如何安装、以及如何使用你的代码。README 文件标准化能够使得创建和维护 README 文件更加简单。 毕竟,要写好一个文档不是那么容易的。

View File

@ -2,7 +2,7 @@
[![standard-readme compliant](https://img.shields.io/badge/readme%20style-standard-brightgreen.svg?style=flat-square)](https://github.com/RichardLitt/standard-readme) [![standard-readme compliant](https://img.shields.io/badge/readme%20style-standard-brightgreen.svg?style=flat-square)](https://github.com/RichardLitt/standard-readme)
> Standard Readme Style A standard style for README files
Your README file is normally the first entry point to your code. It should tell people why they should use your module, how they can install it, and how they can use it. Standardizing how you write your README makes creating and maintaining your READMEs easier. Great documentation takes work! Your README file is normally the first entry point to your code. It should tell people why they should use your module, how they can install it, and how they can use it. Standardizing how you write your README makes creating and maintaining your READMEs easier. Great documentation takes work!

View File

@ -7,7 +7,7 @@
[![license](https://img.shields.io/github/license/:user/:repo.svg)](LICENSE) [![license](https://img.shields.io/github/license/:user/:repo.svg)](LICENSE)
[![standard-readme compliant](https://img.shields.io/badge/readme%20style-standard-brightgreen.svg?style=flat-square)](https://github.com/RichardLitt/standard-readme) [![standard-readme compliant](https://img.shields.io/badge/readme%20style-standard-brightgreen.svg?style=flat-square)](https://github.com/RichardLitt/standard-readme)
> This is an example file with maximal choices selected. This is an example file with maximal choices selected.
This is a long description. This is a long description.

View File

@ -1,6 +1,6 @@
# Title # Title
> This is an example file with default selections. This is an example file with default selections.
## Install ## Install

View File

@ -1,7 +1,7 @@
{ {
"name": "standard-readme-spec", "name": "standard-readme-spec",
"version": "1.1.5", "version": "1.1.5",
"description": "Readme Standard Style", "description": "A standard style for README files",
"bin": "cat.sh", "bin": "cat.sh",
"repository": { "repository": {
"type": "git", "type": "git",

View File

@ -78,7 +78,7 @@ _Note: This is only a navigation guide for the specification, and does not defin
**Requirements:** **Requirements:**
- Must not have its own title. - Must not have its own title.
- Must be less than 120 characters. - Must be less than 120 characters.
- Must start with `> ` - Must not start with `> `
- Must be on its own line. - Must be on its own line.
- Must match the description in the packager manager's `description` field. - Must match the description in the packager manager's `description` field.
- Must match GitHub's description (if on GitHub). - Must match GitHub's description (if on GitHub).