`, so its images render at their full 240px.
**News list.** `- **May 10, 2026**: 🤗 We release the code of FreeOrbit4D!`: full date in bold with the colon outside the bold, an emoji at the start of the sentence, an exclamation mark at the end. Two items, newest first; the list starts directly under the heading with no blank line.
**Code blocks.** All `bash`, with `#` comment lines grouping clone, environment and checkpoint steps in Setup, and a trailing comment listing other demos on the Quick Start command. Output paths follow in inline code (`outputs/rendering/{scene_name}/...`).
**Screenshot plus steps.** In Custom Camera Trajectories, a centred `
` is followed by a three-item numbered list of UI actions with button names in inline code (`Generate Trajectory`, `Save`).
**Citation.** A bare `bibtex` block, `@inproceedings{cao2026freeorbit4d, ...}` with `=` aligned at column 16, braces protecting `{FreeOrbit4D}`, `{4D}`, `{SIGGRAPH}` and `{ACM}`, and a `pages` field.
## Imagery
| Image | Type | Source size | Markdown | Rendered at 920px | Placement |
|---|---|---|---|---|---|
| title.png | PNG logo, wordmark on a dark globe, transparent surround | 752×431 | `
` in `
` | 200×115 | top of the README |
| camel_input.gif and the other showcase GIFs | animated GIF, 30 frames | 320×185 (camel_input) | `![]()
` in `
` | about 257×149 (shrunk by the table) | showcase table, columns 1 and 3 |
| camel_inter.png and the other viewer thumbnails | PNG render of the 4D point cloud with a rainbow camera path on white | 1850×1158 | `![]() ` | about 257×161 | showcase table, column 2 |
| bear_traj1.gif and the other trajectory GIFs | animated GIF, 30 frames | 240×138 (bear_traj1) | `![]() ` | 240×138 | comparison table, all columns |
| viser.png | PNG screenshot of the trajectory editor | 3042×1678 | `` in `` | 760×419 | Custom Camera Trajectories |
| mask.png | PNG screenshot of the Gradio mask UI | 1928×1478 | ` ` in ` ` | 600×460 | Run on Your Own Video, Step 1 |
The showcase is built from fifteen GIFs (six in the first table, nine in the second) and three linked PNGs arranged in two tables, so the results play inline without any embedded video. Only `mask.png` has `alt` text. Images have light or photographic backgrounds and no `` dark variants; the logo's dark globe is the only dark block on the page.
## Adapting to Other Content
- **A video method without an interactive viewer.** Keep the two-table pattern: a full-width table of Input / Ours (or Input / Baseline / Ours) at `width="280"`, then a narrower table of one input against variations at `width="240"`.
- **An image method.** Use the same bordered `` grid with PNG pairs at `width="280"` (three columns) or `width="400"` (two columns, about 856px total), keeping the bold header row.
- **A dataset.** Keep the logo, title, venue, badges and authors, and make the showcase table one row per category with sample clips; add a Download section with a pipe table before Installation.
- **A library.** Drop the authors and TL;DR, keep the 200px logo and the badge pair (Docs, PyPI), and replace the showcase with a two-column table of code snippet and output image.
- **A repo without demos.** Let the TL;DR close the header and move Quick Start up; the h3 linked title and h4 venue still give a compact header without a rule.
## Do's and Don'ts
| Do | Don't |
|---|---|
| Put results in a bordered `` with bold column labels | Stack GIFs one above another with no labels |
| Keep every image in one table at the same `width` | Mix widths within a row |
| Link interactive results from a thumbnail and say so in `(click to explore)` | Hide the viewer link in body text |
| Use one TL;DR sentence under the authors | Repeat the full abstract in the header |
| Check that the bibtex entry parses (FreeOrbit4D's misses a comma after `title`) | Leave citation fields unchecked |
| Point the badge and in-text project links to the same URL | Use two different hosts for the project page |
## Agent Prompt Guide
1. "Write a README header in GitHub HTML: a centred `` with a logo at `width="200"`, then `### [Full paper title](https://arxiv.org/abs/XXXX.XXXXX) ` so the title is a blue #0969da h3 link, a centred `` venue line, a centred `` with two `?style=for-the-badge` badges (Project PAGE `green` #67ac09, arXiv #b31b1b, label #555555), a centred author line with `` affiliation numbers, a centred affiliation line, and a centred bold `` TL;DR sentence."
2. "Under the TL;DR, build a results showcase as `` with a header row of bold labels Input Video, Interactive 4D (with `
(click to explore)`), Output Video, and three example rows of `![]() | `, linking the middle thumbnail to the viewer. Follow it with `### Multiple Trajectories from a Single Input` and a second table of Input Video, Trajectory #1, Trajectory #2 at `width="240"`."
3. "After the showcase, write `##` sections in this order: 🔥 News (bold full dates), Installation (with an h3 Setup `bash` block), Quick Start, Custom Camera Trajectories (a centred 760px screenshot and a numbered list), Run on Your Own Video (h3 Step 1 and Step 2), Citation, Acknowledgements. Use `bash` for every command block."
## Similar Pages
- readme-microsoft-renderformer also opens with a logo above the title, venue and author line, but shows results as one gallery image and navigates with bold text links instead of badges.
- readme-deepmancer-hairport uses the same `for-the-badge` style, with seven badges and numbered paper figures rather than a table of GIFs.
- readme-sisyphm-studiorecon covers a neighbouring 4D reconstruction topic with a single composite teaser and a stage table instead of a clip grid.
## Quick Start
````markdown
### [ProjectName: Full Paper Title](https://arxiv.org/abs/XXXX.XXXXX)
Venue Year
Author One1,
Author Two2
1Institution A, 2Institution B
TL;DR: One sentence that states the contribution.
| Input Video |
Interactive 4D
(click to explore) |
Output Video |
 |
 |
 |
### Multiple Trajectories from a Single Input
| Input Video |
Trajectory #1 |
Trajectory #2 |
 |
 |
 |
For more results, please visit our [project page](https://example.org/project/).
## 🔥 News
- **Month D, YYYY**: 🤗 We release the code!
## Installation
### Setup
```bash
# Clone the repository and its submodules.
git clone --recursive https://github.com/org/name.git
```
## Quick Start
```bash
python run_pipeline.py full --config configs/scenes/example.yaml
```
## Custom Camera Trajectories
1. Step one.
2. Step two.
## Run on Your Own Video
### Step 1 — Prepare the input
### Step 2 — Run the pipeline
## Citation
```bibtex
@inproceedings{key,
title = {...},
}
```
## Acknowledgements
````
## Provenance
- Repo: https://github.com/VVeiCao/FreeOrbit4D (`README.md`, branch `main`, last README commit 700ead9 on 2026-08-12).
- Paper: "FreeOrbit4D: Training-Free Arbitrary Camera Redirection for Monocular Videos via Foreground-Complete 4D Reconstruction", SIGGRAPH Conference Papers '26 (SIGGRAPH 2026), arXiv 2601.18993; first author Wei Cao. Project page https://freeorbit4d.vision.ischool.illinois.edu/.
- Selection: builds the results showcase as bordered HTML tables (input, interactive 4D, output, then input versus two trajectories), a clear grid pattern for video work that stays neat under a small logo and TL;DR line.
- Evidence: raw Markdown and GitHub-rendered HTML (saved 2026-10-28), 1440×900 and 2700px captures at a 920px README column, shields.io SVGs for both badge URLs, the logo, one showcase GIF, one viewer PNG, one trajectory GIF and both screenshots fetched from the repo for pixel sizes and frame counts.
- Written 2026-10-28.
| 
` lines, Project Page and arXiv. Each badge is 28px tall; the row is about 305px wide (136 + 165 px plus a gap). Details in Badges.
5. **Authors** (y≈411): `