Home/ Questions/Q 1022153
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-16T11:25:23+00:00

In the public folder we have stylesheets, javascripts and images. I want to add

  • 0

In the public folder we have stylesheets, javascripts and images.

I want to add a front-end feature that has it’s own css, js and images, but according to this hierarchy i have to store them like this:

stylesheets/calendar/main.css
javascripts/calendar/cal.js
javascripts/calendar/cal2.js
images/calendar/front.jpg
images/calendar/button1.jpg
images/calendar/button2.jpg
images/calendar/button3.jpg

I don’t like that I split the feature up at all.

Is there a way to organize files per feature instead?

calendar/stylesheets/main.css
calendar/javascripts/cal.js
calendar/javascripts/cal2.js
calendar/images/front.jpg
calendar/images/button1.jpg
calendar/images/button2.jpg
calendar/images/button3.jpg

That would be a better structure, following OOP pattern.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    As the others mention, you can do pretty much anything you like.

    This is the system we are currently using:

    Place files inside directories corresponding to the “layout” they are applicable to:

    /web/images
/web/javascripts
/web/stylesheets

/mobile/images
/mobile/javascripts
/mobile/stylesheets

/admin/etc

    Top-level directories (/images /javascripts /stylesheets) are used for elements that are genuinely common (such as jquery, css reset scripts and standard logos).

    Client-side library packages be maintained in their own directory rather than spread out into the standard Rails directories. This greatly aids long term maintenance.

    Using colorbox as an example:

    Rather than:

     /javascripts/colorbox.js
 /stylesheets/colorbox.css

    We have:

     /web/libs/colorbox/colorbox.js
 /web/libs/colorbox/colorbox.css
    • 0