create the Inside Rust blog

Along the way:

- blog post layouts are now mandatory, but must be "post"
- blog manifest specifies if the `team` attribute is required
- if so, it should have the format `team name <team-url>`

Author: nikomatsakis

Cargo.lock

@@ -6,11 +6,13 @@ edition = "2018"
 
 [dependencies]
 handlebars = "1.1.0"
+lazy_static = "1.4.0"
 serde = "1.0"
 serde_derive = "1.0"
 serde_yaml = "0.8"
 serde_json = "1.0"
 comrak = "0.4"
 fs_extra = "1.1.0"
+regex = "1.3"
 sass-rs = "0.2.1"
 time = "0.1.41"

Cargo.toml

@@ -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-01-03-new-years-rust-a-call-for-community-blogposts.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/2018-10-30-help-test-rust-2018.md

@@ -2,3 +2,5 @@ title: Rust Blog
 index-title: The Rust Programming Language Blog
 description: Empowering everyone to build reliable and efficient software.
 maintained-by: the Rust Team
+requires-team: false
+

posts/blog.yml

@@ -0,0 +1,16 @@
+---
+layout: post
+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: the core team <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/2019-09-25-Welcome.md

@@ -0,0 +1,5 @@
+title: Inside Rust blog
+index-title: the Inside Rust blog
+description: Want to follow along with Rust development? Curious how you might get involved? Take a look!
+maintained-by: the Rust Teams
+requires-team: true

posts/inside-rust/blog.yml

@@ -8,11 +8,12 @@ static POSTS_EXT: &str = "md";
 
 #[derive(Deserialize)]
 #[serde(rename_all = "kebab-case", deny_unknown_fields)]
-struct Manifest {
-    title: String,
-    index_title: String,
-    description: String,
-    maintained_by: String,
+pub(crate) struct Manifest {
+    pub(crate) title: String,
+    pub(crate) index_title: String,
+    pub(crate) description: String,
+    pub(crate) maintained_by: String,
+    pub(crate) requires_team: bool,
 }
 
 #[derive(Serialize)]
@@ -36,7 +37,7 @@ impl Blog {
             let path = entry?.path();
             let ext = path.extension().and_then(|e| e.to_str());
             if path.metadata()?.file_type().is_file() && ext == Some(POSTS_EXT) {
-                posts.push(Post::open(&path)?);
+                posts.push(Post::open(&path, &manifest)?);
             }
         }
 

src/blogs.rs

@@ -159,7 +159,7 @@ impl Generator {
             "post": post,
         });
 
-        self.render_template(path.join(filename), "post", data)?;
+        self.render_template(path.join(filename), &post.layout, data)?;
         Ok(())
     }
 

src/main.rs

@@ -1,4 +1,6 @@
+use crate::blogs::Manifest;
 use comrak::ComrakOptions;
+use regex::Regex;
 use serde_derive::{Deserialize, Serialize};
 use std::error::Error;
 use std::path::{Path, PathBuf};
@@ -9,11 +11,14 @@ struct YamlHeader {
     author: String,
     #[serde(default)]
     release: bool,
+    team: Option<String>,
+    layout: String,
 }
 
 #[derive(Debug, Clone, Serialize)]
 pub(crate) struct Post {
     pub(crate) filename: String,
+    pub(crate) layout: String,
     pub(crate) title: String,
     pub(crate) author: String,
     pub(crate) year: String,
@@ -24,10 +29,13 @@ pub(crate) struct Post {
     pub(crate) url: String,
     pub(crate) published: String,
     pub(crate) release: bool,
+    pub(crate) has_team: bool,
+    pub(crate) team: String,
+    pub(crate) team_url: String,
 }
 
 impl Post {
-    pub(crate) fn open(path: &Path) -> Result<Self, Box<dyn Error>> {
+    pub(crate) fn open(path: &Path, manifest: &Manifest) -> Result<Self, Box<dyn Error>> {
         // yeah this might blow up, but it won't
         let filename = path.file_name().unwrap().to_str().unwrap();
 
@@ -49,6 +57,8 @@ impl Post {
             author,
             title,
             release,
+            team: team_string,
+            layout,
         } = serde_yaml::from_str(yaml)?;
         // next, the contents. we add + to get rid of the final "---\n\n"
         let options = ComrakOptions {
@@ -84,6 +94,34 @@ impl Post {
 
         let published = published.rfc3339().to_string();
 
+        // validate for now that the layout is specified as "post"
+        match &*layout {
+            "post" => (),
+            _ => panic!("blog post at path `{}` should have layout `post`", path.display()),
+        };
+
+        // Enforce extra conditions
+        if manifest.requires_team && team_string.is_none() {
+            panic!("blog post at path `{}` lacks team/team_url metadata", path.display());
+        }
+
+        // If they supplied team, it should look like `team-text <team-url>`
+        let (team, team_url) = match team_string {
+            Some(s) => {
+                lazy_static::lazy_static! {
+                    static ref R: Regex = Regex::new(r"(?P<name>[^<]*) <(?P<url>[^>]+)>").unwrap();
+                }
+                let captures = match R.captures(&s) {
+                    Some(c) => c,
+                    None => panic!("team from path `{}` should have format `$name <$url>`",
+                                   path.display()),
+                };
+                (Some(captures["name"].to_string()), Some(captures["url"].to_string()))
+            }
+
+            None => (None, None)
+        };
+
         Ok(Self {
             filename,
             title,
@@ -96,6 +134,10 @@ impl Post {
             url,
             published,
             release,
+            layout,
+            has_team: team.is_some(),
+            team: team.unwrap_or_default(),
+            team_url: team_url.unwrap_or_default(),
         })
     }
 }