You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+19-1Lines changed: 19 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@ What we are generally NOT looking for includes:
39
39
* Rants or anything degrading to any part or member of the Community. Rather than submitting an article about what is wrong with something, we would much rather you write something that explains how you'd make it better.
40
40
* Duplicates of recent posts (even with the wording changed slightly)
41
41
* Links to crates or GitHub repos without some sort of context. We would much rather you submit a blog post introducing your project and how a Rust user might use it (and what it would help them do) and/or what you learned about Rust in the process of writing the project.
42
-
* Anything behind a paywall (this includes Medium's paid article mechanism)
42
+
* Anything behind a paywall (this includes Medium's paid article / members-only mechanism)
43
43
* Anything that requires information to be shared/captured (like an email address) in order to access
44
44
45
45
These are meant to be guidelines, if you are ever not sure about whether something should be included please feel free to open a pull request anyway and we can discuss it!
@@ -48,6 +48,8 @@ The editors of This Week in Rust do reserve the right to make the decision about
48
48
49
49
## Link style guidelines:
50
50
51
+
The link text should be the same as the page's title. If the title seems to need additional context (for example, if the title is "What's New" and should have the project name added), please ask in the PR comments.
52
+
51
53
Links should use the most canonical form. For example, if `example.tech` redirects to `www.example.com`, then the latter is preferred.
52
54
53
55
Links should not contain unnecessary tracking parameters, e.g. `utm_source`, `utm_campaign`.
@@ -58,6 +60,22 @@ Some prefixes are used, and should be placed to the left of the link.
58
60
-`[series]` for articles that are one of a series.
59
61
- 2-letter languages codes (e.g. `[ZH]`, `[ES]`, `[FR]`) for content in a language other than English.
60
62
63
+
## Community sub-categories
64
+
65
+
Editors will sort community links into sub-categories. The following sub-categories are currently used:
66
+
-**Official** -- rust-lang.org blog posts and other official Rust team communications.
67
+
-**Foundation** -- foundation.rust-lang.org blog posts and other official foundation communications.
68
+
-**Project/Tooling Updates** -- News about the progress of a Rust project. Must be more informative than just a changelog.
69
+
-**Newsletters** -- Regularly scheduled articles about an area of Rust development, e.g. posts titled "This Month in ___".
70
+
-**Research** -- Academic Papers that are about Rust or contain significant Rust content.
71
+
-**Observations/Thoughts** -- Articles about Rust.
72
+
-**Rust Walkthroughs** -- Articles that include a significant amount of Rust source code, that walk the reader through building something.
73
+
-**Miscellaneous** -- Links that don't clearly fit in other sub-categories.
74
+
75
+
Most blog posts about Rust belong in **Rust Walkthroughs** if they show how something is done (including source code), otherwise **Observations/Thoughts**. Articles that don't contain much Rust content, or news articles that mention Rust, won't always be accepted, but when they are they can be placed in the **Miscellaneous** sub-category.
76
+
77
+
If a set of related links is published (e.g. from a large Rust conference), the editors may choose to invent a new category just for that issue.
0 commit comments