forked from ucla-oarc-web/WebBlocks
-
Notifications
You must be signed in to change notification settings - Fork 0
Meeting 2012 08 06
ebollens edited this page Aug 6, 2012
·
3 revisions
- Location: Math Science Building 5907 & Remote
- Date/Time: Monday August 6 from 1:00 to 2:00 PM
- Conference Line: 888-921-8686 #3102061670
TODO
Completed markup prototypes:
- Entity/Nav/Main
- Entity/Nav/Bar
- Entity/Header/Masthead
- Entity/Nav/List
- Entity/Figure/Hero
- Gallery
Recent additions:
- Command-line argument specification of a config file location
- Add support for SCSS outside of WebBlocks via configuration file
- Provide default configuration values, but allow override
- Now possible to build your assets into your build directory using an untouched Git submodule:
- https://github.com/ucla/WebBlocks/wiki/Integration
- UCLA's OIT ECTA group has incorporated WebBlocks as described in "Using WebBlocks as a Submodule"
- Fixed several dependency-chain issues
- Updated build documentation
- Package custom JS, images and HTML files into build
- Look at other projects to come up with a portability strategy
- Create Vagrant-based build environment for testing
What should we do about a color strategy?
- Starting thoughts: https://github.com/ucla/WebBlocks/issues/33 for reference
- No support for nested selectors in `@extend`
- Inheriting from something like `.btn` is easy because of its modular implementation
- Other tools like `.nav` and `.navbar` are far more complex and non-viable
- Implementation of `nav.bar` uses Bootstrap variables but not many `@extend` calls
- Definitions aren't laid out ideally
- Often not a clear candidate for `@extend` or `@include`
What entities that are prototyped do people want to start developing?