foundation-apps

Foundation for Apps

This is Foundation for Apps, an Angular-powered framework for building powerful responsive web apps, from your friends at ZURB.

Requirements

You'll need the following software installed to get started.

• Node.js: Use the installer provided on the NodeJS website.
• Git: Use the installer for your OS.
  • Windows users can also try Git for Windows.
• Ruby: Use the installer for your OS. For Windows users, JRuby is a popular alternative.
  • With Ruby installed, run gem install bundler sass.
• Gulp and Bower: Run [sudo] npm install -g gulp bower

Get Started

The Sass and JavaScript components are available on Bower.

bower install foundation-apps --save

You can also use our command-line interface to quickly setup a basic Foundation for Apps project. It includes a pre-built Gulpfile that compiles an Angular-powered web app for you.

Install it with this command:

npm install -g foundation-cli bower gulp

Now you can make a new project:

foundation-apps new myApp
cd myApp

While working on your project, run:

npm start

This will assemble the templates, static assets, Sass, and JavaScript. You can view the test server at this URL:

http://localhost:8080

Building this Repo

If you want to work with the source code directly or compile our documentation, follow these steps:

git clone https://github.com/zurb/foundation-apps.git
cd foundation-apps
npm install

While you're working on the code, run:

npm start

The documentation can be viewed at the same URL as above.

Directory Structure

• build: This is where our documentation is assembled. Don't edit these files directly, as they're overwritten every time you make a change!
• docs: The Foundation for Apps documentation.
• scss: The Sass components.
• js: The Angular modules and directives, and other external libraries.
• iconic: A set of 24 icons from the folks at Iconic.
• tests: Unit tests for the Angular modules.

Versioning

Foundation for Apps follows semver, so we won't introduce breaking changes in minor or patch versions. The master branch will always have the newest changes, so it's not necessarily production ready. The stable branch will always have the most recent stable version of the framework.

Contributing

We love feedback! Help us find bugs and suggest improvements or new features. Follow us on Twitter at @ZURBFoundation to keep up-to-date with what's new, or to just shoot the breeze.

If you find a problem or have an idea, open a new issue on GitHub. When filing a bug report, make sure you specify the browser and operating system you're on, and toss us a screenshot or show us how we can recreate the issue.

Changelog

Version 1.0.3

February 16, 2015

General

• The Bower and npm packages now include a dist folder, which contains compiled CSS and JavaScript files, in minified and unminified flavors.
• The Sass is now fully compatible with libsass. It's been tested in node-sass 1.2.3. Eventually our documentation and template stack will be compiled with node-sass instead of Ruby Sass, but we'll continue to test both.

Breaking Changes

These Sass variables changed. If you're updating an existing project, you'll need to update your _settings.scss file manually.

• Added: $badge-diameter: 1.5rem
• Renamed: $badge-font-color is now $badge-color
• Removed: $badge-padding
• Removed: $badge-radius

The old variables are still in the codebase but aren't being used. They'll be permanently removed in version 1.1.

Template Changes

The Gulpfile used in the template stack now uses the gulp-load-plugins library to streamline use of plugins. If you have an existing project, you don't need to change anything to upgrade.

New Features

• Stacking notifications. (#388) Dynamically-called notifications will now stack when you call more than one.
• Responsive Iconic icons. (#408) Iconic icons are now fluid by default, which means they will adjust their geometry based on the width of the parent container.
• Staggered animations. (#394) When using our motion classes in conjunction with the ng-repeat, you can now add a stagger class to make items animate in sequence. Add the class .stagger, .short-stagger, or .long-stagger to an element to enable the stagger effect.
• #376: Added .info and .dark coloring classes to buttons.
• #436: The items in a menu bar can be aligned with .align-right, .align-center, .align-justify, or .align-spaced. These classes mimic the behavior of the grid alignment classes.
• Notifications can now be assigned a timeout by adding the autoclose attribute. The value of autoclose is the number of milliseconds to wait before closing.
• The speed of all animations has been increased slightly. The default felt just a little too slow.

Bug Fixes

CSS:

• #194: Fixed modals not scrolling when they overflow their parent.
• #412: <button> and <input> elements can be used as prefix/postfix elements in forms now, in addition to <a>.
• #417: Added padding to <select> elements to prevent the text from overlapping with the arrow.
• #435: Fixed a misnamed parameter in the grid-block() mixin.
• #438: Fixed display issues with <select> elements in Firefox.
• #453: Fixed block list checkboxes being misaligned.
• Fixed the .dialog class and sizing classes of modals not working.
• The CSS for badges was refactored so they're sized with width and height instead of padding.
• The pointer cursor is now used when hovering over any anchor (<a>) or any element with the ui-sref attribute.

JavaScript:

• #363: Fixed zf-close not working when placed outside of a component.
• #420: Fixed panel/block animations triggering even though the element is in block mode.
• #427: Fixed the pin-at directive not passing its value to Tether.
• #448: Fixed invalid $scope.params property on the DefaultController controller.
• If a component is closed or opened while a transition is in progress, the transition will reverse.