# Production Plan

Дата: 2026-05-21  
Goal: turn the static prototype into a maintainable public portal.

## Recommended Stack

### MVP

- Static site or Next.js static export.
- Git-backed content in Markdown/JSON.
- No wallet connection.
- No user accounts.
- Manual review for all project and safety-sensitive content.

### Phase 2

- Headless CMS or GitHub-based editorial workflow.
- GitHub issue import for contribution tasks.
- Forum/RSS/API import for discussion highlights.
- Newsletter provider for Weekly Ergo Pulse.
- Event calendar via ICS or a lightweight events collection.
- Provider login for trollbox identity: X/Twitter, Reddit, Telegram and Discord.
- Moderated Telegram/Discord/Web message relay for the trollbox.

### Phase 3

- Contribution profiles connected to provider identity.
- Moderated profile pages.
- Attestations for completed contributions.
- AI assistant over approved source index only.
- Admin dashboard for stale checks and verification.

## Repository Structure

```text
ergocommunity.org/
  app/
  components/
  content/
    projects/
    tasks/
    proposals/
    pulse/
    local/
  data/
    official-links.json
    status-labels.json
  public/
  scripts/
    check-links
    import-github-issues
    verify-projects
```

## Content Workflow

1. Contributor submits project/task/proposal update.
2. Editor checks completeness.
3. Safety reviewer checks risky links.
4. Maintainer approves.
5. Site rebuilds.
6. Weekly stale check flags old records.

## Integrations

### GitHub

Use for:

- good first issues
- open bounties
- release notes
- code contribution proof

### ErgoForum

Use for:

- governance discussions
- proposal summaries
- long-form debates
- weekly digest links

### ErgoDocs

Use for:

- beginner learning
- developer docs
- mining guides
- official contribution references

### Official Domains Page

Use for:

- wallet link verification
- social link verification
- official/community boundary
- safety warnings

### Trollbox Message Relay

Use for:

- Telegram group/channel mirroring through a Telegram bot.
- Discord channel/thread mirroring through a Discord bot.
- Web trollbox messages through a first-party backend.
- Dedupe, rate limits, audit trail and moderation state before cross-posting.

Production rule: Telegram, Discord and web trollbox messages must pass through one relay envelope. Do not let platforms repost directly into each other; direct reposting creates echo loops and weak moderation.

## Backlog

### Must Have

- Role paths
- Contribution board
- Project cards
- Trust center
- Weekly pulse
- Launch checklist
- Project intake

### Should Have

- GitHub issue import
- Events calendar
- Local community pages
- Campaign studio
- Governance summaries
- Contributor spotlight
- Moderated trollbox with provider identity
- Telegram/Discord bridge through Message Relay

### Could Have

- Contributor profiles
- Proof-of-contribution badges
- AI search assistant
- Project health scoring
- Builder incubator workflow
- Cross-room quoting from trollbox into Work Board tasks

### Not For MVP

- Wallet login
- Token-gated access
- Automated reward payouts
- Full social network
- Financial recommendations
- Unmoderated public chat

## Acceptance Criteria

The production portal is ready when:

- Every public external link has a source and review state.
- Every project card has a last checked date.
- Every task has an owner and proof requirement.
- Every role path ends in an action.
- Weekly pulse can be published without engineering work.
- Safety page is visible from every major path.
- Trollbox messages have provider identity, moderation state and rate limits before public launch.
- There is a documented stale-content removal process.