# Wiki & Repository Needed Changes Tracker (`wiki needed changes.md`)

This document tracks all content updates, cleanups, structural refactorings, and link fixes needed in the **Fargo 3D Content Repository** (`Fargo3d/3DPrintMeetup`).

---

## 1. Folder-Based Cleanups (Deprecating Legacy Flat Wiki Tags)

Because the site now infers categories, archive status, and hub placement directly from **folder paths**, markdown files no longer require extensive YAML tags.

### Folder Inference Rules:
| Folder Path | Automatic Category | Automatic Status / Badging | Frontmatter Required? |
| :--- | :--- | :--- | :--- |
| `challenges/current/current.md` | `challenges` | **Active Challenge** | Optional (title inferred from `# H1`) |
| `challenges/current/upcoming.md` | `challenges` | **Upcoming Preview** | Optional |
| `challenges/current/readme.md` | `challenges` | Hub overview / Index | Optional |
| `challenges/archive/*.md` | `challenges` | **Archived Challenge** | Optional (year/month inferred from filename) |
| `tools/*.md` | `tools` | **Community Gear & Supplies** | Optional |
| `HueForge/*.md` | `hueforge` | **Guides & Calibration** | Optional |
| `announcements/*.md` | `announcements` | **Monthly Announcements** | Optional (date inferred from filename) |
| `/` (Root) | `meetup` | **General Meetup Info** | Optional |

---

## 2. Redundant Root Files Cleanup

With the migration to dedicated folders on `dev`, several duplicate files in the root can be archived or cleaned up once the website reads from folders:

- [x] **`Supporting-Our-Community.md`** (Root):
  - Duplicate of `tools/Supporting-Our-Community.md`. Can be removed once tools route points to `tools/`.
- [x] **`Current-Challenge.md`** & **`Upcoming-Challenge.md`** (Root):
  - Replaced by `challenges/current/current.md` and `challenges/current/upcoming.md`.
- [x] **`Challenge-Archive.md`** & **`challenges.md`** (Root):
  - Replaced by `challenges/readme.md` and `challenges/archive/readme.md`.
- [x] **`wiki-content-gitea/`** folder:
  - Legacy flat wiki mirror. Can be retired once the website is reading from the primary repo folders.

---

## 3. Link Standardization Across Markdown Files

In the legacy Gitea wiki, links were flat slugs (e.g. `[Itinerary](Itinerary)` or `[Active Challenge](Current-Challenge)`). For standard git repository browsing and web rendering:

- [x] Update `Home.md` / `Readme.md`:
  - Change `(Itinerary)` -> `(itinerary.md)`
  - Change `(Important-Dates)` -> `(Important-Dates.md)`
  - Change `(Ideas-and-Planning)` -> `(ideas.md)`
  - Change `(Current-Challenge)` -> `(challenges/current/current.md)`
  - Change `(Challenge-Archive)` -> `(challenges/archive/readme.md)`
  - Change `(Supporting-Our-Community)` -> `(tools/Supporting-Our-Community.md)`
- [x] Update `challenges/current/current.md`:
  - Change `[← Back to Challenges Hub](../readme.md)` (already clean relative link).
  - Verify link to `[Upcoming Preview](upcoming.md)`.
- [x] Update `challenges/archive/*.md`:
  - Update any backlink headers to `[← Back to Challenge Archive](readme.md)`.

---

## 4. HueForge & Structured Assets Tasks

- [x] **`HueForge/3d-Fuel.json`**:
  - Verify JSON structure is valid and contains latest colors. (Verified: 127+ color entries with Hex, Brand, Transmissivity, Type).
- [x] **`HueForge/README.md`**:
  - Add quick link to download `3d-Fuel.json` directly from the raw repo URL.

---

## 5. Frontmatter Simplification Standard

Authors no longer need to write 12 lines of YAML. The standard is now lightweight:

```yaml
---
title: "September 2026: Practi-FALL Prints"
order: 1
---
```
*(Category, active/archive status, and tags like `challenge` and `tools` are now inferred automatically by folder location).*