forked from ucla-oarc-web/WebBlocks
-
Notifications
You must be signed in to change notification settings - Fork 0
Meeting 2012 07 25
ebollens edited this page Jul 25, 2012
·
6 revisions
- Location: Math Science Building 5907
- Date/Time: Wednesday July 25 from 1:00 to 2:00 PM
- Conference Line: 888-921-8686 #3102061670
- Eric B
- Eric C
- Chris
- Alice
- Mel
- Celia
- Logan
- Build script [Eric]
- Reworked internals of the script to make it more sustainable
- A number of new build routines have been exposed
- Gemfile added so that all required Ruby packages can be installed with Bundler
- package.json added so that all required Node.js packages can be installed with NPM
- Compile now happens through Compass rather than SASS
- Testing confirmed for OS X and Win 7 - feedback still needed for RHEL and Win 8
- Chris is going to work on a Vagrant build to do universal portability testing
- SASS programmatic layout [Eric]
- SASS code is under src/sass
- WebBlocks code in subfolders (lib, adapter and config) under src/sass
- WebBlocks can be imported with the simple line @import "lib/core" in a file under src/sass (such as site.scss)
- Configure packages in WebBlocks via import lines in src/sass/config/_package.scss
- Configure SASS variables before main SASS code is loaded in _variables.scss
- Each package (folder) in src/sass/lib has a corresponding SCSS file that loads everything under it
- Such as src/sass/lib/foo/ would have a src/sass/lib/_foo.scss file that loads all its contents
- Allows you to load particular packages via src/sass/config/_package.scss instead of everything
- As example, the default in src/sass/config/_package.scss is @import "lib/entity" which loads all entities
- Adapter design pattern [Eric]
- Design challenge is to decouple us from any particular framework:
- Future-proofing as some frameworks may go unmaintained while other frameworks grow
- Allows flexibility at the level of an institution to use a framework that works for them
- Idea is to allow you to define all the definitions necessary to bridge a framework with the entities in WebBlocks
- Configure adapter to load via src/sass/config/_adapter.scss
- Preliminary prototype presented in https://github.com/ucla/WebBlocks/issues/16
- Eric to create "templates" for a few entity markup prototypes to help with this process
- Design challenge is to decouple us from any particular framework:
- Checklist [Logan]
- protype.html
- -ex-example-name1.html
- -ex-example-name2.html
- -ex-img-example-image-name1.html
- -ex-img-example-image-name2.html
- README.md
- Definition
- Usages
- Responsive Considerations
- Entity/Header/Masthead [Alice]
- Entity/Nav/Main [Joseph]
- Entity/Nav/Bar [Eric]
- Extracted from Entity/Header/Masthead since it is a separate unit
- Carry Bootstrap's class-driven semantics into HTML 5 (and escape coupling to Bootstrap itself)
- Gallery [Alice]