# Application Resource Structure

**URL:** <https://forum.kirupa.com/t/application-resource-structure/256831>\
**Category:** programming\
**Created:** [April 7, 2008, 7:59pm UTC](https://forum.kirupa.com/t/application-resource-structure/256831 "2008-04-07T19:59:25Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![nobody](https://avatars.discourse-cdn.com/v4/letter/n/94ad74/32.png) [@nobody](https://forum.kirupa.com/u/nobody)\
**Post date:** [April 7, 2008, 7:59pm UTC](https://forum.kirupa.com/t/application-resource-structure/256831/1 "2008-04-07T19:59:25Z")

</div>

This is a question that bugs me and I think I fail at at it because I have no formal training.

How do you all store resources for a typical web app. My hierarchy is usually pretty weak changes based on every project. I’d really like to see an article on this, but I’d take first hand accounts.

If that didn’t make sense I’m referring to folder structure. Example:

```auto

Application
-design
--css
--images
-app
--conf
--classes
index.php

```