Skip to content

Commit e9847fa

Browse files
fix: add mailto and hashtag links
1 parent 0ef44f7 commit e9847fa

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

_posts/2018-01-03-new-years-rust-a-call-for-community-blogposts.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -47,10 +47,12 @@ A great example of what we're looking for is this post,
4747
["Rust in 2017"](https://medium.com/@Hisako1337/rust-in-2017-8f2b57a67d9b)
4848
by [Anonyfox](https://github.com/Anonyfox).
4949

50-
You can write up these posts and email them to [email protected] or tweet them with the
51-
hashtag `#Rust2018`. We'll aggregate any blog posts sent via email or with the hashtag in one
50+
You can write up these posts and email them to <a href="mailto:[email protected]">[email protected]</a>
51+
or tweet them with the hashtag [`#Rust2018`]. We'll aggregate any blog posts sent via email or with the hashtag in one
5252
big blog post here.
5353

54+
[`#Rust2018`]: https://twitter.com/search?q=%23Rust2018
55+
5456
The Core team will be reading all of the submitted posts and using them to inform the initial
5557
roadmap RFC for 2018. Once the RFC is submitted, we'll open up the normal RFC process, though
5658
if you want, you are welcome to write a post and link to it on the GitHub discussion.

0 commit comments

Comments
 (0)