fix

Author: Hyeok Kim

README.md

@@ -70,18 +70,20 @@ Create a new branch (`git checkout -b my-branch-name`), commit as normal, then p
 
 - How do I add a new blog post?
 
-Create a markdown file under `static/blog-assets/posts`. The filename will be the slug in the URL. It can technically be anything, but the convention is `year-month-date-keyword.md` for consistency. Write a post by taking the following steps:
+Create a markdown file under `static/blog-assets/posts`. The filename will be the slug in the URL. It can technically be anything, but the convention is `year-month-date-keyword.md` for consistency (e.g., `2015-12-17-next-steps.md`). In that file, write a post by taking the following steps:
 
-1. Write meta data for sorting and linking. At the top of your markdown file, write meta data between `---` and `---` in YAML format.
+1. Sepcify meta data in YAML format, between `---` and `---`, at the top of your markdown post file. This is necessary for linking and sorting.
 
 ```yaml
 ---
-date: 2017-10-31 # required. year-month-date
-title: "Introducing Vega-Lite 2.0" # required. in quotes
+date: 2017-10-31 # required. year-month-date, in numbers.
+title: "Introducing Vega-Lite 2.0" # required. in double-quotes
 banner: "../blog-assets/images/2017-10-31-vegalite2-banner.webp" # optional. if provided, it appears before the title.
-paper: vega-lite # optional paper keyword. if provided, it will create a link to the paper under the title. 
-headlinener: "..." # optional if you want to have some special summary for your post. Make sure it is about 100 letters. If external is provided (see below), it is required. 
-external: URL # if it is posted on an external blog, then just provide that url here. While you are still need to say something in the post for parsing purposes, it will be ignored. To do so, headliner must be provided.
+paper: vega-lite # optional. if provided, it will create a link to the paper under the title (in the post page). 
+headliner: "..." # (1) optional, if your post is not external (i.e., there is content below this meta data section) and you want to have some custom summary for your post
+                 # (2) required, if your post is external (i.e., the below `external' field is provided) 
+                 # For both cases, make sure it is about 100 letters for the layout purposes. 
+external: URL # if it is posted on an external blog, then just provide that url here. While you are still need to say something in the post for the parsing purposes (put something like "external post"), it will be ignored. When this field is provided, then the above "headliner" field is required. This will be checked when you run the test script.
 ---
 ```
 
@@ -105,8 +107,25 @@ external: URL # if it is posted on an external blog, then just provide that url
 </div>
 
 *Your caption goes here.*
+```
+
+  c. A display text:
+```
+<p class="display">Some text</p>
+```
+
+  d. A quote (Note: markdown formatting does not work within a `<blockquote>` tag, so any formatting, such as boldface or italic, must be specified using HTML):
+```
+<blockquote>
+Some text <em>italic</em> and <strong>bold</em>
+</blockquote>
+```
+
+  e. A space divider (This will be rendered as a short, center-aligned horizontal line):
+```
+* * *
 ```
 
 3. Store images in `static/blog-assets/images` directory. For maintenence purposes, name your images starting with your post's file name.
 
-4. Supported headlines `<h2>` (`##`) and `<h3>` (`###`).
+4. Supported headings `<h2>` (`##`) and `<h3>` (`###`).

src/lib/pasre-post.ts

@@ -10,7 +10,7 @@ export function parsePostData(text: string, web_name: string): BlogPost {
   }
   const meta: BlogPostMeta = {
     date: metaRaw.date,
-    display_date: metaRaw.date ? (new Date(metaRaw.date + " PST")).toLocaleDateString("us-EN", {
+    display_date: metaRaw.date ? (new Date(metaRaw.date.replace(/-/g, "/") + " PST")).toLocaleDateString("us-EN", {
       year: "numeric",
       month: "short",
       day: "numeric",
@@ -21,6 +21,9 @@ export function parsePostData(text: string, web_name: string): BlogPost {
   if (metaRaw.banner) meta.banner = metaRaw.banner;
   if (metaRaw.headliner) meta.headliner = metaRaw.headliner;
   if (metaRaw.external) meta.external = metaRaw.external;
+  if (meta.external && !meta.headliner) {
+    console.error("An external post must have a headliner.");
+  }
   if (metaRaw.paper) meta.paper = metaRaw.paper;
 
   const post = parts.length == 3 ? parts[2] : parts[0];

src/lib/post-thumb.svelte

@@ -13,9 +13,13 @@
     <div class="thumbnail mb-2 md:mt-1 grow-0 shrink-0 mr-5">
       <div
         class="rounded-lg w-[120px] h-[80px] post-thumb-image"
-        style={`background-image: url(${post.first_image})`}
+        style={`background-image: url(${base}/${post.first_image})`}
       ></div>
     </div>
+  {:else}
+    <div class="thumbnail mb-2 md:mt-1 grow-0 shrink-0 mr-5">
+      <div class="rounded-lg w-[120px] h-[80px]" style={`background-color: white;`}></div>
+    </div>
   {/if}
   <div class="leading-tight">
     <div class="md:block">

src/routes/blog/[slug]/+page.svelte

@@ -23,7 +23,6 @@
     await navigator.clipboard.writeText(url);
     alert('Copied the URL to clipboard.');
   }
-  console.log(paper);
 </script>
 
 <svelte:head>
@@ -69,9 +68,7 @@
 {#if !meta.external}
   <Markdown {content} />
 {:else}
-  This is an external post. Click <a href={meta.external} target="_blank" rel="noopener noreferrer"
-    >here</a
-  > for redirection.
+  This is an external post. Click <a href={meta.external} target="_blank" rel="noopener noreferrer">here</a> for redirection.
 {/if}
 
 <!-- share -->

src/routes/blog/[slug]/+page.ts

@@ -24,7 +24,6 @@ export const load: PageLoad = async ({ params, fetch }) => {
   // find paper
   const paper = post.meta.paper ? await fetch(`${base}/papers/${post.meta.paper}.json`)
     .then((x) => x ? x.json() as Promise<Paper[]> : null) : null;
-  console.log(paper)
 
   const posts = await fetch(`${base}/blog-index.json`)
     .then((x) => x.json() as Promise<BlogPost[]>);

static/blog-assets/posts/2019-08-12-errudite.md

@@ -57,7 +57,7 @@ The problem is, an error group defined in this way is subjective, and experts ca
 In fact, in our user study we observed such inconsistencies even for simple group definitions (please see our paper for details!): When given identical descriptions of an error type from a prior published analysis and asked to reproduce it, our expert users produced groups that vary in size from 13.8% to 45.2% of all errors — which further illustrates the ambiguity in subjective manual labeling. This leads us to our first principle:
 
 <blockquote>
-**P1: Error hypotheses should be defined precisely with concrete descriptions.**
+<em>P1: Error hypotheses should be defined precisely with concrete descriptions.</em>
 </blockquote>
 
 * * *