Not signed in (Sign In)

SkillShare - A place to discuss Web Standards and Web Design topics

Categories

Vanilla 1.1.9 is a product of Lussumo. More Information: Documentation, Community Support.

    •  
      CommentAuthorSpookyET
    • CommentTimeJul 22nd 2006
     permalink
    I am tired of starting from scratch or almost scratch every time. So, I am designing a project template -- a site that would be the base of all sites.
    I am stuck at choosing the directory structure for 3rd party code (sIFR, SWFObject, etc.). Should I go UNIX-style (all binaries in /bin, all libraries in /lib) by dropping all css files in /styles, all javascripts in /javascripts, all images in /images or should I keep the files together and have /vendors/sIFR, /vendors/SWFObjects, etc.?

    Another issue is different versions. If name the files/directories foo.js, to upgrade the library, I just have to drop in the new foo.js. If I name it foo v1.0.js, I can drop in foo v1.1.js beside old version. The only problem is that all files that point to that library would have to be changed to use the new version. I'm not sure if this is an advantage since I use SVN, and I can revert to the previous version if the new version brakes something.
  1.  permalink
    Hey Spooky!

    I would recommend UNIX style but it's really up to you.
    It's very good Idea to come up with couple reuseble templates that can be used over and over again.
    Mostly saves you a lot of time for developing which mean you can complete more projects for the same
    time period.
    The logic behind directory stucture pretty much straignt forward.
    root/
    css/
    style01/
    style02/
    js/
    framework/
    php-bin/
    CMS/

    Cheers, DS
    •  
      CommentAuthorSpookyET
    • CommentTimeJul 22nd 2006 edited
     permalink
    You have not given a reason why UNIX-style is better. Should I bother with versioning -- prototype-1.4.0.js instead of prototype.js? Versioning is a hassle, but it might be worth it.
    If I get something useful going, I might post it online and create a community to edit it. Then, maybe we'll have a PHP-based site project template, FOO-Tech project template, etc.
    • CommentAuthorTim
    • CommentTimeJul 23rd 2006
     permalink
    Or you could use something like Ruby On Rails, Cake PHP, or some of the languages or frameworks that are outhere using the concept of Model, View, Controler... and (in part) the process is being simplified...
Add your comments
    Username Password
  • Format comments as (Help)