# ampproject/wg-amp4email architecture

> Architecture diagram of the GitHub repository ampproject/wg-amp4email, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-05-16). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/ampproject/wg-amp4email
- Repository: https://github.com/ampproject/wg-amp4email

## Overview

##### Project type and purpose
- This is not a runnable codebase or a full-stack application: it’s a coordination repository for the “AMP for Email” Working Group. Its primary goal is to host meeting agendas, status-update templates, issue templates, Code of Conduct, and to serve as the canonical place where the WG publishes its bi-weekly status updates and events.

##### File structure
- Top level:
- .github/ISSUE_TEMPLATE – Markdown files for “discussion,” “meeting-agenda-notes,” and “status-update” templates.
- CODE_OF_CONDUCT.md – The WG’s code of conduct.
- LICENSE.txt, METADATA.yaml – Licensing and repository metadata.
- README.md – An overview of the WG, its members, and communication channels.
- No source code or service definitions are present; instead, the repo produces and maintains documentation.

##### README for additional insights
- Describes the “AMP for Email” spec working group, members, and facilitator.
- Lists communication channels: GitHub issues (with templates), Slack, and a mailing list.
- Points external bug/feature tracking to the amphtml repository.

a. Main components
- Working Group (stakeholders)
- wg-amp4email GitHub repository (templates & status updates)
- amphtml repository (actual email spec)
- GitHub Issues & Pull Requests
- Slack channel (#wg-amp4email)
- Mailing List
- General AMP community / external collaborators
b. Relationships & interactions
- WG members use the repo’s issue templates to file status updates and meeting agendas.
- External contributors open spec issues in amphtml repo (not here).
- WG discusses in Slack; archives decisions in this repo and amphtml.
- WG sends announcements via mailing list; channels feedback back into GitHub issues.
c. Architectural patterns / design principles
- “Centralized coordination” pattern: this repo is the WG’s authoritative coordination hub.
- Separation of concerns:
- Spec lives in amphtml repo
- Coordination and status updates live here
- Communication via Slack and mailing list
d. Key technologies / platforms
- GitHub (repo, issue templates, issues/PRs)
- Markdown (templates and docs)
- Slack (real-time discussion)
- Google Groups (mailing list)

## Diagram (Mermaid)

```mermaid
flowchart TD
    subgraph "User Roles"
        WGMembers("WG Members"):::orange
        ExtContrib("External Contributors"):::orange
    end

    subgraph "Repositories"
        subgraph "wg-amp4email Coordination Hub"
            WGHUB("wg-amp4email Repository"):::repo
            subgraph "Issue Templates"
                Discussion("discussion.md"):::repo
                MeetingAgenda("meeting-agenda-notes.md"):::repo
                StatusUpdate("status-update.md"):::repo
            end
            subgraph "Supporting Docs"
                Readme("README.md"):::repo
                Metadata("METADATA.yaml"):::repo
                License("LICENSE.txt"):::repo
                CodeConduct("CODE_OF_CONDUCT.md"):::repo
            end
        end
        AmpHTML("amphtml Repository"):::repo
    end

    subgraph "Communication Channels"
        Slack("Slack #wg-amp4email"):::channel
        MailingList("Mailing List"):::channel
    end

    WGMembers -->|"post status update"| WGHUB
    WGMembers -->|"file spec issue"| AmpHTML
    ExtContrib -->|"file spec issue"| AmpHTML
    WGMembers <-->|"discuss"| Slack
    Slack -->|"archive decisions"| WGHUB
    Slack -->|"archive decisions"| AmpHTML
    WGHUB -->|"announce updates"| MailingList
    MailingList -->|"feedback"| WGHUB

    click Discussion "https://github.com/ampproject/wg-amp4email/blob/main/.github/ISSUE_TEMPLATE/discussion.md"
    click MeetingAgenda "https://github.com/ampproject/wg-amp4email/blob/main/.github/ISSUE_TEMPLATE/meeting-agenda-notes.md"
    click StatusUpdate "https://github.com/ampproject/wg-amp4email/blob/main/.github/ISSUE_TEMPLATE/status-update.md"
    click Readme "https://github.com/ampproject/wg-amp4email/blob/main/README.md"
    click Metadata "https://github.com/ampproject/wg-amp4email/blob/main/METADATA.yaml"
    click License "https://github.com/ampproject/wg-amp4email/blob/main/LICENSE.txt"
    click CodeConduct "https://github.com/ampproject/wg-amp4email/blob/main/CODE_OF_CONDUCT.md"

    classDef repo fill:#E6F0FA,stroke:#0366D6,color:#0366D6
    classDef channel fill:#e6ffed,stroke:#28a745,color:#28a745
    classDef orange fill:#fff5b1,stroke:#d69f00,color:#d69f00
```
