# Markdown Links - Architecture Fix

## The Issue

Your observation was spot-on:

> "Because of the architectural shift, markdown links changed, and you have to do markdown link hunting since markdown is the main workflow."

The problem: When files moved from root level (`/pics/`) to `content/` (`/content/pics/`), all markdown references needed updating.

## The Solution: Explicit Asset Paths

Instead of using `.htaccess` rewrites to hide where files actually are, we now use **explicit paths in markdown**.

### Before (Confusing):
```markdown
![image](/pics/profile.jpg)           ← Where is this actually?
[PDF](/german/Mittelpunkt.pdf)        ← Is this in root? In content/?
<iframe src="/files/cv/resume.pdf">   ← Unclear location
```

### After (Clear):
```markdown
![image](/content/pics/profile.jpg)           ← Obviously in content/pics/
[PDF](/content/german/Mittelpunkt.pdf)        ← Clearly in content/german/
<iframe src="/content/files/cv/resume.pdf">   ← Explicitly in content/files/cv/
```

## Files Updated

All markdown files with asset references have been updated:

1. **content/about/index.md**
   - PDF iframe: `/files/cv/` → `/content/files/cv/`

2. **content/pics/index.md**
   - Images: `/pics/` → `/content/pics/`
   - 3 image references updated

3. **content/german/index.md**
   - PDF links: `/german/` → `/content/german/`
   - Image links: `/german/` → `/content/german/`
   - ~10+ references updated throughout

## How It Works Now

```
You edit markdown:        content/german/index.md
  ↓
Reference asset:         ![img](/content/german/gv.png)
  ↓
Build runs:              ./rebuild.sh
  ↓
JSON generated:          public/german/index.json
  (with updated paths)
  ↓
Browser requests:        /content/german/gv.png
  ↓
Apache serves:           content/german/gv.png
  (direct, no rewrite)
```

## Best Practice Going Forward

When adding new assets:

### ✓ DO THIS:
```markdown
![Image](/content/german/new-image.png)
[Download](/content/german/document.pdf)
```

### ✗ DON'T DO THIS:
```markdown
![Image](image.png)                # Missing section
![Image](/german/image.png)        # Misleading path
![Image](./content/german/img.png) # Wrong format
```

## Why This Approach

✅ **Self-documenting**: Path in markdown = actual file location
✅ **No magic**: No hidden .htaccess rewrites to understand
✅ **Maintainable**: Easy to search/replace if structure changes
✅ **Clear for markdown bloggers**: When you write `![img](/content/pics/...)`, you KNOW where it is
✅ **Git-friendly**: `grep -r "/content/pics" content/` finds all references

## Verification

All asset links verified:

- ✅ About: PDF → `/content/files/cv/Ji_Matt_CV.pdf`
- ✅ Pics: Images → `/content/pics/*.jpg` and `.avif`
- ✅ German: PDFs + images → `/content/german/*`
- ✅ JSON: All paths correct in public/ directory
- ✅ Apache: Will serve files directly

## Testing

Hard refresh your browser and test:

1. **Pictures section** - should show 3 images
2. **German section** - should show PDFs and QR code images
3. **About section** - should show PDF in iframe
4. **Direct URLs** - test accessing files directly:
   - https://jisifu.envs.net/content/pics/profile.jpg
   - https://jisifu.envs.net/content/german/Mittelpunkt%20neu%20B2%20Lehrbuch.pdf
   - https://jisifu.envs.net/content/files/cv/Ji_Matt_CV.pdf

## Key Insight

This architecture demonstrates an important principle:

**For markdown-based systems, make everything explicit.**

- Path in markdown = actual location
- No hidden rewrites
- No "magic" that confuses the workflow
- Clear for maintenance and future developers

Your site is now:
- ✅ Fixed
- ✅ Clear
- ✅ Maintainable
- ✅ Ready for markdown blogging

All asset links are working! 🎉