🍯 Glaze

# Glaze Plan / TODO 🍯

This document tracks upcoming work for Glaze and its supporting Odin HTTP/library stack.

For a high-level description of what Glaze is, see `README.md`.

---

## Current Status

Glaze is a working web frontend for soft-serve.

It currently supports:

- Listing public repositories
- Reading repository visibility/configuration from `soft-serve.db`
- Browsing bare git repositories through libgit2
- Ref-aware tree/blob/raw URLs
- Tree listing and full path traversal
- Blob viewing with `
`
- Raw blob output
- Breadcrumb navigation
- Latest commit metadata on repo pages
- Rendered `README.md`
- Static assets and styling
- Custom templates
- Styled layout and visual identity
- Public Docker deployment

The HTTP layer is custom-built in Odin and currently supports:

- HTTP/1.x parsing
- keep-alive
- pipelining / carry buffer
- growing ring buffer
- thread-per-connection handling
- connection caps
- idle timeouts
- unsupported `Transfer-Encoding` rejection
- response header management
- static file serving
- routing
- route params
- middleware

---

## Immediate Priorities

### 1. Audit request/response memory lifetimes

Do a focused pass over the HTTP library and app code to confirm ownership rules.

Checklist:

- Request head/body memory lifetime is clear
- Route params do not outlive the request
- Response headers are always freed after sending
- Response bodies have clear ownership
- Middleware does not retain request-local memory accidentally
- Static file handling closes all file descriptors
- Connection job memory is freed after socket close
- Active connection counter decrements via `defer`
- No thread-local arena data leaks into shared/global caches
- Template-rendered output ownership is clear
- Error response paths clean up correctly

Goal:

- Make request/response lifecycle boring, predictable, and leak-free.

---

### 2. Refine template data model

The current template system works, but the data model should be simplified.

Current syntax:

```html
{{field}}

{{#block}}
  ...
{{/block}}
````

Desired direction:

* Split template data into fields and blocks
* Keep logic in Odin
* Keep templates intentionally dumb
* Use explicit view models instead of passing domain objects directly
* Prefer strings and block lists over rich runtime types
* Escape normal fields by default
* Allow explicitly safe/raw HTML for trusted content such as rendered Markdown

Possible model:

```text
Template_Context
  fields: name -> string
  blocks: name -> []Template_Context
```

Goal:

* Make templates easier to reason about and easier to feed from handlers.

---

### 3. Add styled error pages

Now that templates exist, replace plain/default errors with Glaze-styled pages.

Pages to support:

* 400 Bad Request
* 404 Not Found
* 408 Request Timeout
* 413 Payload Too Large
* 431 Request Header Fields Too Large
* 500 Internal Server Error
* 503 Service Unavailable

Notes:

* App-level missing repos/files/refs should render styled 404s
* Hidden/private repos should return 404, not 403
* Low-level malformed requests may stay minimal if necessary
* Error rendering should be overridable by applications using the HTTP library

Goal:

* Make failure states feel like part of the site.

---

### 4. Add branch/ref UI

Ref support works through URLs, but it needs to be discoverable in the UI.

Ideas:

* Show current ref in repo header
* List branches
* List tags
* Add ref dropdown or simple selector
* Preserve current path when switching refs
* Link each ref to the corresponding tree page
* Consider separating branches and tags visually

Goal:

* Make branch/ref browsing usable without manually editing URLs.

---

## Near-Term App Improvements

### 5. Improve README rendering and Markdown styling

Rendered README support exists. Improve presentation.

Tasks:

* Style headings
* Style lists
* Style links
* Style inline code
* Style code blocks
* Style blockquotes
* Ensure rendered Markdown is safely handled as trusted HTML only after conversion
* Handle missing README gracefully

Goal:

* Make repo root pages feel polished.

---

### 6. Improve tree/blob UI

Small UX improvements for browsing.

Ideas:

* File size column
* File/directory icons
* Parent directory link
* Better blob header
* Raw/view toggle links
* Copy path link
* Better mobile layout
* Improved focus states
* Better hover states
* Optional line numbers for blob view later

Goal:

* Make code browsing smoother and more pleasant.

---

### 7. Add semantic/IndieWeb metadata

Basic metadata is now planned or partially in place.

Site-wide:

* `