EMBL Content meta properties
These meta tags describe the role of page within the EMBL information architecture.
HTML
<meta name="embl:who" content="all">
<meta name="embl:where" content="EMBL">
<meta name="embl:what" content="services, websites">
<meta name="embl:active" content="what">
<meta name="embl:utility" content="-8">
<meta name="embl:reach" content="-5">
<meta name="embl:maintainer" content="Strategy and Communications">
<meta name="embl:last-review" content="NaN">
<meta name="embl:review-cycle" content="">
<meta name="embl:expiry" content="2019-06-20">
Usage
The meta properties:
- Content descriptors
embl:who
the people, groups and teams involved
embl:what
the activities covered
embl:where
at which EMBL sites the content applies
embl:active
which of the above three facets is most important for this content
- Content role:
embl:utility
if content is task and work based or if is meant to inspire
embl:reach
if content is externally (public) or internally focused (those that work at EMBL)
- Page infromation:
embl:maintainer
the contact person or group responsible for the page
embl:last-review
the last time the page was reviewed or updated
embl:review-cycle
how long in days before the page should be checked
embl:expiry
if there is a fixed point in time when the page is no longer relevant
These tags should be placed in your <head>
.
Why do they matter?
- Ensures future quality of content
- Will be programatically queried by other patterns to offer contextually-appropriate content and navigation
- Can affect the look and feel of content
Installation info
This component is distributed with npm. After installing npm, you can install the embl-content-meta-properties
with this command.
$ yarn add --dev @visual-framework/embl-content-meta-properties
Sass/CSS
The source files included are written in Sass(scss
). You can point your Sass include-path
at your node_modules
directory and import it like this.
@import "@visual-framework/embl-grid/index.scss";
Make sure you import Sass requirements along with the modules. You can use a project boilerplate or the vf-sass-starter
Changelog
Changelog
1.0.23
- small change to cards on homepage
1.0.18
1.0.17
1.0.16
1.0.13
- dependency bump
- adds roamap and consultation docs
1.0.12
- design token documenation now lives in the component libary
1.0.7
1.0.6
- begin to make more pattern/boilerplate guidance
- minor templating updates
1.0.5
1.0.4
- uses vf-favicon
- adds meta attributes
1.0.3
- run
vf-component-assets:everything
on local dev
- remove reference to removed
/css/app.css
1.0.2
- Add 404
- Fix component CSS generation
1.0.1
- Also generate per-component CSS with
vf-css:generate-component-css
1.0.0
- Initial release to be used with vf-core 2.2.0
Assets
File system location: components/embl-content-meta-properties