create the Inside Rust blog

Along the way:

- blog post layouts are now mandatory (and respected)
- inside rust blog posts are tagged with a distinct
  layout (`post-inside-rust`)
- this layout requires `team` and `team_url` metadata

Author: nikomatsakis

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

@@ -1,6 +1,7 @@
 ---
 title: "New Year's Rust: A Call for Community Blogposts"
 author: "The Rust Core Team"
+layout: post
 ---
 
 'Tis the season for people and communities to reflect and set goals- and the Rust team is

posts/2018-10-30-help-test-rust-2018.md

@@ -1,6 +1,7 @@
 ---
 title: "Help test Rust 2018"
 author: "The Rust Core Team"
+layout: post
 ---
 
 Back in July, we talked about ["Rust 2018"]. In short, we are launching a

posts/inside-rust/2019-09-25-Welcome.md

@@ -0,0 +1,17 @@
+---
+layout: post-inside-rust
+title: "Announcing the Inside Rust blog!"
+author: Niko Matsakis
+description: "A new blog where the Rust team can post updates on the latest developments"
+team: core
+team_url: https://www.rust-lang.org/governance/teams/core
+---
+
+Welcome to the inaugural post of the **Inside Rust** blog! This is a
+new blog where the various Rust teams and working groups can post
+updates about new developments. It's a great place to watch if you're
+interested in following along with Rust development -- and a
+particularly great place to watch if you're interested in contributing
+to Rust. Expect to see updates on new projects, calls for help, design
+notes, and other similar items. Thanks for reading!
+

posts/inside-rust/blog.yml

@@ -0,0 +1,4 @@
+title: Inside Rust blog
+index-title: Internal workings of the Rust project
+description: Want to follow along with Rust development? Curious how you might get involved? Take a look!
+maintained-by: the Rust Teams

src/main.rs

@@ -3,6 +3,7 @@ mod posts;
 
 use crate::blogs::Blog;
 use crate::posts::Post;
+use crate::posts::PostLayout;
 use handlebars::{Context, Handlebars, Helper, HelperResult, Output, RenderContext, RenderError};
 use sass_rs::{compile_file, Options};
 use serde_derive::Serialize;
@@ -159,7 +160,12 @@ impl Generator {
             "post": post,
         });
 
-        self.render_template(path.join(filename), "post", data)?;
+        let template_name = match post.layout {
+            PostLayout::Post => "post",
+            PostLayout::PostInsideRust => "post-inside-rust",
+        };
+
+        self.render_template(path.join(filename), template_name, data)?;
         Ok(())
     }
 

src/posts.rs

@@ -9,11 +9,15 @@ struct YamlHeader {
     author: String,
     #[serde(default)]
     release: bool,
+    team: Option<String>,
+    team_url: Option<String>,
+    layout: String,
 }
 
 #[derive(Debug, Clone, Serialize)]
 pub(crate) struct Post {
     pub(crate) filename: String,
+    pub(crate) layout: PostLayout,
     pub(crate) title: String,
     pub(crate) author: String,
     pub(crate) year: String,
@@ -24,6 +28,14 @@ pub(crate) struct Post {
     pub(crate) url: String,
     pub(crate) published: String,
     pub(crate) release: bool,
+    pub(crate) team: String,
+    pub(crate) team_url: String,
+}
+
+#[derive(Debug, Copy, Clone, Serialize)]
+pub(crate) enum PostLayout {
+    Post,
+    PostInsideRust,
 }
 
 impl Post {
@@ -49,6 +61,9 @@ impl Post {
             author,
             title,
             release,
+            team,
+            team_url,
+            layout,
         } = serde_yaml::from_str(yaml)?;
         // next, the contents. we add + to get rid of the final "---\n\n"
         let options = ComrakOptions {
@@ -84,6 +99,23 @@ impl Post {
 
         let published = published.rfc3339().to_string();
 
+        let layout = match &*layout {
+            "post" => PostLayout::Post,
+            "post-inside-rust" => PostLayout::PostInsideRust,
+            _ => panic!("blog post at path `{}` has an unrecognized layout", path.display()),
+        };
+
+        // Enforce extra conditions
+        match layout {
+            PostLayout::PostInsideRust => {
+                if team.is_none() || team_url.is_none() {
+                    panic!("blog post at path `{}` lacks team/team_url metadata", path.display());
+                }
+            }
+
+            _ => { }
+        }
+
         Ok(Self {
             filename,
             title,
@@ -96,6 +128,9 @@ impl Post {
             url,
             published,
             release,
+            layout,
+            team: team.unwrap_or_default(),
+            team_url: team_url.unwrap_or_default(),
         })
     }
 }

templates/post-inside-rust.hbs

@@ -0,0 +1,17 @@
+{{#*inline "page"}}
+<section id="{{post.title}}" class="white">
+  <div class="w-100 mw-none ph3 mw8-m mw8-l center f3">
+    <header>
+      <h2>{{ post.title }}</h2>
+      <div class="highlight"></div>
+    </header>
+
+    <div class="publish-date-author">{{month_name post.month}} {{post.day}}, {{post.year}} &middot; {{post.author}} &middot; <a href="{{post.team_url}}">{{post.team}}</a></div>
+
+    <div class="post">
+      {{{ post.contents }}}
+    </div>
+  </div>
+</section>
+{{/inline}}
+{{~> (parent)~}}