Unverified Commit 5d67c9f8 authored by Ken Hawkins's avatar Ken Hawkins Committed by GitHub
Browse files

CHORE - alpha.8, merge to master (#499)

* vf-form dependencies

* chore: opimise-sas-import-paths

Sets up a cleaner hirearchy of sass path imports.

Also does an npm update.

* fix: vf-global-header-dependencies

Was using an old version of vf-logo

* chore: load-latest-patterns-to-npm

Resolve a couple of broken package dependencies.

* Fix: docs should soft fail when vf-design-tokens aren't present

* Typos

* Chore: don't send backstop files to npm

Just a cleanup thing I suppose.

* Always ignore any vf-core-components/vf-core components

There should typically never be any components here, but:

1. A developer might drop them in the wrong spot
2. if we're testing the npm directly from github, we need to ignore these

* Typo

* removes BackStop.js and adds Percy

* adds .percy.yml config file

* adds Percy.io badge

* updates percy yml file

* chore: cleanup autocomment

Mostly does two things:

- Reduces the amount of spam we're getting when a PR is made and review requested (and I think this phrasing might be more helfpul to external devs)
- Tries to fix [ ] checkbox formatting with 2 spaces at end of each line

* updates .percy.yml

* updates travis.yml for percy to be fired

* fixes incorrect variable spelling

* updates breadcrumbs so the work without an embl-grid

* adds spacing for when on desktop, hides fake dark grey bar

* various spacing issues fixed to make it look nicer

* stylelint fixes

* tidies up breadcrumbs specifity

* fixes breadcrumb on mobile

* fixes breadcrumb on mobile

* fixes main navigation inside header

* bug: conditional-edit-order-of-operation

Resolves an issue where `?embl-conditional-edit` was being parsed before content had loaded.

* enhancement: dont-link-breadcrumbs-without-url

The current desire is that when we don't have a working url, to not link the term.

* Enhancement: vf-blockquote

Adds `blockquout` to `vf-conent` and better insulates against external styling with a `border: 0`

Relates to https://gitlab.ebi.ac.uk/emblorg/backlog/issues/215

* Usage updates for vf-breadcrumb to remove wrapping grid

* the one that fixes quite a lot of small issues with vf-core and vf-wp (#441)

* fixes incorrect variable spelling

* updates breadcrumbs so the work without an embl-grid

* adds spacing for when on desktop, hides fake dark grey bar

* various spacing issues fixed to make it look nicer

* stylelint fixes

* tidies up breadcrumbs specifity

* fixes breadcrumb on mobile

* fixes breadcrumb on mobile

* fixes main navigation inside header

* the one where we include the first pass at a card component (#440)

* npm shrinkwrap idk

* adds initial vf-card pattern

* some spacing fixes for hover and mobile

* makes the image not go crazy on small viewports

* Enhancement: update heading--l text size

Resolves issues that occur as `heading--l` and `heading--l-alit` were both 24px

For more background see: https://gitlab.ebi.ac.uk/emblorg/backlog/issues/215#note_45386

We could also resolve some of these issues by manually setting the `.vf-content h2` size, but that would be a bit of a hack and not get updates from vf-design-tokens.

This will have some knockon effects to other patterns, sometimes it may be a "change for the better" other times we may need to update a pattern to use `--l-alt`

The Sketch paragraph styles may also need to be updated.

* enhancement: use-heading--l-alt-for-some-patterns

Follows up on #443 by subing out `heading--l` for `heading--l-alt` in:

- vf-card
- vf-section-header
- vf-summary
- vf-video-teaser

Basically, where a bump from 30px to 24px was undesirable.

We may have a larger refactor of the naming of some of these tokens coming, but for now this "makes things look right", i think.

* BUG: hover issue with buttons or links that look like buttons

Procrastinating writing some documentation so had a go at sorting #436

* Chore: vf-sass-utilities should be on npm (#449)

Addresses #399

* Docs: How do we version patterns on npm? #119

* Docs: List core audiences/user types #127

* Typos

* Typos

* Bug: Autocomment formatting

Continues effort to (attempt to) clean up formatting.

* bug: spacing-token-naming

The spacing token names missed an update, that is: `vf-spacing-r` should be `vf-spacing--r`

Also adds an issue where nested `.vf-content ul li > ul` didn't have a needed margin at the top.

* Enhancement: gulp css building, linting

Addresses #412 and also address the "spirit" of that ticket, by:

- Making the css linting come after the css recompilation
- Adds a soft-fail css linting task that won't explode the local deve experience
- Fixes `vf-css` to use a better callback approach so that:
    1. You get an accurate idea of the css build time
    2. A real signal that the vf-css pipe stream has completed
    3. No longer get a flash of fractal befor the css build has finished

And it should be a bit faster now that fractal won't try to run while the Sass is still building.

* Bug: fix static build path

This mainly fixes how vf-card was showing without the image when deployed. It relates to #364 on how we need to document this, propbably in the pattern template too.

It also sneaks in a fix where the utility mixins were need for the hover effect for the button.

* Drop vf-sass-lint from watch command

* docs: Using frctl `path` with njk templates (#458)

Addresses #364

* updates ordering of typography

* CHORE: Swap npm for yarn

Addresses #455

* Bug: component variant name, demo (#461)

A few minor fixes I stumbled on while working on #460: a name for a vf-text variant and the vf-headings demo

* the one where we use variants for the vf-card component (#462)

* makes use of nunjucks to create variants

* makes use of variables and maps and normalises some sizing

* small readme update

* Elsewhere we've used hyphens, changing for consistency

* Remove _preview--grids

It's the same as --containers

* Remove _preview--containers

* bug: vf-conent-hub-html grid-escape

The below tweak introduced some layout issues as non-layout affecting content out of the content hub (think: blocks) was being escaped from the grid.

```
.embl-content-hub-html {
  grid-column: 1 / -1;
}
```

This fixes that by only targeting elements that are direct children of `-grid`.

It also add `.embl-content-hub-html` so we can begin to update classes in the contentHub.

* updates button, body, and text design tokens

* removes unused monospace tokens

* swaps vf-color--grey--light and vf-color--grey--lightest

* Chore: set percy to run only on develop

This limits the percy command to only run on commits to develop and compares against master.

We might also want to disable the github integration to stop comparissons on PRs, which has chewed through our alotment of screenshots.

This also set it only do mobile/desktop for a 33% savings :D

But it doesn't really matter until August as we've already gone through our quota!

* Forgot to commit

* Docs: move design token demonstration (#468)

As I work through cleaning up docs and making "things more approachable", it became clear that the design tokens can (of course) change in both how they're used and how much technical detail should be shown.

With that in mind I've moved the existing `/docs/styles/` to be paired directly with `vf-design-tokens`

I think this:

1. Makes it clear that these settings come from `vf-design-tokens`
2. Are where developers might expect the most technical values
3. We can link to from `/docs`
4. Makes it possible to put something more high level in `docs/styles`
5 It also stops the risk of "what happens when there's `docs/styles` but `vf-design-tokens` wasn't installed?

* updats

* adds vertical spacing for vf-lede, normalises spacing for vf-intor (#472)

* adds vertical spacing for vf-lede, normalises spacing for vf-intor

* moves vf-lede margin to vf-intro parent

* RELAESES - alpha.7 (#470)

* Update package.json

* Update npm versions

* Guidance on how (and when) to start using vf-core #391, #339 (#474)

In this commit we make it clear(er) that the role of the Fractal part of vf-core is to be the component library.

It also works to cleanup the docs in general leverage the vf-welcome site, which itself is a work in progress.

In all, this narrows the role of docs within vf-core to be directly about the component library and lets vf-welcome be an umbrella site to support both vf-core and vf-eleventy, and likely other sites as well.

* Drop glob for fastglob

Before: `Finished 'vf-css' after 1.68 s`
After: `Finished 'vf-css' after 1.41 s`

Background: see #481

Note: fastglob isn't suitable for use everywhere, particuarly if we want to pass globed assets into a folder.

* BUG: Remove extra spacing from vf-badge

Was breaking formatting on render in whitespace-aware environments.

* BUG: Fix for code examples that break layout

Currently .vf-content pre and .vf-code-example__pre have the default behaviour of never breaking and will explode the layout.

This stops that.

* ENHANCEMENT: Code highlighting

I'm working a lot with code snippets at the moment and the lack of formatting has finally gotten to me. This is basically GitHub's approach with VF sizings.

Probably more to do here, but a placeholder until Mark has time to draft a design.

* Fix pre blocks, use spacing map

* linting

* chore: update-footer

* Revert "chore: update-footer"

This reverts commit 8b52e692.

* Make footer generic

* Chore: twaks for vf-component-rollup docs, integration

A couple of minor edits to the rollup to make its use a bit clearer. Also add a `.yml` and `.njk` whose absence would make fractal brittle in some occasions.

* Language tweaks

* Give info about cloning the vf-component-rollup

* removes normalize dependency

* removes normalize dependency

* adds body margin reset

* enhancement: vf-grid--reset

Sometimes content needs to escape a grid container, for example full-width content inside of `.vf-body`.

This formalises an adhoc approach that was appearing in some places, like the component library when needing to show components like the global footer at full-screen width in the middel of the page, or on the groups sites with the local `.vfwp-column-reset`

* Somehow the old docs came back

* Remove uneedded dependencies

* the one where we update the card so it can be a link (#495)

* fixes the text moving issue on hover

* adds the option to use as link

* adds the option to use as link

* ENHANCEMENT - ship, enhance component generator (#477)

* CHORE - Ship component generator

It will be easier to create local design system components (think: `randomservice-component-idea`) if we ship the component generator.

* Pick up the project namespace for making the component

That is, if you're in an embl environment it gives you an `embl-` option ... EBI gives you `ebi-`, Service X gives `servicex-`

* Use package.json relative to project root

* Sneak in a templeting fix

Sorts an issue if docsection is empty.

In reality this whole chunk of code might go soon, but error proofing for now.

* Should default to the local environment

* Fix namespace guidance

* Make npm frasing future-tense

* Respect vfComponentPath; no need to set globals here

* CHORE - update component versions status (#496)

* Chore: update component versions, status

This goes through the components in prep of the beta:

- updates status of several components to be alpha/beta, depending on how much they're likely to change (quite a lot of the components are understandably alpha)
- makes a component's npm alpha/beta consistent with the alpha/beta status in the config.yml
- sets the version to `alpha/beta.0`, which will be bumped to `.1` on the next lerna publish

* Cleanup changelogs

No one wants to no the pre-release junk

* updates t-shirt sizes to be at least two letter variants

* fixes a little 2izes problem

* Run vf-tokens

* Remove zombie files from merge resolve

* Class name fixes, mostly on usage of `.vf-u-`

* should fix all outstanding issues with design tokens switch

* Fix njk templates

* Use integer sizing for type/heading

* fixes radio buttons not working (#497)

* Capture lerna bumps

* Update vf-core to alpha.8

* Update vf-content dependencies

* Update dependencies, remove trivial dependencies

* Version bumps to incorporate latest package.json fixes
parent 3269e2e6
Pipeline #26264 passed with stage
in 2 minutes and 46 seconds
......@@ -4,7 +4,6 @@ bin
.travis.yml
CHANGELOG.md
CONTRIBUTING.md
tools/component-generator
public
build
.max-age
......
# Visual Framework 2.0
[![This project is using Percy.io for visual regression testing.](https://percy.io/static/images/percy-badge.svg)](https://percy.io/EMBL/EMBL-Visual-Framework)
[![npm version](https://badge.fury.io/js/%40visual-framework%2Fvf-core.svg)](https://badge.fury.io/js/%40visual-framework%2Fvf-core) ![Chat for support on Discord](https://discordapp.com/api/guilds/596668639004983296/widget.png?style=shield) [![This project is using Percy.io for visual regression testing.](https://percy.io/static/images/percy-badge.svg)](https://percy.io/EMBL/EMBL-Visual-Framework)
---
**👋 Downloading or cloning this repo? 🛑**
Usually you don't need this whole repo. Only clone this repo if you wish to further develop the Visual Framework core or contribute a global component, otherwise: [see the "Get Started" section](#get-started).
Most won't need to clone this repo. Do so if you only wish to develop the architecture of the Visual Framework core or contribute a global component, otherwise: [see the online component library](https://visual-framework.github.io/vf-core/) and [Visual Framework welcome site](https://visual-framework.github.io/vf-welcome).
---
......@@ -18,65 +18,35 @@ The VF 2.0 enables consistency and portability, it is extensible, modular and ov
- **Demo:**  
[Online component library](https://visual-framework.github.io/vf-core)
  §   [Changelog](https://github.com/visual-framework/vf-core/blob/develop/docs/changelog/index.md)
- **Philosophy:**  
  §   [Changelog](https://github.com/visual-framework/vf-core/releases)
- **Why:**  
[Aims of the VF 2.0](https://blogs.embl.org/communications/2018/09/12/faster-scientific-websites-through-reusability/)
  §   [Principles and Methods](https://dev.beta.embl.org/guidelines/visual-framework/principles-methods/)
  §   [Principles and guidelines](https://visual-framework.github.io/vf-welcome/documentation/#guidelines)
- **Help out:**  
[Contributing guide](https://github.com/visual-framework/vf-core/blob/develop/CONTRIBUTING.md)
[Contributing guide](https://visual-framework.github.io/vf-welcome/documentation/#components)
  §   [Request a component](https://github.com/visual-framework/vf-core/issues/new?template=new-component-request.md)
  §   [Make a new component](https://visual-framework.github.io/vf-core/docs/guidelines.html)
- **Make it your own:**  
[Clone the child theme template](https://github.com/khawkins98/vf-child-playground)
### ⏰ When will this be ready?
- This is a v2.0 that was imagined in 2017 and development began in the summer of 2018.
- As of February 2019 we're on alpha.3.
- We're hopeful a beta could be ready before summer 2018.
Watch the [releases](https://github.com/visual-framework/vf-core/releases) and let us know your feedback: [issues](https://github.com/visual-framework/vf-core/issues) or [email](mailto:ken.hawkins@embl.de).
### 🤔 Why a VF?
The Visual Framework address three major needs:
1. ⚗️🌳 Life sciences: We address common needs for [life science websites](https://www.ebi.ac.uk/services). The Visual Framework can be easily tailored to niche needs, but out of the box it's pleasant looking, but dry and serious to support focus, clarity and data.
1. 🏰 Share only what you need to: the Visual Framework is designed to work with other frameworks (both CSS, like Bootstrap, and JS, like React or Angular). This allows common components (and brand design) to be shared between sites without cross-contaminating into another framework. We mainly achieve this by:
- Name spacing all selectors for CSS or JS (`vf-*`)
- No CSS styling on HTML elements. We only attached to name spaced classes, that is:
-`.vf-button {}`
- 🚫 `.button {}`
- 🚫 `button {}`
- 🚫🙊🙉 `div.button {}`
- 🖕 This necessarily requires a bit more class writing, but it ensures the Visual Framework won't break existing code.
- BYOJS: Bring your own JavaScript. We've included only a minimal amount of JS in components and it's fully optional (just remove [the JavaScript selectors](https://github.com/visual-framework/vf-core/issues/115#issuecomment-455524131); i.e. `data-vf-js-tabs`). So if you'd rather use Angular or Bootstrap for your tabs, the Visual Framework won't get in the way.
1. 🌕🌜 Use a little or a lot:
- A lot: The framework (and [child theme template](https://github.com/khawkins98/vf-child-playground)) will generate a monolithic `styles.css` and `script.js` that can be easily included, a la Bootstrap.
- A little: Instead you can include `.scss` partials or per-component `.css` and `.js` files. You can do this through making a [child theme](https://github.com/khawkins98/vf-child-playground) or [npm installs](https://www.npmjs.com/org/visual-framework).
[Use the template](https://github.com/visual-framework/vf-eleventy)
## 🚧 ✍ Developing, contributing
### How do I make my own theme or customise components?
<a id="get-started"></a> [See the contributing guide](https://github.com/visual-framework/vf-core/blob/develop/docs)
<a id="get-started"></a> [See the contributing guide](https://visual-framework.github.io/vf-welcome/documentation/#getting-started)
### I have an idea or concern!
There are a few ways that we discuss and track ideas:
- ⁉ General: Slack at [embl-vf.slack.com](https://embl-vf.slack.com/messages) for general ideas and discussion
- ⚙️ Technical: [GitHub issues here](https://github.com/visual-framework/vf-ebi/issues) for implementing deeply technical and specific issues, like the Sass build process, browser bugs
- ⁉ General: [Chat us](https://discord.gg/XHAvkUX) for general ideas and discussion
- ⚙️ Technical: [GitHub issues here](https://github.com/visual-framework/vf-core/issues) for implementing deeply technical and specific issues, like the Sass build process, browser bugs
- 🏢 E-mail: if you have a sweeping Big Idea™️, e-mail Ken Hawkins <ken.hawkins@embl.de>
## Versioning
[See the versioning guide in the changelog](https://github.com/visual-framework/vf-core/blob/develop/docs/changelog)
### Alpha development of v2.0
As the Visual Framework is in heavy, active development, we will have many `v2.0.0-alpha.X` releases. With new alphas planned on a monthly basis (last Thursday of each month).
[See the versioning guide](https://visual-framework.github.io/vf-welcome/documentation/guidelines/versioning/)
## Local development
To use the Visual Framework your machine will require some software to be installed to start. [See the "Setting up" guide](https://github.com/visual-framework/vf-core/blob/develop/docs/contributing/setting-up.njk).
To use the Visual Framework your machine will require some software to be installed to start. [See the "Setting up" guide](https://visual-framework.github.io/vf-welcome/documentation/getting-started/3-setting-up/).
......@@ -2,155 +2,3 @@
All notable changes to this project will be documented in this file.
See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
## 0.0.23 (2019-07-08)
**Note:** Version bump only for package @visual-framework/embl-boilerplate-page
## 0.0.22 (2019-06-21)
**Note:** Version bump only for package @visual-framework/embl-boilerplate-page
## 0.0.21 (2019-06-20)
**Note:** Version bump only for package @visual-framework/embl-boilerplate-page
## 0.0.20 (2019-06-20)
**Note:** Version bump only for package @visual-framework/embl-boilerplate-page
## 0.0.19 (2019-06-20)
**Note:** Version bump only for package @visual-framework/embl-boilerplate-page
## 0.0.18 (2019-06-20)
**Note:** Version bump only for package @visual-framework/embl-boilerplate-page
## 0.0.17 (2019-06-20)
**Note:** Version bump only for package @visual-framework/embl-boilerplate-page
## 0.0.21 (2019-06-20)
**Note:** Version bump only for package @visual-framework/embl-boilerplate-page
## 0.0.20 (2019-06-20)
**Note:** Version bump only for package @visual-framework/embl-boilerplate-page
## 0.0.19 (2019-06-20)
**Note:** Version bump only for package @visual-framework/embl-boilerplate-page
## 0.0.18 (2019-06-20)
**Note:** Version bump only for package @visual-framework/embl-boilerplate-page
## 0.0.17 (2019-06-20)
**Note:** Version bump only for package @visual-framework/embl-boilerplate-page
## 0.0.16 (2019-06-03)
**Note:** Version bump only for package @visual-framework/embl-boilerplate-page
## 0.0.15 (2019-05-02)
**Note:** Version bump only for package @visual-framework/embl-boilerplate-page
## 0.0.14 (2019-03-28)
**Note:** Version bump only for package @visual-framework/embl-boilerplate-page
## 0.0.13 (2019-02-28)
**Note:** Version bump only for package @visual-framework/embl-boilerplate-page
## 0.0.12 (2019-02-28)
**Note:** Version bump only for package @visual-framework/embl-boilerplate-page
# 0.1.0
### Added
- added this
- added that
### Changes
- changed this
- changed that
### Removed
- deleted this
- deleted that
......@@ -26,7 +26,7 @@
<section class="vf-banner vf-banner--fixed vf-banner--bottom vf-banner--phase" data-vf-js-banner data-vf-js-banner-state="dismissible" data-vf-js-banner-button-text="Close notice">
<div class="vf-banner__content | " data-vf-js-banner-text>
<div>
<h3 class="vf-text vf-text--heading-r">
<h3 class="vf-text vf-text-heading-3">
Don't need to customise the EMBL Design Language for Websites?
</h3>
<p class="vf-banner__text">Here's the core CSS and JS you need. Don't forget to <a href="http://dev.beta.embl.org/guidelines/visual-framework/dev-docs/" class="vf-link">consult the pattern library</a>.</p>
......
{
"version": "0.0.23",
"version": "1.0.0-alpha.2",
"name": "@visual-framework/embl-boilerplate-page",
"description": "embl-boilerplate-page component",
"homepage": "http://dev.beta.embl.org/guidelines/visual-framework/dev-docs/",
......
......@@ -2,229 +2,3 @@
All notable changes to this project will be documented in this file.
See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
## 0.0.16 (2019-07-08)
### Bug Fixes
* don't insert a root term as a crumb ([003d88c](https://github.com/visual-framework/vf-core/commit/003d88c))
* embl-grid-and-breadcrumbs ([68676a6](https://github.com/visual-framework/vf-core/commit/68676a6))
* only insert crumb if it respects the original term context of who/what/where ([2159778](https://github.com/visual-framework/vf-core/commit/2159778))
## 0.0.15 (2019-06-21)
### Bug Fixes
* don't insert a root term as a crumb ([003d88c](https://github.com/visual-framework/vf-core/commit/003d88c))
* embl-grid-and-breadcrumbs ([68676a6](https://github.com/visual-framework/vf-core/commit/68676a6))
* only insert crumb if it respects the original term context of who/what/where ([2159778](https://github.com/visual-framework/vf-core/commit/2159778))
## 0.0.14 (2019-06-20)
### Bug Fixes
* don't insert a root term as a crumb ([003d88c](https://github.com/visual-framework/vf-core/commit/003d88c))
* embl-grid-and-breadcrumbs ([68676a6](https://github.com/visual-framework/vf-core/commit/68676a6))
* only insert crumb if it respects the original term context of who/what/where ([2159778](https://github.com/visual-framework/vf-core/commit/2159778))
## 0.0.13 (2019-06-20)
### Bug Fixes
* don't insert a root term as a crumb ([003d88c](https://github.com/visual-framework/vf-core/commit/003d88c))
* embl-grid-and-breadcrumbs ([68676a6](https://github.com/visual-framework/vf-core/commit/68676a6))
* only insert crumb if it respects the original term context of who/what/where ([2159778](https://github.com/visual-framework/vf-core/commit/2159778))
## 0.0.12 (2019-06-20)
### Bug Fixes
* don't insert a root term as a crumb ([003d88c](https://github.com/visual-framework/vf-core/commit/003d88c))
* embl-grid-and-breadcrumbs ([68676a6](https://github.com/visual-framework/vf-core/commit/68676a6))
* only insert crumb if it respects the original term context of who/what/where ([2159778](https://github.com/visual-framework/vf-core/commit/2159778))
## 0.0.11 (2019-06-20)
### Bug Fixes
* don't insert a root term as a crumb ([003d88c](https://github.com/visual-framework/vf-core/commit/003d88c))
* embl-grid-and-breadcrumbs ([68676a6](https://github.com/visual-framework/vf-core/commit/68676a6))
* only insert crumb if it respects the original term context of who/what/where ([2159778](https://github.com/visual-framework/vf-core/commit/2159778))
## 0.0.10 (2019-06-20)
### Bug Fixes
* don't insert a root term as a crumb ([003d88c](https://github.com/visual-framework/vf-core/commit/003d88c))
* embl-grid-and-breadcrumbs ([68676a6](https://github.com/visual-framework/vf-core/commit/68676a6))
* only insert crumb if it respects the original term context of who/what/where ([2159778](https://github.com/visual-framework/vf-core/commit/2159778))
## 0.0.14 (2019-06-20)
### Bug Fixes
* don't insert a root term as a crumb ([003d88c](https://github.com/visual-framework/vf-core/commit/003d88c))
* embl-grid-and-breadcrumbs ([68676a6](https://github.com/visual-framework/vf-core/commit/68676a6))
* only insert crumb if it respects the original term context of who/what/where ([2159778](https://github.com/visual-framework/vf-core/commit/2159778))
## 0.0.13 (2019-06-20)
### Bug Fixes
* don't insert a root term as a crumb ([003d88c](https://github.com/visual-framework/vf-core/commit/003d88c))
* embl-grid-and-breadcrumbs ([68676a6](https://github.com/visual-framework/vf-core/commit/68676a6))
* only insert crumb if it respects the original term context of who/what/where ([2159778](https://github.com/visual-framework/vf-core/commit/2159778))
## 0.0.12 (2019-06-20)
### Bug Fixes
* don't insert a root term as a crumb ([003d88c](https://github.com/visual-framework/vf-core/commit/003d88c))
* embl-grid-and-breadcrumbs ([68676a6](https://github.com/visual-framework/vf-core/commit/68676a6))
* only insert crumb if it respects the original term context of who/what/where ([2159778](https://github.com/visual-framework/vf-core/commit/2159778))
## 0.0.11 (2019-06-20)
### Bug Fixes
* don't insert a root term as a crumb ([003d88c](https://github.com/visual-framework/vf-core/commit/003d88c))
* embl-grid-and-breadcrumbs ([68676a6](https://github.com/visual-framework/vf-core/commit/68676a6))
* only insert crumb if it respects the original term context of who/what/where ([2159778](https://github.com/visual-framework/vf-core/commit/2159778))
## 0.0.10 (2019-06-20)
### Bug Fixes
* don't insert a root term as a crumb ([003d88c](https://github.com/visual-framework/vf-core/commit/003d88c))
* embl-grid-and-breadcrumbs ([68676a6](https://github.com/visual-framework/vf-core/commit/68676a6))
* only insert crumb if it respects the original term context of who/what/where ([2159778](https://github.com/visual-framework/vf-core/commit/2159778))
## 0.0.9 (2019-06-03)
### Bug Fixes
* don't insert a root term as a crumb ([003d88c](https://github.com/visual-framework/vf-core/commit/003d88c))
* embl-grid-and-breadcrumbs ([68676a6](https://github.com/visual-framework/vf-core/commit/68676a6))
* only insert crumb if it respects the original term context of who/what/where ([2159778](https://github.com/visual-framework/vf-core/commit/2159778))
## 0.0.8 (2019-05-02)
### Bug Fixes
* don't insert a root term as a crumb ([003d88c](https://github.com/visual-framework/vf-core/commit/003d88c))
* embl-grid-and-breadcrumbs ([68676a6](https://github.com/visual-framework/vf-core/commit/68676a6))
* only insert crumb if it respects the original term context of who/what/where ([2159778](https://github.com/visual-framework/vf-core/commit/2159778))
## 0.0.7 (2019-03-28)
### Bug Fixes
* don't insert a root term as a crumb ([003d88c](https://github.com/visual-framework/vf-core/commit/003d88c))
* only insert crumb if it respects the original term context of who/what/where ([2159778](https://github.com/visual-framework/vf-core/commit/2159778))
## 0.0.6 (2019-02-28)
**Note:** Version bump only for package @visual-framework/embl-breadcrumbs-lookup
## 0.0.5 (2019-02-28)
**Note:** Version bump only for package @visual-framework/embl-breadcrumbs-lookup
# 0.1.0
### Added
- added this
- added that
### Changes
- changed this
- changed that
### Removed
- deleted this
- deleted that
title: EMBL Breadcrumbs lookup
label: EMBL Breadcrumbs
status: alpha
context:
component-type: embl-block
......
{
"version": "0.0.16",
"version": "1.0.0-alpha.2",
"name": "@visual-framework/embl-breadcrumbs-lookup",
"description": "embl-breadcrumbs-lookup component",
"homepage": "http://dev.beta.embl.org/guidelines/visual-framework/dev-docs/",
......
......@@ -2,155 +2,3 @@
All notable changes to this project will be documented in this file.
See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
## 0.0.18 (2019-07-08)
**Note:** Version bump only for package @visual-framework/embl-conditional-edit
## 0.0.17 (2019-06-21)
**Note:** Version bump only for package @visual-framework/embl-conditional-edit
## 0.0.16 (2019-06-20)
**Note:** Version bump only for package @visual-framework/embl-conditional-edit
## 0.0.15 (2019-06-20)
**Note:** Version bump only for package @visual-framework/embl-conditional-edit
## 0.0.14 (2019-06-20)
**Note:** Version bump only for package @visual-framework/embl-conditional-edit
## 0.0.13 (2019-06-20)
**Note:** Version bump only for package @visual-framework/embl-conditional-edit
## 0.0.12 (2019-06-20)
**Note:** Version bump only for package @visual-framework/embl-conditional-edit
## 0.0.16 (2019-06-20)
**Note:** Version bump only for package @visual-framework/embl-conditional-edit
## 0.0.15 (2019-06-20)
**Note:** Version bump only for package @visual-framework/embl-conditional-edit
## 0.0.14 (2019-06-20)
**Note:** Version bump only for package @visual-framework/embl-conditional-edit
## 0.0.13 (2019-06-20)
**Note:** Version bump only for package @visual-framework/embl-conditional-edit