Eleventy boilerplate for Visual Framework 1.3
This allows you to use the 11ty static site generator
with direct access to Visual Framework 1.3 and 2.0 components.
This is possible as the VF 2.0 is no-conflict with VF 1.3.
This is in active development as of 2019.08.16
- We recommend using this over EBI-Boilerplate-Jekyll
as node+Eleventy facilitates more flexible solutions and frees a Ruby dependency.
1. Creating a new project powered by ebi-eleventy-boilerplate
There are two methods you can use:
Use the interactive yarn template [RECOMMENDED] Not yet implemented
- If you don't have npm, install it
- The
create-vf-eleventy
project allows you to interactively create a new site by typing
yarn create @visual-framework/vf-eleventy your-new-site-name ebi-eleventy-boilerplate
- Follow the prompts
- The GitHub template
2. Configuring your new site
- In
package.json
update vfConfig
- In
elevnety.js
update pathPrefix
- Update
./src/site/_data/siteConfig.js
Otherwise configure gulp and eleventy as you would for any other project.
3. Developing your new site
- You'll need to install npm
- If you don't have
yarn
, install it
- Install all the things
- Generate the site in
/build
gulp dev
renders and servesgulp build
build static assets
- Edit all the things:
- pages:
./src/site/
- templates:
.src/site/_includes
- site information:
./src/site/_data
- local css:
./src/scss
4. Adding Visual Framework components
To add a component you can use Yarn or install it manually.
In either case you'll need to re-run gulp dev
to ensure the component is fully loaded.
By package
- installation:
yarn add @visual-framework/vf-logo
- updating components:
yarn upgrade-interactive --latest
- alias:
yarn run update-components
Manual installation for customisation
- Download a pattern
- Copy it to
./src/components/vf-component-name
Create your own local component
You can add a custom VF-compatible component to ./src/components
and use it in
your site.
You'll find a vf-sample
component already placed in ./src/components
5. Deploying
- Why
yarn
and not npm
?
For the particular structure of the Visual Framework components, Yarn is considerably
faster at installing and does so more efficiently (about half the total file size). You'll
also be able to use yarn upgrade-interactive --latest
, which makes it easier to update
VF components.