Workbench for UI-driven development: A tool for developers and designers to build and document web sites and apps.
Useful if you want to …
- Create a living pattern library
- Document your design system
- Prototype with your apps components and templates
- Use code as a single source of truth
🚀 What it enables
- Establish a UI-driven workflow and structure your web UI into modular components.
- Give your team and stakeholders a central spot to develop and discuss the UI.
- Replace deliverables with usable, testable and production ready output/code.
- Make documentation fun and easy by providing structure and nice looking pages.
To explore the features yourself you can quickly initialize a project with some demo content:
mkdir uiengine-demo && cd uiengine-demo && npm init -y npm install @uiengine/core @uiengine/adapter-html --save-dev npx uiengine init --demo npx uiengine build --serve --watch
🖥 Examples and Screenshots
To get an idea of what a real-world project looks like, see the React sample project:
- Tasty BBQ Design System: The UIengine output for this sample project
- Tasty BBQ Website: The corresponding website, built with React and Next.js.
- Tasty BBQ Source Code.
See the documentation site, which is also generated with the UIengine.
🔩 Technical TL;DR
⚒ How does it work?
At its core, the UIengine is a static site generator. It can be used in standalone mode or integrated into your build process.
It consumes the files and structure of your project and generates the documentation based on this. In development mode the output is regenerated on file change and synced to the browser. This provides you with a development environment for creating the components, prototyping and writing the docs.
💯 Main features
- Prototyping environment: Build your UI without the need for an existing backend/API. Render your templates and components with mock data. Build various variants for pages by providing different data to your views.
- Best practice approach: The tool guides you towards best practices like the component folder pattern, the modlet workflow and by proposing a separation of data and template/component.
- In sync with the end product: The docs are generated from the code that is used in your application. Hence you get a living pattern library – not a separate thing that needs to be looked after regularly.
- Flexible integrations: Templating engines can be configured so you can fit it to your needs. Same goes for the markdown parsing/rendering which is configurable too.
- Covers green- and brownfield projects: Whether you start out with a pattern library or want to transition your process and refactor your existing UI into modular components, the UIengine has you covered.
For the evaluation process you might also want to have a look at the alternatives.
UIengine requires at least Node.js 14.15 (tracking the latest active Node.js LTS version). This guarantees a reasonable level of backwards compatibility.
OK, the UIengine looks really cool but it's not quite what you are looking for? Or you want to first compare a few solutions to see which one is the right fit? Here are some other projects that you might want to evaluate:
You like this project and are interested in participating? See the development docs for an introduction and workflows when hacking on the UIengine.
Thanks goes to these wonderful people:
This project follows the all-contributors specification. Contributions of any kind welcome!
👨🏻💻 Brought to you by the nice people behind UIengineering. 👨🏻💻