christhekeele
commented
9 years ago It could be implemented by:
- Adding a new page,
sandbox.html - Creating a sidebar of links to jump to each feature in a
_menu.htmlpartial - Creating a partial for each element of the kitchen sink
- Adding the new partials to the sandbox, making it easy to comment out Foundation components you've no intention of using
- Linking to the sandbox from the panel on the landing page that talks about the kitchen sink, all the components, and the docs
What if this project came with a copy of the kitchen sink page?
It'd make test driving customized Foundation installs trivial. Clone this project, play around the SCSS until your overrides are just right, then start developing the site or even just plug the customizations into whatever framework you intend on using.
I ask because when I start new projects, I normally develop the backend while someone else works on the branding, typography, and general feel of the site. This way, we could work asynchronously and meet in the middle when I get enough content on page to merit larger-scale design decisions.
Since he's familiar with Foundation's SCSS and I'm familiar with its HTML and JS, I could just build with vanilla Foundation installed with the confidence that I can just plug and play his styles when they're finished.
If he had a sandbox with everything ready to go, we'd be a devastatingly effective duo.