basantjamwal opened a new pull request, #2129:
URL: https://github.com/apache/apisix-website/pull/2129

   Fixes: #2098
   
   Changes:
   
   Blog posts with more than one author only showed the first author in the 
byline (for example, the 3.16.0 release post showed only "Abhishek Choudhary": 
https://apisix.apache.org/blog/2026/04/07/release-apache-apisix-3.16.0/). The 
cause was in the Astro site: `next/src/lib/content.ts` read only 
`authors[0]?.name` from the front-matter, so the other authors were dropped 
before the layout rendered them.
   
   - `next/src/lib/content.ts`
     - Added an `authorNames()` helper that returns every author name from 
`author` or from all entries of `authors` (object entries with a `name`, or 
plain strings).
     - `blogPost()` now sets `author` to all names joined with commas (used by 
the byline and post cards) and adds a new `authors` array to `Post`.
     - Added `authors?: string[]` to the `Post` interface.
   - `next/src/layouts/Article.astro`
     - The `BlogPosting` JSON-LD now lists every author as its own `Person`. 
Posts without an `authors` list keep the previous fallbacks (a single `Person`, 
or the Apache APISIX `Organization`).
   
   The change is limited to dated blog posts. Other post types are unchanged.
   
   Screenshots of the change:
   
   <img width="1920" height="1080" alt="Screenshot 2026-09-24 022812" 
src="https://github.com/user-attachments/assets/5b345da7-2cea-45fd-b485-49a81e125ed8";
 />
   
   
   Before (live site): only the first author is shown.
   
   After (local build, `npm run dev`): `Apr 7, 2026 · Abhishek Choudhary, Traky 
Deng · 8 min read`
   
   Testing:
   
   - Ran `npm run dev` in `next/` and checked 
`/blog/2026/04/07/release-apache-apisix-3.16.0/` and its `/zh/` version.
   - Checked that the page source contains one `Person` entry per author in the 
JSON-LD.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to