> For the complete documentation index, see [llms.txt](https://visualonecompany.gitbook.io/storyframeworkdocs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://visualonecompany.gitbook.io/storyframeworkdocs/getting-started/quickstart/content-browser.md).

# Content Browser

To understand any already setup project, we'll first start by how Story Frameworks assets and content are structured within the content browser.

***

<div align="left"><figure><img src="https://2310584459-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuiMQl6UzBr8OnuaoaiWO%2Fuploads%2FNrErena1bGdrYNQ9Ig5n%2Fimage.png?alt=media&amp;token=a33bcb83-bb49-4b4c-b7c3-0e8e2032c188" alt=""><figcaption></figcaption></figure></div>

The "root" Story Framework folder will contain the following content;

**Core**\ <sup><mark style="color:$info;">This homes all of the core systems, widgets, and general content for Story Framework.<mark style="color:$info;"></sup>\
**Example**\ <sup><mark style="color:$info;">This folder contains content that is not technically "needed". Core systems should not depend on anything within this folder. Content found here is generally used either to demonstrate something specific, or exclusively for the Sample Map.<mark style="color:$info;"></sup>\
**FrameworkSettings (Asset)**\ <sup><mark style="color:$info;">This asset is your frameworks configuration page. You'll find a long list of modifiable values that effects Core systems, widgets, and some other bonus contents.<mark style="color:$info;"></sup>\
**SFBlueprintStructure (Asset)**\ <sup><mark style="color:$info;">A general "helper" blueprint explaining how some of SF's blueprint graphs are structured for better understanding when modifying Core behaviour.<mark style="color:$info;"></sup>

***

<div align="left"><figure><img src="https://2310584459-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuiMQl6UzBr8OnuaoaiWO%2Fuploads%2FhKC9vZqME4Hx8mhoLw6L%2Fimage.png?alt=media&amp;token=d8d0741a-6fc7-4bb7-a958-1ccf615551c9" alt=""><figcaption></figcaption></figure></div>

Inside of the "Core" folder, you'll be greeted with 3 more folders;

**Editor**\ <sup><mark style="color:$info;">This folder contains all of the logic and extra assets specifically for SF's library of editor tools. This folder shouldn't contain anything you'd generally be looking for. For further context, this folder in its entirety is also excluded from packaged builds.<mark style="color:$info;"></sup>\
**Gameplay**\ <sup><mark style="color:$info;">This folder holds all of the assets for SF's Core systems, as well as "general" content shared between systems or content that is not system specific.<mark style="color:$info;"></sup>\
**SaveGame**\ <sup><mark style="color:$info;">This folder contains all assets relating to SF's save system workflow. If you're tampering with anything save-game in SF, this is where you'll find that content.<mark style="color:$info;"></sup>

***

<div align="left"><figure><img src="https://2310584459-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuiMQl6UzBr8OnuaoaiWO%2Fuploads%2FrfyZgH1eN0jik2yDbjpt%2Fimage.png?alt=media&amp;token=9e183d1c-e9da-468b-bb2b-1a6d358ef03f" alt=""><figcaption></figcaption></figure></div>

Inside of the "Gameplay" folder, each larger system is given its own folder. This makes searching for specific assets from a specific system quicker and easier.

<div align="left"><figure><img src="https://2310584459-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuiMQl6UzBr8OnuaoaiWO%2Fuploads%2FvCBqCEB6mWmdd0NDmU5r%2Fimage.png?alt=media&amp;token=8c4f4d89-acb2-4284-aec0-da0d05668086" alt=""><figcaption></figcaption></figure></div>

Inside of each systems folder, they generally share the same folder naming. For instance, both "Interaction" and "Inventory" can contain a "Data" folder. This keeps the folder structure in its entirety easier to follow and manage.

***
