Hi @dennybritz

Current npm 0.2.4 is broken. This PR fix that.

I changed Object.assign to jQuery.extend. Now is more IE9 and mobile compliant without babel-polyfill dependencies.

Hi @dennybritz this is for make Navbar more customizable via className

This way anyone can, for example, create navbar fixed at top navbar-fixed-top.

sample-page.jsx

export default (props) => (
  <Page>
    <Navbar brand={brand} className="navbar-fixed-top">
...

This PR don´t broke current neal-sample

Currently available versions of Internet Explorer used in Windows 7, Window 8.1, Windows Phone 8.1 and Windows 10 do not support ES6 (e.g. Object.assign) natively, and there are no polyfills included with neal-react for ES6 features it uses.

Due to this issue, a neal-react-based landing page (i.e. nealjs.com) cannot be opened on a Windows phone at all, as there are no third-party browsers for this platform.

Since I don't like to take and use something without giving something back in return, I've taken the liberty to upgrade your entire package. Stating from Babel 6 and working my way to the remainder modules, everything has been updated and subsequently tested in conjunction with your other package, neal-sample which I'll be pull submitting shortly as well.

One thing I didn't touch was linting since everybody has their own preference, however I would recommend looking into this aspect of your build.

$ symbol has a wide support of web fonts, but some currency, for example Russian ruble \u20BD has not.

It would be nice to be able to select the currency symbol in pricing-table component.

Not very familiar with React, tried to do, but unsuccessfully:

<div className="neal-pricing-plan-price-amount"><i className="fa fa-rub"></i> {this.props.price}</div

Under the "batteries included"... "repetetive" should be "repetitive"...sorry could not figure out a better place to report this

Hi! I used neal-react a few times for creating landing pages for events and I noticed that a timer stating how many days / hours / minutes / seconds are left until the event, is a nice feature and brings a little bit action to the page. I think that adding the countdown component can bring value to the repo. Here an example of the countdown element: What do you think?

It's not strictly required, but it's useful metadata, and part of the recommended license template text (see http://choosealicense.com/licenses/isc/ and https://opensource.org/licenses/isc-license)

Going through the code then when back to the readme I wanted to jump back to the component code. This PR add ability to do that.

I also noticed that figure component wasn't listed so I added.

Great job btw.

I tried using this library with an app that uses React 16 and I get errors that look to be due to use of deprecated features. Are there any plans to bring this library up-to-date with recent React changes? thanks

Fixes #36 and #32.

Using prop-types to allow for React 16 support.

There were also multiple places where we were passing through props to elements that we didn't want to (some are bad and React complains). Instead of passing {...this.props} in these cases, I destructured the props and only passed through the extras.

I tried using this library with an app that uses React 16 and I get errors that look to be due to use of deprecated features. Are there any plans to bring this library up-to-date with recent React changes? thanks

This repo points to nealjs, which has either been hijacked or is an intentional malware. The site asks you to click a "security button", which then opens a dialog box for installing a chrome extension that can access & alter all websites/pages.

Use of {... this.props} is causing this error in the browser console:

Unknown prop `backgroundImage` on <div> tag

From https://facebook.github.io/react/warnings/unknown-prop.html

Are you using {...this.props} or cloneElement(element, this.props)? Your component is transferring its own props directly to a child element (eg. https://facebook.github.io/react/docs/transferring-props.html). When transferring props to a child component, you should ensure that you are not accidentally forwarding props that were intended to be interpreted by the parent component.