-
Notifications
You must be signed in to change notification settings - Fork 101
[RFC] blog.rust-embedded.org #191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,58 @@ | ||
- Feature Name: blog | ||
- Start Date: 2018-08-22 | ||
- RFC PR: (leave this empty) | ||
- Rust Issue: (leave this empty) | ||
|
||
# Summary | ||
[summary]: #summary | ||
|
||
Host a blog at blog.rust-embedded.org and use it for our newsletters and | ||
announcements. | ||
|
||
# Motivation | ||
[motivation]: #motivation | ||
|
||
So far we have been posting our newsletters and announcements to | ||
https://users.rust-lang.org but it would be nice to have them on a place that's | ||
*ours* and that would be a blog. | ||
|
||
An advantage to having a blog is that it would be easier for readers to browse | ||
through our newsletters and announcements. Right now, they get lost in the | ||
stream in of new content posted to the users forum. Also, with a blog we can | ||
provide RSS which is something our readers have requested before. | ||
|
||
# Detailed design | ||
[design]: #detailed-design | ||
|
||
We'll create a new repository named `blog` that the resources team will be in | ||
charge of developing and maintaining. | ||
|
||
The content for the blog will be authored as markdown files, and the blog will | ||
be hosted as a static web site on https://blog.rust-embedded.org . The blog | ||
posts will *not* have a comments section. The exact mechanism by which the | ||
markdown files will be converted into a static site will be decided by the | ||
resources team. | ||
|
||
The WG newsletters and announcements will be posted on this blog. The resources | ||
team will be in charge of reviewing all the new content before its published. | ||
|
||
Finally, the newsletters directory in this repository will be moved into | ||
the blog repository. | ||
|
||
# Drawbacks | ||
[drawbacks]: #drawbacks | ||
|
||
- Readers would lose the ability to comment on newsletters and announcements. | ||
But, if we wish to, we can post a link to blog posts on reddit or the users | ||
forum and use that space to receive comments. | ||
|
||
# Alternatives | ||
[alternatives]: #alternatives | ||
|
||
- Continue posting our newsletters and announcements to | ||
https://users.rust-lang.org. | ||
|
||
# Unresolved questions | ||
[unresolved]: #unresolved-questions | ||
|
||
None |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it make sense to have a disqus as the comment section in the articles ?
I rather use a forum post/reddit
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We are trying to avoid having to host anything ourselves for now; I don't know if that'd be the case for disqus. My preference would be to use the users forum as mentioned in the next line of the RFC.