---
type: reference
title: "Wikifita Site — Front-Facing Publication Pipeline"
description: "Next.js site serving wikifita content publicly. Pushes to main branch update the live site at wikifita.aleffita.dev. Branch model separates public and personal content."
tags: [wikifita, site, nextjs, pipeline, deployment, personal-branch]
timestamp: "2026-07-17"
---

# Wikifita Site — Front-Facing Publication Pipeline

## Overview

Wikifita has a public-facing site at `wikifita.aleffita.dev` built with Next.js. Pushes to the `main` branch of the wikifita repository automatically update the live site content. This creates a controlled publication pipeline where the wikifita repo serves dual purposes: internal knowledge base and public-facing documentation.

## Architecture

```
wikifita (git repo)
├── main branch    → wikifita.aleffita.dev (public)
└── personal branch → private (never deployed)
```

### Branch Model

| Branch | Purpose | Deployed | Content |
|---|---|---|---|
| `main` | Public knowledge base + site content | Yes | Technical documentation, research, forensics, infrastructure |
| `personal` | Private notes, correspondence, sensitive references | No | Emails, salary negotiations, personal contacts, internal decisions |

**Rule:** Anything on `main` is potentially visible on the public site. Sensitive content goes on `personal` and is never merged to `main` without explicit review.

### Deployment Flow

1. Content is authored in the wikifita repo
2. `git push origin main` triggers site rebuild
3. Next.js site renders the updated content
4. Site live at `wikifita.aleffita.dev`

## Site Technology

- **Framework:** Next.js (TypeScript)
- **Location:** `~/Claude/wikifita-site/`
- **Deployment:** Docker (compose.yaml + Dockerfile)
- **Database:** Drizzle ORM
- **Proxy:** Custom proxy.ts for API routing

## What's Public vs. Private

### Always Public (main branch)
- Technical research (clickfix, kaggle, fitdnuvo, pesquisas)
- Infrastructure documentation (fitalabs, claude_desktop, mcp)
- Hacks and reverse engineering notes
- OKF conventions and methodology
- Public-facing skill documentation

### Personal Only (personal branch)
- Job search correspondence and salary negotiations
- Personal contacts with sensitive details
- Internal decision logs
- Anything containing credentials, phone numbers, or financial details
- Draft communications

## Workflow

### Publishing to the Site
```bash
# Work on main branch
git checkout main
# ... edit files ...
git add -A && git commit -m "docs: update content"
git push origin main
# Site rebuilds automatically
```

### Working with Personal Content
```bash
# Switch to personal branch
git checkout personal
# ... sensitive edits ...
git add -A && git commit -m "feat: add private reference"
# Never push personal to origin, or push to a private remote
```

### Merging Personal → Main (with review)
```bash
# Only when content has been sanitized for public display
git checkout main
git merge personal --no-ff
# Review diff carefully before pushing
git push origin main
```

## Related Pages

- [[clickfix-handoff]] — Example of public-facing technical content
- [[skills-architecture]] — How wikifita integrates with Claude Desktop/Cowork
- `CLAUDE.md` — Root instructions (canonical)

---
*This page documents the wikifita site pipeline. The site itself lives at wikifita.aleffita.dev.*