Webcomponents is a Grav plugin that can be used to get webcomponents integrated into your Grav site with ease. Simply drop your webcomponents into user/webcomponents (unpacked from bower_components if using a framework like Polymer).
The simplest way to install this plugin is via the Grav Package Manager (GPM). From the root of your Grav install type:
bin/gpm install webcomponents
If for some reason you can't use GPM you can manually install this plugin. Download the zip version of this repository and unzip it under
/your/site/grav/user/plugins. Then, rename the folder to
You should now have all the plugin files under:
This should give you the dependencies you need to get going.
- Enable the Web components plugin and any dependencies it requires.
- The default is to serve JS assets up from a CDN. Should you need to change this keep reading into building your own assets.
You may build Web components from source if needed. We default to use CDNs which will effectively point to this directory or some mutation of it -- https://github.com/elmsln/HAXcms/tree/master/build
If you want to build everything from source, your welcome to use yarn / npm to do so though our build routine effectively will end in the same net result. If you want to do custom build routines such as rollup or webpack and not use our prebuilt copies / split build approaches, then your welcome to check the box related to not loading front end assets in the settings page in order to tailor the build to your specific needs.
You need polymer cli (not polymer but the CLI library) in order to interface with web components in your site. Get polymer cli installed prior to usage of this (and (yarn)[https://yarnpkg.com/lang/en/docs/install/#mac-stable] / an npm client of some kind)
$ yarn global add polymer-cli
Perform this on your computer locally, this doesn't have to be installed on your server.
- Find https://github.com/elmsln/unbundled-webcomponents and run the tooling to create your build (
yarn run build)
- create a
- copy the files from https://github.com/elmsln/unbundled-webcomponents into
We don't think so. While it may seem counter intuitive, the theme layer should be effectively implementing what the site is saying is available. If you think of standard HTML tags are being part of this (p, div, a, etc) then it makes a bit more sense. You don't want functional HTML components to ONLY be supplied if your theme is there, you want your theme to implement and leverage the components.
We built our own tooling to take the guess work out of creating, publishing and testing web components. We highly recommend you use this tooling though it's not required: