Structuring of Code about palomar

[jmohler1970]

I have 3 sources of inspiration on how to organize code. FW/1, Ruby on Rails, and Bootstrap.

FW/1

FW/1 is a MVC (model, view, controller) framework.

Models are further subdivided into beans (transients) and services (singletons).

HTML generation is divided into views, which happen early in request process and layouts which happen late in the request process

FW/1 Controllers are straight forward. Unlike ColdBox all variables are in the rc scope.

Ruby on Rails

Ruby on Rails provides a different set of inspiration. When a Ruby on Rails website is setup, all kinds of directories are created along with it. I have taken the most interesting and added them to the FW/1 mix. These directories are

controllers/concerns for re-used functions in various controllers
model/beans/concerns/ for re-used functions in various beans
model/services/concerns/ for re-used functions in various service

This application is so small, it does not have anything that would fall into those categories, but I like that there is a place for them.

vendor is used for all CSS, Fonts, and JS from 3rd parties.

These are considered to be static. For there is a CSS or JS file that will be altered, then it belongs in assets.

Bootstrap

Bootstrap is not free form its structure. The path for its fonts must be ../fonts/ For this reason vendor/fonts must exist.