Skip to content

fix: correct invalid LinkedIn social handle in blog authors config#2

Draft
ayadseghairi with Copilot wants to merge 2 commits into
mainfrom
copilot/vscode-mnuip7qy-eped
Draft

fix: correct invalid LinkedIn social handle in blog authors config#2
ayadseghairi with Copilot wants to merge 2 commits into
mainfrom
copilot/vscode-mnuip7qy-eped

Conversation

Copilot AI commented Apr 11, 2026

Copy link
Copy Markdown

Docusaurus 3.10.0 requires author social values to be either a bare username/handle or a fully qualified https:// URL. The linkedin entry in blog/authors.yml was set to a partial path (in/ayad-seghiri/), causing the dev server to fail on startup.

Change

blog/authors.yml

  • Updated linkedin social value from partial path to absolute URL:
# Before
linkedin: in/ayad-seghiri/

# After
linkedin: https://www.linkedin.com/in/ayad-seghiri/
Original prompt

ayad@fedora:~/Documents/geekdz-docs$ npm run start

geekdz-docs@0.0.0 start
docusaurus start

[INFO] Starting the development server...

[ERROR] Error: Author socials should be usernames/userIds/handles, or fully qualified HTTP(s) absolute URLs.
Social platform 'linkedin' has illegal value 'in/ayad-seghiri/'
at normalizeSocialEntry (/home/ayad/Documents/geekdz-docs/node_modules/@docusaurus/plugin-content-blog/lib/authorsSocials.js:54:15)
at Array.map ()
at normalizeSocials (/home/ayad/Documents/geekdz-docs/node_modules/@docusaurus/plugin-content-blog/lib/authorsSocials.js:66:55)
at normalizeAuthor (/home/ayad/Documents/geekdz-docs/node_modules/@docusaurus/plugin-content-blog/lib/authorsMap.js:82:73)
at /home/ayad/Documents/geekdz-docs/node_modules/@docusaurus/plugin-content-blog/lib/authorsMap.js:87:16
at /home/ayad/Documents/geekdz-docs/node_modules/lodash/lodash.js:13500:38
at /home/ayad/Documents/geekdz-docs/node_modules/lodash/lodash.js:4998:15
at baseForOwn (/home/ayad/Documents/geekdz-docs/node_modules/lodash/lodash.js:3037:24)
at Function.mapValues (/home/ayad/Documents/geekdz-docs/node_modules/lodash/lodash.js:13499:7)
at normalizeAuthorsMap (/home/ayad/Documents/geekdz-docs/node_modules/@docusaurus/plugin-content-blog/lib/authorsMap.js:86:29)
[INFO] Docusaurus version: 3.10.0
Node version: v22.22.0

[Chronological Review: The conversation began with the user requesting updates to the `docusaurus.config.js` file to configure SEO and enable dynamic sitemap generation. The user specified exact changes to the `url`, `baseUrl`, and `sitemap` properties. The user then requested to create a new `sitemap.xml` file and later checked the local URL for the sitemap. Following that, the user requested to delete unnecessary files. The conversation culminated in the user attempting to start the Docusaurus development server, which resulted in an error related to author social links.]

[Intent Mapping:

  1. "Please update my docusaurus.config.js file to configure SEO and enable dynamic sitemap generation..." - User wants to enhance SEO and sitemap functionality.
  2. "new create the sitemap.xml file" - User wants to create a new sitemap file.
  3. "إحذف جميع الملفات الزائدة والتي لا فائدة منها" - User requests deletion of unnecessary files.
  4. "npm run start" - User attempts to start the Docusaurus server, indicating readiness to test changes.]

[Technical Inventory:

  • Docusaurus: A documentation framework being used for the tech club's platform.
  • Configuration file: docusaurus.config.js for SEO and sitemap settings.
  • Error handling: The error encountered relates to author social links in the blog plugin configuration.]

[Code Archaeology:

  • docusaurus.config.js: User requested specific updates to the url, baseUrl, and sitemap properties.
  • sitemap.xml: User requested its creation and later checked its accessibility.]

[Progress Assessment:

  • Completed Tasks: User has specified the necessary updates for the docusaurus.config.js file.
  • Partially Complete Work: The creation of sitemap.xml is pending confirmation of successful generation and the resolution of the Docusaurus server error.]

[Context Validation: All necessary context for continuing work on the Docusaurus configuration and sitemap generation is captured, including the recent error encountered.]

[Recent Commands Analysis:

  • Last Agent Commands: User executed npm run start to start the Docusaurus server.
  • Tool Results Summary: The command resulted in an error indicating that the author social link for 'linkedin' was improperly formatted, which needs to be corrected before the server can start successfully.
  • Pre-Summary State: The agent was actively working on starting the Docusaurus server when the token budget was exceeded.
  • Operation Context: The command was executed to test the recent configuration changes made to the Docusaurus setup.]
1. Conversation Overview: - Primary Objectives: - "Please update my `docusaurus.config.js` file to configure SEO and enable dynamic sitemap generation..." - "new create the sitemap.xml file" - "إحذف جميع الملفات الزائدة والتي لا فائدة منها" - "npm run start" - Session Context: The conversation focused on configuring a Docusaurus documentation platform, specifically enhancing SEO and sitemap functionality, followed by attempts to start the development server. - User Intent Evolution: The user transitioned from configuration requests to testing the setup, indicating readiness to implement changes.
  1. Technical Foundation:
  • Docusaurus: Version 3.10.0, used for building documentation sites.
  • Configuration: docusaurus.config.js for SEO and sitemap settings.
  1. Codebase Status:
  • File Name: docusaurus.config.js
    • Purpose: Configures the Docusaurus site settings.
    • Current State: Awaiting updates for SEO and sitemap generation.
    • Key Code Segments: Updates to url, baseUrl, and `site...

Created from VS Code.

Copilot AI changed the title [WIP] Fix illegal value for linkedin social platform fix: correct invalid LinkedIn social handle in blog authors config Apr 11, 2026
Copilot AI requested a review from ayadseghairi April 11, 2026 15:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants