ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Your File Structure with EE 2?

August 25, 2010 12:58pm

Subscribe [6]
  • #1 / Aug 25, 2010 12:58pm

    PhireGuys

    525 posts

    Now that EE2 is out of beta, we’re finally implementing it for one of our clients.  I used to have a good system for my file structure with EE1, but now I’m not sure what is the best practice.

    What I mean by file structure are files that aren’t templates.  For example, images used in the actual layout of the site, scripts, flash files, and even css.  I used to have these all in a folder outside of the system directory, in the root.

    Now with the new file structure of EE2, what do people who use it do?  Where do you keep these files that aren’t ‘content’ but are part of the layout/design of the website you are building?

    Thanks!

  • #2 / Aug 25, 2010 1:27pm

    ender

    1644 posts

    we make a /resources/ directory in the web root with subfolders for js, css, swf, images, etc.  The benefit of this approach lets us poke a single ‘hole’ into the .htaccess index.php removal rule (just have to exclude anything starting with /resources/) as well as letting us manage the resources directory through subversion and not interfering with EE’s /images/ folder which may have user- or client-submitted content in it.

  • #3 / Aug 26, 2010 1:27pm

    PhireGuys

    525 posts

    Thanks for the reply.  Yeah, this was what we did for EE1, so I looks like it may be the best way for EE2 as well.

  • #4 / Aug 26, 2010 4:04pm

    John Ryan

    51 posts

    Yes, I take a similar approach. It leaves you with a lovely tidy site root!

  • #5 / Aug 26, 2010 4:30pm

    ender

    1644 posts

    Yes, I take a similar approach. It leaves you with a lovely tidy site root!

    I spy transmit 4 😉

  • #6 / Aug 27, 2010 10:18am

    PhireGuys

    525 posts

    Yes, I take a similar approach. It leaves you with a lovely tidy site root!

    I noticed you don’t have the root level images folder that EE comes with.  What do you do with that?  Isn’t it a hassle to have to remap it in EE?

  • #7 / Sep 04, 2010 8:50pm

    achilles

    2 posts

    Could someone give an example of “poke a single ‘hole’ into the .htaccess index.php removal rule”?

  • #8 / Sep 06, 2010 4:00am

    bensmithett

    3 posts

    Could someone give an example of “poke a single ‘hole’ into the .htaccess index.php removal rule”?

    Seconded. At the moment I just have seperate CSS, JS & images folders in the Root.

  • #9 / Sep 06, 2010 6:00pm

    Ben Lilley

    214 posts

    I noticed you don’t have the root level images folder that EE comes with.  What do you do with that?  Isn’t it a hassle to have to remap it in EE?

    Also curious about this as I’d love to move that bloody folder out of the site root, same with themes to be honest. My dream folder structure looks like this:

    /assets/ (my css/img/js)
    /templates/
    /system/
    index.php

    Alas my root folder currently looks like this:
    /assets/
    /templates/
    /system/
    /images/
    /themes/
    index.php

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases