mirror of
https://github.com/wagtail/wagtail.git
synced 2024-12-01 11:41:20 +01:00
f584dd57bb
The rationale for these was to keep the control flow in one direction, so that the child blocks don't know about the wider sequence they belong to. But that's already undermined by the fact that they have to keep track of their own index number, and it just makes things needlessly unwieldy, particularly when we go on to make action buttons pluggable (and emphatically want to avoid having a mass of abstraction between the button and the action it performs). |
||
---|---|---|
.. | ||
.storybook | ||
scss | ||
src | ||
tests | ||
package-lock.json | ||
README.md | ||
webpack.config.js |
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 />
Development
# From the project root, start the webpack + styles compilation.
npm run start
You will also need:
- React DevTools – React developer tools integrated into Chrome.
- Redux DevTools – Redux developer tools integrated into Chrome.
Releases
The front-end is bundled at the same time as the Wagtail project. This package also aims to be available separately on npm as wagtail
.