Skip to content

Generate the organization profile catalog from canonical data #9

Description

@Scriptception

Problem

The organization profile duplicates the website product list manually and already disagrees about which products appear and their stage.

User outcome

GitHub visitors see the same approved portfolio facts as website visitors without maintainers editing two catalogs.

Scope

  • Consume the publication-safe product manifest owned with the website workflow.
  • Generate the project-list section while preserving intentional profile-specific framing.
  • Make generated boundaries explicit so unrelated profile content remains hand-maintained.
  • Fail CI when generated output is stale.

Non-goals

  • Including non-public repositories or confidential portfolio data.
  • Turning the profile into a copy of the full website.

Acceptance criteria

  • Every profile project entry maps to one published manifest item.
  • Names, stages, summaries, and destinations match the website.
  • A deterministic generation check runs on pull requests.
  • New repositories do not appear without explicit publication approval.

Validation

  • Generate both surfaces from the same fixture and compare shared facts.
  • Test internal, archived, malformed, and unpublished manifest entries.

Relationships

  • Paired with IcebergAI/icebergai.github.io issue Create a canonical public product manifest.
  • Precedes profile catalog validation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationenhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions