Gooi will be a pureJs application scaffold. It will concentrate on the presentation layer and server connectivity of a web site. I expect that it will include some external plugins where they are available to take care of some of the underlining activities.
Gooi's topography will be explicitly represented on the file-system. The folder Gooi will represent the taxon, the top level of the scaffold's taxonomy.
The taxonomy will be scoped into the following domains, "Core", "Helpers", "Page", "Type", "Picto", "Ux" and a "Plugins" location. Each will house all the Broader Terms, those resources that are logically grouped under that category. Each top level category will house any general resources, and all appropriate related term nodes.
Gooi attempts to manage resources by implementing a controlled vocabulary and will associate all "related term" resources via placement in the file-system and the resource's file name to establish its placement in the taxonomy.
The first two hierarchical levels of the Gooi app scaffold are represented below, with sample broader terms added as examples, see Figure 2 in the appendix.
Gooi attempts to solve the following problems.
- Presentation Resource Management and Categorization
- Images
- Sprites
- web fonts
- style sheets
- Consolidation of resources,
Figure 1.
Note: Taxon > domains > broader terms > related terms
Figure 2.
- Gooi
- GooiCore
- GooiCoreLoader
- GooiCoreModules
- GooiCorePackages
- GooiCorePrimatives
- GooiCoreSockets
- GooiHelpers
- GooiCoreArrays
- GooiCoreUtilities
- GooiPage
- GooiPageHeader
- GooiPageHeaderMenu
- GooiPageContent
- GooiType
- GooiPicto
- GooiUx
- GooiUxButton
- GooiUxFaceted
- GooiUxForm
- GooiUxGrid
- Plugins
- JSon2 (1.3kb)
- Microajax (.4kb)
- Qwery (2.6kb)
- yepnope (1.8kb)
Auxiliary project resources, like the Topography document and it's associated resources and the solutions readme file will be prefixed with an underscore and added to the Gooi folder root.
No comments:
Post a Comment