Create Multiple Blogs Instances

Just like with multiple docs folders, Docusaurus allows you to create multiple blogs by leveraging multiple instances of the @docusaurus/plugin-content-blog plugin. This is incredibly useful if you want to have distinct blog sections on your site, for example:

A main company blog
A developer blog
A product updates blog
A news or announcements section

Here's how to set it up:

1. Create your additional blog folders

First, create the directories for your new blogs. Let's say you have the default blog folder, and you want to add dev-blog and news. Your project structure might look like this:

my-docusaurus-site/
├── blog/
│   ├── 2023-01-01-hello.md
│   └── ...
├── dev-blog/
│   ├── 2024-03-15-tech-update.md
│   └── ...
├── news/
│   ├── 2024-07-20-company-announcement.md
│   └── ...
├── src/
├── static/
├── docusaurus.config.js
└── ...

2. Configure `docusaurus.config.js`

You'll modify your docusaurus.config.js to add multiple instances of the @docusaurus/plugin-content-blog. Each instance will point to a different blog folder and have a unique id.

// docusaurus.config.js

/** @type {import('@docusaurus/types').Config} */
const config = {
  // ... other configurations

  presets: [
    [
      "@docusaurus/preset-classic",
      /** @type {import('@docusaurus/preset-classic').Options} */
      ({
        docs: {
          // Default docs configuration
          path: "docs",
          sidebarPath: "./sidebars.js",
          editUrl:
            "https://github.com/facebook/docusaurus/tree/main/packages/create-docusaurus/templates/shared/",
        },
        blog: {
          // This is for your primary 'blog' folder
          path: "./blog", // The default 'blog' folder
          routeBasePath: "blog", // Base URL for this blog (e.g., yoursite.com/blog/...)
          showReadingTime: true,
          editUrl:
            "https://github.com/facebook/docusaurus/tree/main/packages/create-docusaurus/templates/shared/",
        },
        theme: {
          customCss: "./src/css/custom.css",
        },
      }),
    ],
  ],
  plugins: [
    [
      "@docusaurus/plugin-content-blog",
      /** @type {import('@docusaurus/plugin-content-blog').Options} */
      {
        id: "devBlog", // Unique ID for this blog instance
        path: "./dev-blog", // Path to your developer blog folder
        routeBasePath: "dev-blog", // Base URL for these blog posts (e.g., yoursite.com/dev-blog/...)
        showReadingTime: true,
        blogTitle: "Developer Blog",
        blogDescription: "Updates and articles for developers.",
        // You can add more options specific to this blog, like:
        // postsPerPage: 5,
        // feedOptions: { type: 'all' },
      },
    ],
    [
      "@docusaurus/plugin-content-blog",
      /** @type {import('@docusaurus/plugin-content-blog').Options} */
      {
        id: "news", // Unique ID for this blog instance
        path: "./news", // Path to your news blog folder
        routeBasePath: "news", // Base URL for news posts (e.g., yoursite.com/news/...)
        showReadingTime: false, // Maybe you don't need reading time for news
        blogTitle: "Company News",
        blogDescription: "Latest announcements and company updates.",
      },
    ],
  ],
  // ... rest of your config
};

module.exports = config;

Key points in the configuration:

plugins array: This is where you add additional instances of the blog plugin.
id: Crucial! Each blog instance must have a unique id. This is how Docusaurus distinguishes between them. The default blog instance (configured within preset-classic) has an implicit id of default.
path: Points to the directory where the Markdown files for that specific blog are located.
routeBasePath: Defines the URL segment for that blog. For example, if routeBasePath: 'dev-blog', your posts will be at yoursite.com/dev-blog/my-post.
Other options: You can customize options like blogTitle, blogDescription, postsPerPage, showReadingTime, etc., independently for each blog instance.

3. Add Blog Posts

Create Markdown files in your newly created blog directories. Remember to follow Docusaurus's blog post naming conventions (e.g., YYYY-MM-DD-your-post-title.md) or use front matter to specify the date.

Example dev-blog/2024-03-15-tech-update.md:

---
title: "Latest Tech Update"
description: "An overview of recent technical improvements."
authors: ["dev-team"]
tags: ["engineering", "release"]
---

# Latest Tech Update

This is a technical blog post about our recent system changes...

Example news/2024-07-20-company-announcement.md:

---
title: "New Partnership Announced!"
description: "Exciting news about our collaboration."
authors: ["pr-team"]
tags: ["company", "partnerships"]
---

# New Partnership Announced!

We are thrilled to announce our new partnership with...

Finally, update your docusaurus.config.js to add links to these new blog sections in your navbar:

// docusaurus.config.js

navbar: {
    title: 'My Site',
    // ...
    items: [
      {
        to: '/blog', // Link to your default blog
        label: 'Main Blog',
        position: 'left',
        activeBaseRegex: `/blog/`,
      },
      {
        to: '/dev-blog', // Link to your developer blog
        label: 'Developer Blog',
        position: 'left',
        activeBaseRegex: `/dev-blog/`,
      },
      {
        to: '/news', // Link to your news blog
        label: 'News',
        position: 'left',
        activeBaseRegex: `/news/`,
      },
      // ... other navbar items (docs, etc.)
    ],
  },

Now, when you run Docusaurus (npm run start or yarn start), you'll have distinct URLs and sections for each of your blogs!

Given the current date, I'll assume you're looking for an authors.yml file that would be compatible with Docusaurus and support the dev-team and pr-team author keys you mentioned.

Here's an example of an authors.yml file that defines these "teams" as authors, along with some common fields you might include for each:

# authors.yml

# --- dev-team ---
# This section defines a 'dev-team' author.
# It can represent a group or a generic author for development-related posts.
dev-team:
  name: The Development Team
  title: Engineering Department
  url: https://github.com/your-org-dev-team # Optional: Link to a team GitHub, internal dev portal, etc.
  image_url: https://docusaurus.io/img/docusaurus.png # Placeholder image
  # You can also add custom fields like:
  # twitter: yourdevteamhandle
  # email: dev@example.com

# --- pr-team ---
# This section defines a 'pr-team' author.
# Similar to dev-team, it represents a group or a generic author for PR/news posts.
pr-team:
  name: Public Relations Team
  title: Communications Department
  url: https://your-website.com/newsroom # Optional: Link to your newsroom or PR contact page
  image_url: https://docusaurus.io/img/docusaurus.png # Placeholder image
  # You can also add custom fields like:
  # twitter: yourprteamhandle
  # email: pr@example.com

# --- Individual Authors (Optional, but common) ---
# You can also define individual authors in the same file.
# For example, if 'dev-team' posts are sometimes attributed to individuals.
john_doe:
  name: John Doe
  title: Senior Developer
  url: https://github.com/john_doe
  image_url: https://docusaurus.io/img/docusaurus.png # Replace with John's actual image
  twitter: johndev

jane_smith:
  name: Jane Smith
  title: Communications Manager
  url: https://linkedin.com/in/jane-smith
  image_url: https://docusaurus.io/img/docusaurus.png # Replace with Jane's actual image
  twitter: janesmithpr

How to use this `authors.yml` in Docusaurus:

Place the file: Typically, you'd place authors.yml in your blog directory (or the specific blog directory if you have multiple, e.g., dev-blog/authors.yml or news/authors.yml). If you want to use the same authors.yml across multiple blogs, you can place it in a common location and reference it in each blog's configuration.

A common place is at the root of your blog folder:
- blog/authors.yml
- dev-blog/authors.yml
- news/authors.yml

Reference in Blog Posts: In your Markdown blog posts, you would reference these authors in the front matter using their keys (e.g., dev-team, pr-team).

For dev-blog/2024-03-15-tech-update.md:

---
title: "Latest Tech Update"
description: "An overview of recent technical improvements."
authors: ["dev-team"] # <-- This refers to the 'dev-team' key in authors.yml
tags: ["engineering", "release"]
---

# Latest Tech Update

...

For news/2024-07-20-company-announcement.md:

---
title: "New Partnership Announced!"
description: "Exciting news about our collaboration."
authors: ["pr-team"] # <-- This refers to the 'pr-team' key in authors.yml
tags: ["company", "partnerships"]
---

# New Partnership Announced!

...

You can also mix and match, or attribute to individual authors:

---
title: "Another Post"
authors: ["john_doe", "dev-team"] # Attributed to an individual and the team
---

Docusaurus will automatically pick up this authors.yml file when rendering your blog posts, displaying the name, title, and image specified for the corresponding author keys.

1. Create your additional blog folders​

2. Configure docusaurus.config.js​

3. Add Blog Posts​

4. Link in your Navbar​

How to use this authors.yml in Docusaurus:​

1. Create your additional blog folders

2. Configure `docusaurus.config.js`

3. Add Blog Posts

4. Link in your Navbar

How to use this `authors.yml` in Docusaurus: