Whitespae [#1005]

static-site/content/blog/2019-10-21-auspice-v2.md

@@ -181,7 +181,7 @@ See [requests made from the client](https://nextstrain.github.io/auspice/customi
 ## Improvements in the entropy panel
 
 We improved the usability of the entropy (genomic diversity) panel, as well as fixing a few hidden bugs -- see [PR #771](https://github.com/nextstrain/auspice/pull/771).
-For instance, you can now see which codon a nucleotide codes for (and vice-versa). 
+For instance, you can now see which codon a nucleotide codes for (and vice-versa).
 
 ![entropy](img/v2-entropy.gif)
 
@@ -211,4 +211,4 @@ We have now generalised this, and the [getAvailable API request](https://nextstr
 ## `auspice view` uses a custom Auspice client if present
 It's possible to use `auspice build` to [build a custom auspice client](https://nextstrain.github.io/auspice/customise-client/introduction).
 If this has been done, then running `auspice view` will serve it -- before you had to run `auspice view --customBuild`.
-This streamlines generating custom auspice bundles and serving them locally.
+This streamlines generating custom auspice bundles and serving them locally.

static-site/content/blog/2022-04-29-SARS-CoV-2-clade-naming-2022.md

@@ -18,7 +18,7 @@ Our revised set of guidelines will therefore now be to designate a clade when an
   2. A clade reaches >20% global frequency for 2 or more months
   3. A clade reaches >30% regional frequency for 2 or more months
   4. A clade shows consistent >0.05 per day growth in frequency where it's circulating and has reached >5% regional frequency
-  
+
 Additionally, for points 2, 3, and 4, we require the clade to show multiple mutations in S1 or particular mutations of known biological relevance.
 
 As a result of this, we are designating 3 new Nextstrain clades:

static-site/pages/blog.jsx

@@ -19,7 +19,7 @@ export default function Index({redirectTo}) {
 
 /**
  * Return the URL for the latest blog post
- * 
+ *
  * Note that we cannot return a redirect property here as that's not
  * useable for statically generated sites. See
  * <https://nextjs.org/docs/pages/api-reference/functions/get-static-props#redirect>

static-site/pages/blog/[id].jsx

@@ -23,11 +23,11 @@ export const getStaticPaths = (async () => {
     fallback: false // any paths not defined will result in a 404 page
   }
 })
- 
+
 /**
  * For a given id (matching the route /blog/id via the dynamic routing filename `blog/[id].jsx`)
  * return the params to be parsed to the rendering component.
- * 
+ *
  * Note: The context.params.id is set to one of the entries in the array returned from
  * `getStaticPaths`. See <https://nextjs.org/docs/pages/api-reference/functions/get-static-props>
  */

static-site/src/util/blogPosts.js

@@ -13,7 +13,7 @@ export function getBlogPosts() {
   const postsDirectory = path.join(__dirname, "..", "..", "content", "blog")
   const markdownFiles = fs.readdirSync(postsDirectory)
     .filter((fileName) => fileName.endsWith(".md"));
-  
+
   const blogPosts = markdownFiles.map((fileName) => {
     const {data: frontmatter, content: mdstring, isEmpty} = matter(
       fs.readFileSync(path.join(postsDirectory, fileName), 'utf8')
@@ -37,4 +37,3 @@ export function getBlogPosts() {
 
   return blogPosts;
 }
-