> ## Documentation Index > Fetch the complete documentation index at: https://docs.bravenlab.com/llms.txt > Use this file to discover all available pages before exploring further. # Project tabs, explained > What each tab in a project is actually for — Overview, Experiments, Devices, Analysis, Reports, and Pipelines. Every project has the same six sections, in the same order. This page is the short answer for "what is the X tab for" — each links out to a full guide where there's more to say. The project's "about" page — a project-level summary, not tied to any single experiment. Useful for orienting a teammate who's new to the project. Every experiment in the project, including ones with **no device linked yet** — this is deliberate: you shouldn't have to fix device linking before you can even find and open your data. Open one to see its files, Config, Summary, Series, and Figures. See the [data model](/concepts/data-model) for what each of those means. Experiments list in table view, showing measured and simulated battery cell experiments with Config and Summary columns like cathode_thickness_um, capacity_mAh, and internal_resistance_mOhm A **Card**, **Table**, or **Plot** view sits in the top-right of the list. Plot view turns the same Config/Summary columns into a scatter chart across every experiment — useful for spotting a trend (or checking that a real measurement landed where a simulation predicted) without leaving the list. See [Analyze and compare](/guides/analyze-and-compare) for the deeper comparison tool. Every physical device that's been linked to an experiment in this project, and its history over time. See [Devices](/concepts/devices) for how identity and linking actually work. The cross-experiment comparison view: pick series and figures from **multiple experiments** and overlay them on shared charts — the place you go to compare a slope across ten devices, or a curve across temperatures. Full guide: [Analyze and compare](/guides/analyze-and-compare). Turn an Analysis arrangement into something saved and shareable, instead of rebuilding the same comparison every time you want to show it to someone. Full guide: [Reports](/guides/reports). Write or reuse a pipeline script — like Devices, Pipelines are company-wide, so one written in another project shows up here too — assign it to a watched folder, and watch runs execute (queued / running / history). Full guide: [Write a pipeline script](/guides/write-a-pipeline-script). ## Inside an experiment Experiment detail page for a measured battery cell experiment, showing empty Config and Summary panels, a Figures list with a discharge curve, a linked Device, and the rendered discharge curve plot in the Images tab Opening an experiment gets you five sub-tabs: | Tab | What's there | | --------- | ---------------------------------------------------------------------------------------------------------------- | | Images | Rendered plots — PNGs from `braven.upload(fig, ...)`, including Figures (see [data model](/concepts/data-model)) | | Artifacts | Any other uploaded file — raw data, notebooks, anything not an image | | Notes | Free-text notes on the experiment | | Pipeline | The Runs that have executed against this experiment, their status, and their Config/Summary/Series output | | Script | The exact pipeline script version that produced this experiment's output, for traceability | The **Script** tab is what makes results traceable back to the exact code that produced them — if a pipeline script changes later, past experiments still show the script version that actually ran.