Use this section for the paper-style abstract. It should briefly define the problem, describe the core idea, summarize the training or system design, and state the main empirical outcomes. This section should be readable on its own without requiring the rest of the page.
Project Template
Project Name Goes Here
A clean standalone project page for research systems, demos, and technical showcases.
This template is intentionally self-contained. It does not depend on Jekyll layouts, global CSS, remote fonts, or external JavaScript. You can copy this folder anywhere and open the file directly.
The section structure is designed for a research project page: abstract, method overview, data generation, qualitative demos, quantitative results, deeper analysis, resources, and citation.
- StatusTemplate
- FocusResearch Project Page
- FormatStandalone HTML
Abstract
One dense paragraph that explains the problem, method, and outcomeModel Overview
Method overview, architecture, or system diagramCore idea
Use this area for the high-level method explanation: what components exist, how they connect, and why this formulation is different from previous approaches.
System design
Use this card for pipeline stages, module responsibilities, pre-training versus post-training, or how planning, grounding, and control interact in the full system.
Data Generation
Use this when the project has synthetic, collected, or curated data pipelinesPipeline
Describe how data is generated or collected: simulation engine, annotation stages, intermediate labels, filtering rules, or asset sources.
Scale
Summarize dataset size, task diversity, modality composition, and any design choices that matter for readers trying to understand why the data is a contribution by itself.
Qualitative Results
Best for videos, GIFs, visual cases, and demo showcasesPrimary demo block
Demo Placeholder
Swap this for a featured video, embedded player, or image sequence.
Additional scenarios
- Instruction-following or task completion cases.
- Robustness, clutter, or long-horizon scenarios.
- Failure cases, comparisons, or real-world transfer.
Experimental Results
Tables, benchmark plots, ablations, and quantitative summariesMain benchmarks
Use this card for headline benchmark performance. A chart, table, or compact comparison block fits well here.
Ablations and studies
Use this card for component analysis, training recipe ablations, or scaling studies. It is especially useful when the project page needs to explain why a design choice matters.
Detailed Analysis
Use this for reasoning, visual diagnostics, or fine-grained capability breakdownsCapability slices
- Box / point / trace / plan / trajectory style analyses.
- Prompt sensitivity, grounding quality, or failure taxonomy.
- Human-readable evidence for what the model has learned.
Visualization block
Analysis Placeholder
Use for image grids, diagnostic examples, or capability visualizations.
Resources
Citation
BibTeX Placeholder
Use a copy button, code block, or plain citation text here.
Project Timeline
-
Mar 2026Initial public release of the project page.
-
Feb 2026Paper accepted, demo released, or benchmark update announced.
-
Jan 2026Project kickoff, teaser, or first internal milestone.