dominickm / jupiter_broadcasting_mobile_community

The Jupiter Broadcasting community project.
Other
100 stars 17 forks source link

Organization #22

Closed ograycode closed 11 years ago

ograycode commented 11 years ago

I think it has come time for some organization of the files. I think it's getting a little out of hand.

I purpose master goes something like:

Top Level
| .gitignore
| README.md
| License
| index.html
-|-Docs
--| COMMITPOLICY.md
--| Credits.md
-|-JQuery
--| All jquery files, like jquery 1.7.2 and jquery mobile
-|- JS 
--|all.js files
-|- CSS
--| all .css files
-|-images
--| same as now

Guide:

| top level item
-|- new_folder in top level
--| one level in

Anyways, does anyone else have a good organization schema? We may just want to make a Resources folder and put the JQuery, JS, CSS, and Images file into them. It will help when transferring to different platforms or updating existing ones, as then all you need to transfer the core of the application is index.html and the resources folder.

ShaneQful commented 11 years ago

I like it. We definitely need this. The root directory for the project is a little messy right now. Also lets put this in the docs so that new comers will know where everything is.

ograycode commented 11 years ago

Pull request sent for peer review, see https://github.com/dominickm/jupiter_broadcasting_mobile_community/pull/23

I did basic testing on it to make sure I didn't break anything in the process.

ghost commented 11 years ago

I quite like having the resources directory in place with the external code and assets inside it. I think if we have a manual or documentation directory that would be useful.

If we could create documentation for new comers would be useful.