v2.0.0

BlogLogistics Markdown for Agents v2.0.0

Version 2.0.0 changes the plugin to a fully user-controlled Markdown discovery model.

What's Changed

• Removed automatic Markdown generation for the homepage.
• Removed dynamic /index.md generation.
• Removed Accept: text/markdown content negotiation.
• Markdown content is now entirely user-managed and is never generated or rewritten by the plugin.
• Added support for curated Markdown companion files such as:
  • /index.md
  • /about-us/index.md
  • /notes/index.md
  • other matching /page/index.md files.
• Added support for a user-managed /llms.txt file.
• Added an administrator-run Markdown file scan.
• Matching Markdown URLs are stored as WordPress post/page metadata using:
  • bloglogistics_markdown_url
• Added per-page and per-post opt-out support using:
  • bloglogistics_markdown_disabled
• Added Markdown controls to the WordPress editor.
• Added central Markdown management under:
  • BlogLogistics → Markdown for Agents
• Pages without a matching Markdown file are automatically excluded.
• Public page requests do not scan the filesystem, probe Markdown URLs, generate Markdown, or make external requests.
• Eligible pages advertise their curated Markdown companion using rel="alternate".
• Eligible pages can advertise the site-managed llms.txt using rel="describedby".

Editorial Control

BlogLogistics Markdown for Agents does not create or modify Markdown content.

Site owners retain full control over:

• llms.txt
• all /index.md Markdown companion files
• which WordPress posts and pages advertise Markdown
• individual page/post exclusions

After adding, removing, or moving Markdown files, run Scan for Markdown Files from the plugin administration screen.

Upgrade Note

Version 2.0.0 replaces the previous dynamically generated Markdown model.

Sites upgrading from an earlier version should create and maintain their desired static Markdown files before relying on Markdown discovery.