wagtail/client
Tim Heap 75e58efab8 Move version from wagtail.wagtailcore to wagtail
This is where developers expect it to be, similar to Django and other
projects. The version info still exists at the old `wagtail.wagtailcore`
location, for backwards compatibility.

Fixes #2557
2016-08-18 12:05:33 +01:00
..
scss Tooling for modern front-end components: React JS, ES6, and BEM CSS 2016-02-25 13:32:48 +00:00
src Tooling for modern front-end components: React JS, ES6, and BEM CSS 2016-02-25 13:32:48 +00:00
template Tooling for modern front-end components: React JS, ES6, and BEM CSS 2016-02-25 13:32:48 +00:00
tests/components Tooling for modern front-end components: React JS, ES6, and BEM CSS 2016-02-25 13:32:48 +00:00
.npmignore Tooling for modern front-end components: React JS, ES6, and BEM CSS 2016-02-25 13:32:48 +00:00
README.md Move version from wagtail.wagtailcore to wagtail 2016-08-18 12:05:33 +01:00
package.json Tooling for modern front-end components: React JS, ES6, and BEM CSS 2016-02-25 13:32:48 +00:00

README.md

Wagtail client-side components

This library aims to give developers the ability to subclass and configure Wagtail's UI components.

Usage

npm install wagtail
import { Explorer } from 'wagtail';

...

<Explorer onChoosePage={(page)=> { console.log(`You picked ${page}`); }} />

Available components

TODO

  • Explorer
  • Modal
  • DatePicker
  • LinkChooser
  • DropDown

Building in development

Run webpack from the Wagtail project root.

webpack

How to release

The front-end is bundled at the same time as the Wagtail project, via setuptools.