fix displaying author(s)

Author: joshspicer

_layouts/post.html

@@ -2,16 +2,13 @@
 layout: singlePage
 ---
 <div class="container">
-    <p>{{ page.date | date_to_string }} - 
-    {% if page.authors.size == 1 %}
-        <a href="{{ page.authorUrl }}">{{ page.author }}</a>
-    {% else %}
-        Authors:
-        {% for author in page.authors %}
-            <a href="{{ author.authorUrl }}">{{ author.name }}</a>{% unless forloop.last %}, {% endunless %}
+    <p>{{ page.date | date_to_string }} -
+        {% assign i = 0 %}
+        {% for a in page.author %}
+            <a href="{{ page.authorUrl[i] }}">{{ page.author[i] }}</a>
+            {% assign i = i | plus:1 %}
         {% endfor %}
-    {% endif %}
     </p>
 
     {{ content }}
-</div>
+</div>

_posts/2022-11-01-author-a-feature.md

@@ -1,8 +1,10 @@
 ---
 layout: post
 title:  "Authoring a Dev Container Feature"
-author: "@joshspicer"
-authorUrl: https://github.com/joshspicer
+author:
+    - "@joshspicer"
+authorUrl:
+    - https://github.com/joshspicer
 ---
 
 Development container ["Features"](/features) are self-contained, shareable units of installation code and development container configuration. We [define a pattern](/implementors/features-distribution) for authoring and self-publishing Features.

_posts/2022-12-16-dockerfile.md

@@ -1,8 +1,10 @@
 ---
 layout: post
 title:  "Using Images, Dockerfiles, and Docker Compose"
-author: "@chuxel"
-authorUrl: https://github.com/chuxel
+author:
+  - "@chuxel"
+authorUrl:
+  - https://github.com/chuxel
 ---
 
 When creating a development container, you have a variety of different ways to customize your environment like ["Features"](/features) or [lifecycle scripts](/implementors/json_reference/#lifecycle-scripts). However, if you are familiar with containers, you may want to use a [Dockerfile](/guide/dockerfile#dockerfile) or [Docker Compose / Compose](/guide/dockerfile#docker-compose) to customize your environment. This article will walk through how to use these formats with the Dev Container spec.

_posts/2023-02-15-gitlab-ci.md

@@ -1,8 +1,10 @@
 ---
 layout: post
 title:  "Working with GitLab CI"
-author: "@raginjason"
-authorUrl: https://github.com/raginjason
+author:
+  - "@raginjason"
+authorUrl:
+  - https://github.com/raginjason
 ---
 
 For simple use cases you can use your development container (dev container) for CI without much issue. Once you begin using more advanced dev container functionality such as [Features](/features), you will need dev container tooling in your CI pipeline. While GitHub CI has the [devcontainers-ci GitHub Action](https://github.com/marketplace/actions/devcontainers-ci), there is no such analog in GitLab CI. To achieve the goal of using your dev container in GitLab CI, the container must be pre-built.

_posts/2023-06-14-feature-authoring-best-practices.md

@@ -1,8 +1,10 @@
 ---
 layout: post
 title:  "Best Practices: Authoring a Dev Container Feature"
-author: "@joshspicer"
-authorUrl: https://github.com/joshspicer
+author:
+  - "@joshspicer"
+authorUrl:
+  - https://github.com/joshspicer
 ---
 
 Last November I wrote about the basics around [authoring a Dev Container Feature](/guide/author-a-feature). Since then, [hundreds](https://containers.dev/features) of Features have been written by the community. The flexibility of Features has enabled a wide variety of use cases, from installing a single tool to setting up specific aspects of a project's development environment that can be shared across repositories.  To that effect, many different patterns for Feature authorship have emerged, and the core team has learned a lot about what works well and what doesn't.

_posts/2023-08-22-prebuild.md

@@ -1,10 +1,10 @@
 ---
 layout: post
 title:  "Speed Up Your Workflow with Prebuilds"
-authors:
+author:
   - "@bamurtaugh"
   - "@craiglpeters"
-authorUrls:
+authorUrl:
   - "https://github.com/bamurtaugh"
   - "https://github.com/craiglpeters"