A frontend prototyper tool for rapid prototyping of websites
This is the npm that powers these Fepper prototypers:
- Fepper Main - main distribution.
- Fepper Base - no unnecessary assets, styles, Pattern Lab demo, or fp-stylus extension.
- Fepper for Drupal - templates configured for Drupal, along with a Drupal theme built to accommodate those templates.
- Fepper for Wordpress - templates configured for WordPress, along with a WordPress theme built to accommodate those templates.
Please consult any of the above links for documentation on getting started and on power-usage of Fepper.
Minimum supported Node.js version 12.0.0
To just run a Node.js implementation of Pattern Lab, instantiate a
object as follows:
const config = ;const cwd = process;const Patternlab = ;const patternlab = config cwd;
Patternlab constructor recognizes a second argument (current working
directory) for instantiating a
patternlab object. This allows it to be
instantiated from any directory within any task runner or custom application.
Fepper exposes these methods on the
- build: function (options)
- compile: function (options)
- resetConfig: function (config)
options argument is optional. If submitted, it must be an object whose
properties are intended to override one or more properties in the
object consumed by the
Keep in mind that configs overridden by an
options argument will persist
through all future operations on that
Patternlab instance. In order to revert
the configs back to the original configs, call
resetConfig with the original
resetConfig will reset any number of properties submitted but will
not delete any preexisting properties.
Fepper is 100% compatible with Pattern Lab PHP Mustache code. It aims to maintain parity with the PHP distribution with respect to performance and core features.
Using this npm decoupled from a full Fepper project requires compiling the UI by running this line of Node.js:
The word "compile" takes on a special meaning in Fepper, referring to assembling "components" into a whole. "Build" refers to outputting patterns to be displayed by the UI.
All aspects of the UI are available for customization. For example, the toolbar
can accept additions, modifications, and deletions per the needs of end-users.
The UI markup is compiled by recursive, functional React calls. The recursion
tree is reflected by the directory structure containing the modules which
compose the UI. To override any given module, copy the directory structure
leading to the module from
source/_ui/index/html, respective to your implementation. Modifications to
modules in that directory will override the corresponding modules in core.
Additions (so long as they are correctly nested) will also be recognized.
A working example of UI customization can be found at
The Fepper for Drupal project overrides its HTML title to read "Fepper D8"
instead of "Fepper". In order to do so, it has the
nested in directories that correspond to the tags that nest the
head.component.js and its nesting directories must be named
similarly to their corresponding elements.
.component.js indicates that the
file is a module to be rendered by React.
It must export properties that
The numeric prefix to
00-head orders it to precede
01-body, even though
"body" precedes "head" alphabetically.
In this example, by allowing customizations in the
00-head directory separate
from the core components, core updates will be respected for all components
except for the HTML head.
this way as well. While a head element is unlikely to have associated scripts or
styles, the UI's main element does have its scripts and styles componentized as
index/html/01-body/40-main. A big advantage
for this type of componentization comes when elements are renamed or deleted.
When you rename or delete an element, are you absolutely sure you'll rename
or delete accordingly in some far-flung, monolithic script or style file?
Alas, no one should be forced to componentize this way. Generic modifications
to UI scripts can be added to
Similarly, generic modifications to UI CSS can be added to
source/_styles/pattern-scaffolding.css. (The file is named this way to adhere
the Pattern Lab documentation on pattern states. It should not be relied on
for pattern scaffolding.)
View All markup can also be overridden by copying the
.mustache files in
and pasting them to
source/_ui/viewall (nested correctly). Modifications will
then be recognized and displayed in the UI. (No additions are allowed.) Custom
View All styles can be added to
You will need to compile the UI in order for the browser to pick up custom changes to the UI. Within a full Fepper project, this can be accomplished with the following command:
New UI customizations will not be picked up simply by restarting Fepper.
While it is recommended that you use Fepper with the
fp command, you can alternatively instantiate a barebones Fepper
const cwd = process;const Fepper = ;const fepper = cwd;
cwd must contain
pref.yml, and the
There is currently no public API for object-oriented Fepper. To express demand for one, please open an issue.