Engineering
blueprint-document-reference avatar

blueprint-document-reference

Guide for creating, editing, and maintaining Adobe Digital Experience Blueprints with standard architecture, documentation, and content structures.

Introduction

This skill acts as an authoritative reference for technical writers and architects managing the Adobe Digital Experience Blueprints repository. It provides the structural standards and editorial guidelines necessary to produce high-quality, repeatable implementation blueprints that address complex business and technical challenges within the Adobe Experience Platform ecosystem. The skill ensures that all content adheres to repository conventions, including frontmatter requirements, section ordering, diagram standards, and consistent linking practices to Adobe Experience League documentation.

  • Standardizes blueprint structure including H1 headers, applications lists, use cases, prerequisites, guardrails, and implementation steps.

  • Defines technical frontmatter requirements such as title, description, solution categorization, exl-id management, and doc-type assignment.

  • Enforces external documentation best practices, specifically linking to Adobe Experience League for APIs, tutorials, and product guardrails instead of duplicating long-form content.

  • Manages content hierarchy including repository structure, TOC.md updates, and the differentiation between overview pages and specific scenario blueprints.

  • Provides templates for architecture diagrams, ensuring technical consistency and visual clarity for complex system and data flow integrations.

  • Use this skill when initiating a new blueprint document or modifying existing technical architecture pages.

  • Follow the defined schema for frontmatter to ensure correct publishing flow and search indexing.

  • Always cross-reference the reference.md file provided within the repository for specific URL patterns and linking conventions.

  • Ensure all architecture diagrams contain descriptive alt text and adhere to accessibility guidelines.

  • When adding new pages, remember to update help/blueprints/TOC.md to maintain repository navigation integrity.

  • Prioritize linking to official documentation rather than drafting custom technical procedures to ensure information remains accurate and up-to-date with product releases.

Repository Stats

Stars
1
Forks
8
Open Issues
11
Language
Not provided
Default Branch
main
Sync Status
Idle
Last Synced
May 3, 2026, 08:31 PM
View on GitHub