linux中的medium
Update: Instead of publishing on Medium, we now run our own self-hosted open-source tool where we're publishing articles to an even larger audience.
更新：现在，我们不再在Medium上发布，而是运行自己的自托管开源工具，在其中将文章发布给更大的受众。
You can read more about our move on this forum thread, which includes instructions for how you can apply to become an author, read this style guide.
您可以通过此论坛主题详细了解我们的举动，其中包括有关如何申请成为作者的说明，请阅读此样式指南 。
What follows is for historical purposes if you're curious.
如果您好奇的话，以下内容出于历史目的。
Our open source community runs Medium’s largest technical publication. If you write about development, design, or data science — and are looking for an audience — this is a good place to get published.
我们的开源社区经营Medium最大的技术出版物。 如果您撰写有关开发，设计或数据科学的文章，并且正在寻找读者，那么这是发布的好地方。
freeCodeCamp is an open source community with thousands of contributors, mentors, teachers, and event organizers.
freeCodeCamp是一个开源社区，拥有成千上万的贡献者，导师，教师和活动组织者。
More than a million people learn to code using freeCodeCamp each month, and thousands of us have worked through the 1,200-hour curriculum and gotten their first developer jobs.
每月有超过一百万的人学习使用freeCodeCamp编写代码，而我们中成千上万的人已经完成了1200小时的课程，并获得了他们的第一个开发人员职位。
We’re a nonprofit. You can help us pay for servers and other costs by becoming a supporter.
我们是非营利组织。 您可以通过成为支持者来帮助我们支付服务器和其他费用。
Here’s what all this means for you as a writer:
这对您作为作家意味着什么：
- We won’t plaster your story with advertisements, or put it behind a paywall (or “email wall” or anything — no weird tricks). 我们不会在广告中贴上您的故事，也不会将其放在付费专栏(或“电子邮件专栏”之类的东西–没有奇怪的花招)后面。
- You can include links to your own blog or service, and even affiliate links, as long as it’s done tastefully and transparently. 您可以包括指向您自己的博客或服务的链接，甚至包括会员链接，只要它是高雅而透明地完成的。
- Your stories are yours. We don’t lay any claim to them. You can cross-post them wherever you want. Other newspapers and websites may even approach you about syndicating them or translating them. That’s fine with us. We just ask that — since we invest a lot of time in editing and promoting your stories — you don’t remove them from our Medium publication once we’ve published them. 你的故事是你的。 我们对他们没有任何要求。 您可以将它们交叉张贴在任何地方。 其他报纸和网站甚至可能会与您联系以组织或翻译它们。 对我们来说很好。 我们只是要问一下-由于我们投入了大量时间来编辑和宣传您的故事，因此一旦发布，就不要将它们从“中型”出版物中删除。
Our editors have experience running newspapers and editing technical publications. We’ll read your submission, and if we think it’s promising, we’ll give you candid feedback as to how you can improve it. Then we’ll perform final editing on your story, publish it, then help you publicize it.
我们的编辑人员具有运行报纸和编辑技术出版物的经验。 我们将阅读您的提交内容，如果我们认为它很有希望，我们将为您提供有关如何改进它的坦诚反馈。 然后，我们将对您的故事进行最终编辑，将其发布，然后帮助您进行宣传。
Since we launched this Medium publication 18 months ago:
自我们18个月前发布此中号出版物以来：
- we’ve published about 1,000 stories 我们已经发表了大约1000个故事
- that have received an average of 23,000 views 平均获得23,000次观看
- with a median of 6,500 views (that is, half of these stories have received at least 6,500 views) 平均观看次数为6,500次(也就是说，其中一半故事至少获得了6,500次观看)
So if you’re writing about technology, we can help you reach a much larger audience.
因此，如果您正在撰写有关技术的文章，我们可以帮助您吸引更多的受众。
目录 (Table of Contents)
我们如何评估，编辑和发布故事 (How we evaluate, edit, and publish stories)
Note: I’ve hidden the submission instructions, the secret word, and the email address in the text below so that you’ll read all of this. ?
注意：我在下面的文本中隐藏了提交说明，密码和电子邮件地址，以便您阅读所有内容。 ？
We receive 100+ submissions each week, and are protective of our readers’ time. We seek to only publish stories that are:
每周我们都会收到100余篇论文，并保护了读者的时间。 我们仅寻求发布以下故事：
- well written 写得好
- about interesting topics that people haven’t already written about too much 人们还没有写太多有趣的话题
relevant to our audience of developers, designers, and data scientists.
与开发人员 ， 设计师和数据科学家的听众有关。
If we think your story is a good fit, we’ll add you as a writer to the freeCodeCamp publication and send you an acceptance letter with further instructions.
如果我们认为您的故事很合适，我们会将您作为作家添加到freeCodeCamp出版物中，并向您发送包含进一步说明的录取通知书。
Then we’ll put your story in the queue to be edited and published. (Here’s our editor handbook if you’re curious about this process). This process may take a while, so we thank you in advance for your patience. You’ll be able to view edits in Medium’s revision history. You will still have full control of your article if you need to make updates.
然后，我们会将您的故事放到队列中进行编辑和发布。 (如果您对此过程感到好奇，请参阅我们的编辑手册 )。 这个过程可能需要一段时间，因此我们感谢您的耐心配合。 您将能够在Medium的修订历史记录中查看修改。 如果需要进行更新，您仍然可以完全控制您的文章。
If we don’t think your story is a good fit for the freeCodeCamp publication, we will send you an email letting you know this. No worries. It won’t negatively affect your ability to get subsequent stories published here.
如果我们认为您的故事不适合freeCodeCamp出版物，我们将向您发送电子邮件告知您。 别担心。 它不会负面影响您在此处发布后续故事的能力。
Note that all our editors have other responsibilities within the open source community, so it may take several days for us to reply to you. But as long as you follow the submission instructions hidden below, we will reply to you.
请注意，我们所有的编辑人员在开源社区中还承担其他责任，因此我们可能需要几天的时间才能回复您。 但是，只要您按照下面隐藏的提交说明进行操作，我们就会回复您。
快速入门，适合在中等水平上书写 (A quick primer for writing well on Medium)
As a writer, you fight a war against indifference. You have to get people to care enough to click through to your story. You have to convince them to take a chance on you.
作为作家，您要与冷漠进行斗争。 您必须让人们足够关心才能单击您的故事。 您必须说服他们把握机会。
You have only two weapons against the relentless scroll of news feeds: a headline and an image.
您只有两种武器来抵制不断更新的新闻提要：标题和图片。
Here’s what a story looks like in Medium’s news feed:
这是Medium的新闻Feed中的故事：
Here’s what it looks like on Facebook:
这是在Facebook上的样子：
And here’s what it looks like on Twitter:
这就是Twitter上的样子：
Your headline and opening image are the only things people have to judge your story on. Before they can even read your story’s first paragraph, they must answer a question. It’s the same question that we all ask ourselves every day: is this going to be worth my time?
人们只需要用标题和开头的图片来判断您的故事即可。 在他们甚至无法阅读您故事的第一段之前，他们必须回答一个问题。 我们每天都问自己同样的问题： 这值得我度过吗？
Your first job as a writer is to choose a headline and image that will make people answer “yes.”
作为作家的第一项工作是选择标题和图像，使人们回答“是”。
一个好的标题可以使一切变得不同 (A good headline makes all the difference)
Your headline is the most important part of your story. Spend time refining it.
标题是故事中最重要的部分。 花时间完善它。
Don’t use clickbait: “You won’t believe this one ridiculously effective headline dark pattern”
不要使用clickbait：“您不会相信这种荒谬有效的标题暗纹”
Don’t use listicles: “11 outrageous headlines that will compel people to read your Medium story”
不要使用列表：“ 11个令人发指的标题会迫使人们阅读您的中型故事”
Do tell the truth: “Clever but matter-of-fact headline about an interesting topic”
实话实说：“关于一个有趣话题的聪明而真实的标题”
How long should your headline be? HubSpot analyzed 6,000 blog posts and found that stories with 8 to 14-word headlines get more social media shares.
您的标题应该多久？ HubSpot 分析了 6,000个博客文章，发现标题为8到14个单词的故事获得了更多的社交媒体份额。
This said, make sure your headline is 80 characters or fewer. Otherwise, the title will get truncated in news feeds when people share your article on Facebook and Twitter.
也就是说，请确保标题不超过80个字符 。 否则，当人们在Facebook和Twitter上分享您的文章时，标题将在新闻提要中被截断。
Another consideration is how emotional a headline is. The more emotional (positive or negative) a headline is, the more likely people will click it.
另一个考虑因素是标题的情感程度。 标题越情绪化(正面或负面)，人们点击它的可能性就越大。
Here’s a tool that helps you balance the length and sentiment of your headlines.
这是一个可以帮助您平衡标题的长度和情感的工具 。
Headlines are traditionally written in “title case.” The Associated Press says to “capitalize the first letter of every word except articles, coordinating conjunctions, and prepositions of three letters or fewer.”
头条传统上以“标题大小写”书写。 美联社说：“将每个单词的首字母大写，除了文章，协调连词和三个字母或少于三个字母的介词。”
On Medium, I often throw title case out the window and just write headlines like a normal sentence. I even include punctuation as necessary. This format is more conversational, and easier to read.
在Medium上，我经常把标题放在外面，只是像一般句子一样写标题。 我甚至在必要时添加标点符号。 这种格式更易于对话，更易于阅读。
Don’t break stories into parts. Labels like “part 1” scare people off, because who knows when you’ll get around to writing part 2. And if people encounter “part 2” and they haven’t read part 1, there’s a good chance they just won’t bother reading either. So it’s much better to just publish a single in-depth story.
不要将故事分成几部分。 诸如“第1部分”之类的标签会让人们感到恐惧，因为谁知道您何时开始编写第2部分。如果人们遇到“第2部分”而他们没有读过第1部分，则很有可能他们不会要么打扰阅读。 因此， 只发布一个深入的故事会更好。
图片被捕 (Arrest with images)
The second most important aspect of your story is its featured image.
故事的第二个最重要的方面是其特色形象。
Medium will automatically make the first image in your article its featured image. This means your article’s og-image meta property will be this image. This image will serve as your story’s ambassador everywhere: social media news feeds, Reddit, Google News — even RSS readers.
中号会自动使您文章中的第一张图片成为特色图片。 这意味着您文章的og-image元属性将是该图像。 该图像将在任何地方充当您故事的大使：社交媒体新闻提要，Reddit，Google新闻-甚至是RSS阅读器。
You can manually force Medium to treat a specific image as your article’s featured image. While in edit mode, click the image, then:
您可以手动强制Medium将特定图像视为文章的特色图像。 在编辑模式下，单击图像，然后：
- Mac: ⌘ + Opt + 8 Mac：⌘+ Opt + 8
- PC: Ctrl + Alt + 8 PC：Ctrl + Alt + 8
Start considering images early in the writing process. And never publish without at least one image. Otherwise your story will be all but invisible in news feeds.
在写作过程中尽早开始考虑图像。 绝不要发布至少一张图片。 否则，您的故事在新闻源中几乎是看不见的。
You should break up long stories with images. To paraphrase Mary Poppins, a spoonful of images helps the text go down.
您应该用图像分解长篇小说。 用玛丽·波平斯(Mary Poppins)来形容，一勺图像有助于使文本下降。
Medium offers four different image widths. Note that these will all look the same on mobile.
中号提供四种不同的图像宽度。 请注意，这些内容在移动设备上看起来都是一样的。
Most of the time, you’ll want to stick with column width:
大多数时候，您会坚持使用列宽：
If you have a chart that is hard to read when it’s small, go bigger:
如果您的图表很小，则难以阅读，请放大：
And if you’re really proud of an image, or if it’s chock full of interesting data, go full-bleed:
并且，如果您真的为图像感到骄傲，或者图像中充满了有趣的数据，请全血：
… and then there’s side straddle. Don’t use this size at all, because it makes the text less comfortable to read.
……然后是侧面跨骑。 完全不要使用此大小，因为它会使文本阅读起来不太舒服。
It’s also awkward when you’re done talking about the photo and your text is still pushed to the side.
当您谈论完照片并且文本仍被推到一边时，这也很尴尬。
Yeah. I’m still stuck over here.
是的 我仍然被困在这里。
Always include a high-resolution image at the top of a story under your headline. This has the following benefits:
始终在标题下方的故事顶部包含高分辨率图像。 这具有以下好处：
- When people share your story on Facebook and Twitter, it will be more prominent in news feeds, making people more likely to click on it. 当人们在Facebook和Twitter上分享您的故事时，它将在新闻源中更加突出，使人们更有可能点击它。
- It will look better in Medium’s own news feeds. 在Medium自己的新闻提要中看起来会更好。
- Humans are visual creatures, and click on images. 人类是视觉生物，点击图像。
建立强大的领导力 (Build momentum with a strong lead)
Once your reader clicks through to your story, the trial begins. They’re looking for any excuse to jump back to their news feed. Reading requires a lot more effort than scrolling through cat photos.
读者点击阅读您的故事后，便开始试用。 他们正在寻找借口跳回到他们的新闻提要。 与滚动浏览猫的照片相比，阅读需要付出更多的努力。
Don’t waste time with intros or updates like “This was published on my blog at [blog URL]” or “Update: this has been posted on Hacker News.” You can put these things at the bottom of your story.
不要浪费时间进行介绍或更新，例如“此消息已发布在我的博客[blog URL]上”或“更新：此消息已发布在Hacker News”上。 您可以将这些内容放在故事的底部。
Instead, start making points and telling your story immediately.
相反，请开始提出观点并立即讲故事。
建立信誉 (Establish credibility)
Figure out a way to establish your credibility within the first few paragraphs. If you’re a top expert in your field, say so. Don’t assume that people are going to take the time to google you.
在前几段中找出建立信誉的方法。 如果您是该领域的顶级专家，请这么说。 不要以为人们会花时间去找你。
“Who you are speaks so loudly I can’t hear what you’re saying.” — Ralph Waldo Emerson
“你这么大声说话，我听不到你在说什么。” —拉尔夫·沃尔多·爱默生
Any achievement or distinction that makes people take you more seriously will help give your readers the impression that “this person knows what they’re talking about.”
任何使人们更加重视您的成就或成就，都会给读者留下“这个人知道他们在说什么”的印象。
Reinforce your credibility throughout your story. Support your arguments with data. Use inline links to (non-paywalled) research.
在整个故事中增强您的信誉。 用数据支持您的论点。 使用内联链接(无付费)研究。
This isn’t the New England Journal of Medicine. This is Medium. So don’t use footnotes.
这不是《新英格兰医学杂志》。 这是中。 因此，请勿使用脚注。
写得聪明 (Write smart)
Good writing is hard. Like any skill, it takes practice. There are no shortcuts to becoming a strong writer.
好的写作很难。 像任何技能一样，它需要练习。 成为一名强大的作家没有捷径。
Do yourself a favor: write what you know.
帮自己一个忙： 写下你所知道的 。
Have you ever heard the term “writers block?” Writer’s block happens when you don’t know enough about a topic to write about it.
您听说过“作家封锁”一词吗？ 如果您对某个主题的了解不足，就无法编写作家。
If you have trouble coming up with at least 5 minutes worth of things to say on a topic — or if your story devolves into a list of bullet points — you don’t know enough about it.
如果您在提出至少5分钟的话题话题时遇到麻烦-或者您的故事陷入了要点列表中-您对此一无所知。
The antidote is research. Learning. Going out into the field.
解药是研究。 学习。 走进田野。
Don’t publish anything you’re not proud of. Medium isn’t a numbers game. It’s a social contract. People follow you. In turn, you show respect for their scarce time.
不要发布任何您不感到骄傲的东西。 中型不是数字游戏。 这是社会契约。 人们跟随你。 反过来，您要尊重他们的稀缺时间。
Good Medium stories don’t come naturally. For every minute of story length, expect to spend at least an hour writing, re-writing, and editing your story.
好的中级故事并非自然而然。 对于故事的每一分钟，预计至少要花费一个小时来编写，重写和编辑故事。
归因于您的来源 (Attribute your sources)
The simplest way to attribute an image is to put the words “Image credit” below an image, and link this text to its original source.
归因于图像的最简单方法是在图像下方放置“图像信用”一词，并将此文本链接到其原始来源。
If you’re looking for images you can safely use without permission, check out Pexels, Unsplash, or search Google for images labeled for re-use.
如果您正在寻找图片，可以在未经许可的情况下安全使用，请查看Pexels ， Unsplash或在Google中搜索标记为可重复使用的图片。
Plagiarism — misrepresenting someone else’s writing as your own — is a serious offense in college, and it’s just as serious on Medium. Always attribute quotes to the people who originally said them. If it’s a multi-line quote, you should use Medium’s pull quotes:
gi窃-歪曲别人的作品作为自己的作品-在大学里是严重的违法行为，在中型媒体上也是如此。 始终将引号归于最初说过的人。 如果是多行引号，则应使用中号的拉引号：
“When you have wit of your own, it’s a pleasure to credit other people for theirs.”
“当您拥有自己的智慧时，很高兴为别人效忠。”
You should only use Medium’s pull quotes as a way to highlight actual quotes — not to style your own text.
您仅应使用中号的拉引号作为突出显示实际引号的方法，而不能为自己的文本设置样式。
展示您的代码 (Showcase your code)
Where possible, code should be in text form rather than images. This makes the code more accessible to screen readers, and easier for people to copy and paste.
可能的话，代码应采用文本形式而不是图像形式。 这使屏幕阅读器更易于访问代码，并且人们更容易复制和粘贴代码。
Medium has a hidden shortcut that will turn text plain text like this:
中号有一个隐藏的快捷方式，它将使文本变成纯文本，如下所示：
if (developer === true) {
如果(开发人员=== true){
follow(this.mediumPublication);
按照(this.mediumPublication);
}
}
…into a formatted code block:
……变成格式化的代码块：
if (developer === true) {follow(this.mediumPublication);}To accomplish this, select the text, then push:
为此，请选择文本，然后按：
Windows: Control + Alt + 6
Windows ：Control + Alt + 6
Mac: Command + Option + 6
Mac ：Command + Option + 6
Linux: Control + Alt + 6
Linux ：Control + Alt + 6
You can also start a code block with triple back-ticks. If you type three backticks (```) on a new line, Medium will switch into code input mode.
您还可以使用三个反向标记来启动代码块。 如果在新行上键入三个反引号(```)，则Medium将切换到代码输入模式。
To highlight code inline, select it, then press the backtick key. This way, you can format text as code freeCodeCamp()right in the middle of a sentence.
要突出显示内联代码，请选择它，然后按反引号键。 这样，您可以在句子的中间将文本格式化为代码freeCodeCamp() 。
You can even embed runnable apps right into Medium. Just in case these don’t render properly in Medium’s mobile apps, I recommend including links below each of the embeds as a fallback.
您甚至可以将可运行的应用程序直接嵌入Medium。 以防万一这些内容无法在Medium的移动应用中正确呈现，我建议在每个嵌入下方添加链接作为后备。
Paste a CodePen.io URL into Medium, then hit enter:
将CodePen.io URL粘贴到Medium中，然后按Enter：
View my CodePen here.
在这里查看我的CodePen。
You can also do this with JSFiddle.net:
您也可以使用JSFiddle.net做到这一点：
View my JSFiddle here.
在这里查看我的JSFiddle。
Sometimes people start lines of code with a $ if they’re terminal commands. Don’t do this. It will confuse beginners and makes it harder to copy and paste commands. Instead, just say something like “Enter the following commands in your terminal.”
有时，如果是终端命令，人们会以$开头的代码行。 不要这样 它将使初学者感到困惑，并使复制和粘贴命令变得更加困难。 而是说“在终端中输入以下命令”。
使链接看起来自然 (Make links look natural)
Figure out a way to work a link into a sentence. One thing I do not recommend doing is putting a link on its own line and pressing enter. This will create a nice looking preview card, like this:
找出将链接链接到句子的方法。 我不建议您做的一件事是在自己的行上放置一个链接，然后按Enter键。 这将创建一个外观漂亮的预览卡，如下所示：
How to stand on the shoulders of giantsConquer Not Invented Here Syndrome, then do something new.medium.freecodecamp.com
如何站在巨人的肩膀上 征服“此处未发明”综合症，然后做一些新的事情。 medium.freecodecamp.com
… but readers often assume these are ads, and don’t even look at them.
…但是读者经常认为这些是广告，甚至根本不看它们。
The only time I would recommend using this is at the end of your story, if you want to link to further reading.
如果您想链接到进一步的阅读内容，我唯一建议使用的方法是在故事的结尾。
Underlining text makes it harder to read, so only hyperlink a few words.
带下划线的文本使阅读更困难，因此仅超链接几个单词。
Don’t paste URLs directly, like this: ❌ https://www.freecodecamp.com ❌
不要像这样直接粘贴URL：❌https : //www.freecodecamp.com❌
Instead link to sites like freeCodeCamp mid sentence, like I just did here.
而是链接到freeCodeCamp中间句子之类的网站，就像我在这里所做的那样。
嵌入媒体 (Embed media)
You can embed Tweets, YouTube videos, and other media by pasting their URLs into Medium on a new line, then pressing enter.
您可以通过以下方式嵌入推文，YouTube视频和其他媒体：将其URL粘贴到新行上的“中”，然后按Enter。
Use these sparingly, since they may distract your reader from finishing your story.
请谨慎使用这些内容，因为它们可能会使您的读者无法完成故事。
解释缩写 (Explain abbreviations)
Don’t use an abbreviation unless the abbreviation is more widely understood than what it stands for. For example, HTTP is more widely recognized than Hypertext Transfer Protocol.
除非缩写比其含义更广泛地理解，否则不要使用缩写。 例如，HTTP比超文本传输协议得到更广泛的认可。
If an abbreviation isn’t already widely understood, and you’re going to refer to it more than a few times, you can define it as an abbreviation by doing this:
如果缩写尚未被广泛理解，并且您将多次使用该缩写，则可以通过执行以下操作将其定义为缩写：
“Let’s break the code down into an Abstract Syntax Tree (AST).”
“让我们将代码分解为抽象语法树 (AST)。”
Here I also linked to the Wikipedia article, for readers’ convenience. Don’t assume people will read these external links, though. You still need to define concepts or illustrate them through example.
为了方便读者，在这里我还链接了Wikipedia文章。 但是，不要以为人们会阅读这些外部链接。 您仍然需要定义概念或通过示例进行说明。
Avoid defining an abbreviation in your opening paragraphs, as it slows your reader down and makes them less likely to continue reading.
避免在开头的段落中定义缩写，因为这会使读者放慢速度，并使他们不太可能继续阅读。
Here’s the very short list of technology abbreviation that you don’t need to define: API, AJAX, BIOS, CPU, CSS, HTML, HTTPS, JSON, LAN, RAM, REST, USB, WWW, XML. For everything else, you should spell it out.
这是您不需要定义的非常简短的技术缩写列表：API，AJAX，BIOS，CPU，CSS，HTML，HTTPS，JSON，LAN，RAM，REST，USB，WWW，XML。 对于其他所有内容，您都应说明。
Always spell out short multi-part words like JavaScript and front-end. Don’t shorten them. The brevity isn’t worth the possible confusion.
始终拼写出包含JavaScript和前端之类的简短的多部分单词。 不要缩短它们。 简洁不值得造成混乱。
外观和风格 (Look and style)
If you want to emphasize something, use bold, but use it sparingly. Italics are harder to read. Don’t bold hyperlinks — the line underneath them already provides enough emphasis.
如果您想强调某些内容，请使用粗体 ，但要少用。 斜体字更难读。 不要用粗体显示超链接-它们下面的线已经足够强调了。
Don’t use drop caps. They look elegant in old books, but silly on the web.
不要使用首字下沉。 它们在旧书中看起来很优雅，但在网络上却很愚蠢。
Only use one exclamation point at a time, typically only after exclamations like: Golly gee! Hot dog!
一次只能使用一个感叹号，通常只能在类似感叹号之后使用：Golly gee！ 热狗！
Put commas and periods inside quotes, except when it might confuse a reader (like with variable names or book titles).
将逗号和句点放在引号中，除非它可能会使读者感到困惑(例如，使用变量名或书名)。
In some parts of the world, people put spaces before colons or question marks, like this : example. Don’t do this.
在世界的某些地方，人们在冒号或问号之前放置空格，例如：example。 不要这样
Use English instead of Latin:
使用英语而不是拉丁语：
- Use “for example” instead of “E.G.” 使用“例如”代替“ EG”
- Use “that is” instead of “I.E.” 使用“即”代替“ IE”
- Use “note that” instead of “N.B.” 使用“注意”而不是“ NB”
- Instead of ending lists with “etc.” start them with “like”: “Elvis eats food like bread, peanut butter, and bananas.” 而不是用“等”结尾列表。 以“喜欢”开始：“猫王喜欢吃面包，花生酱和香蕉等食物。”
According to Google Books, semicolons have been dying a slow death. Let’s put them out of their misery. Just use a period instead, and break clauses into separate sentences.
根据Google图书的说法，分号已死于缓慢的死亡。 让我们摆脱他们的痛苦。 只需使用句号，然后将子句分成单独的句子即可。
Use the Oxford Comma when possible. It makes things easier, clearer, and prettier to read.
尽可能使用牛津逗号。 它使事情变得更容易，更清晰和更漂亮。
Use the Hemingway App. There’s nothing magical about this simple tool, but it will automatically detect widely agreed-upon style issues:
使用Hemingway App 。 这个简单的工具没有什么神奇的，但是它将自动检测出广泛认可的样式问题：
- passive voice 被动语态
- unnecessary adverbs 不必要的副词
- words that have more common equivalents 具有更常见的等价词
The Hemingway App will assign a “grade level” for your writing. Even technical stories can pull off a grade level of 6. And they should aspire to.
海明威应用程序将为您的写作分配一个“年级”。 甚至技术故事也可以达到6级。他们应该向往。
Most humans are not native English speakers, and the ones who are don’t usually sit around reading Chaucer all day. They want their information accessible and to the point.
大多数人不是讲英语的人，而那些通常不整天坐在草地上读书的人。 他们希望他们的信息可以访问并指向重点。
Err on the side of breaking long sentences and paragraphs down into shorter ones.
将较长的句子和段落分解为较短的句子时出错。
Despite what you may have learned in English composition class, people prefer short paragraphs to “walls of text.”
尽管您可能在英语作文课上学到了什么，但人们还是喜欢短段落而不是“文字墙”。
There’s nothing wrong with single-sentence paragraphs.
单句段落没有错。
Err on the side of creating new paragraphs.
在创建新段落方面犯了错误。
Use contractions. They’ll make your prose seem more conversational. That’s always a plus.
使用宫缩。 他们会让您的散文看起来更具对话性。 这总是一个加号。
Keep your tense consistent throughout. If you’re talking about something that occurred in past, use past tense.
始终保持一致。 如果您在谈论过去发生的事情，请使用过去时。
Also, front-end development (adjective form with a dash) is when you’re working on the front end (noun form with no dash). The same goes with the back end, full stack, and many other compound terms.
同样， 前端开发(带破折号的形容词形式)是在前端上工作时 (带破折号的名词形式)。 后端，完整堆栈和许多其他复合术语也是如此。
新增5个标签 (Add 5 tags)
Medium allows you to add up to five tags to your story. Use them.
中号可让您为故事添加多达五个标签。 使用它们。
People follow specific topics on Medium. The most popular ones are #tech, #life-lessons, #travel, #design, and #startup.
人们遵循中型的特定主题。 最受欢迎的是＃tech，＃life-lessons，＃travel，＃design和#startup。
People who follow the tags you use may see your story in their news feed. Tags also make it easier for people to stumble upon your story in search results.
遵循您使用的标签的人可能会在其新闻Feed中看到您的故事。 标签还使人们更容易在搜索结果中偶然发现您的故事。
And now that you’ve read this far, here’s how to submit your story to the freeCodeCamp publication: send an email to submit at freecodecamp org. Include the URL for your story on Medium (preferably an unpublished draft) and the word “bananas” so that we’ll know that you have read all this. Only send one story URL per email. There’s no need to add anything further to your email — we just read the stories and judge them based on their own merits.
到目前为止，您已经阅读了这里，下面是如何将故事提交到freeCodeCamp出版物：发送电子邮件以在freecodecamp org上提交。 在“中”(最好是未发表的草稿)上包含您故事的URL，并加上“香蕉”一词，这样我们就会知道您已经阅读了所有这些内容。 每封电子邮件仅发送一个故事URL。 无需在您的电子邮件中进一步添加任何内容-我们只需阅读故事并根据自己的优点对其进行判断。
在社交媒体上发布您的故事 (Publicize your stories on social media)
You can share your story on Twitter, Facebook groups, and relevant Subreddits. If you have a mailing list, you can blast it out to your subscribers, too.
您可以在Twitter，Facebook组和相关的Subreddit上分享您的故事。 如果您有邮件列表，也可以将其分发给您的订阅者。
You can view your story’s stats in real time. Ask for feedback from your friends and followers. Incorporate this feedback into your story.
您可以实时查看故事的统计信息 。 要求您的朋友和关注者提供反馈。 将此反馈纳入您的故事。
Don’t do anything sketchy to promote your story. You will most likely be caught. Sites like Hacker News and Reddit are very good at detecting abnormal voting behavior. This will reflect poorly not just on you, but the entire freeCodeCamp community as well.
不要粗略地宣传您的故事。 您很可能会被抓住。 像Hacker News和Reddit这样的网站非常擅长检测异常投票行为。 这不仅会影响到您，而且也会影响整个freeCodeCamp社区。
最终建议 (Final advice)
Remember that when you publish on Medium, you’re asking thousands of people to give you several minutes of their lives. Don’t take your readers for granted.
请记住，当您在Medium上发布时，您是在要求成千上万的人给您几分钟的生命。 不要把你的读者视为理所当然。
Before you publish a story, I recommend you sleep, wake up, then proof-read it again.
在发布故事之前，建议您睡觉，醒来，然后再次进行校对。
If you aren’t a native English speaker and are writing in English, ask a native speaker to proof-read your story before submitting it to a publication.
如果您不是讲英语的人，并且使用英语写作，请在讲故事之前，先让讲英语的人对您的故事进行校对。
We’re looking forward to reading your submissions. I hope we can help you further improve your stories, and reach a much wider audience.
我们期待着您的来信。 希望我们能帮助您进一步完善您的故事，并扩大受众范围。
linux中的medium
81万+
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
