GitLab

* Feature: allow examples of variants

Adds technical support to facilitate #1530 by:

1. Adding a new component cotnext variable `isExample: true`
2. Adding template support in the component library

While these are technically new variants, they do not generate additional template files and are shown in contextually appropriate way.

Incroporating examples also brings some required updates to the layout of  the component pages — most of which have been overdue, such as removing the tree layout (whose function is planned to be replaced by the forthcoming mega menu).

When vf-location-nearest activates a tab, browsers scroll that content into focus -- this is not desirable.

* enhancement: create design-token for blue-interactive

Create new background blue and add `interactive-color` sass map

For #1688

* use new interactive token

* Add interactive token to docs

* Generate ios and css custom propos

* Documentation: update component creation process

We've had some information but it's been:

1. Hard to find
2. Out of date

This sorts that.

* Update component creation guidance

* Component release 20211001-01

* Update release notes

* Remove hero duplication

* Use directory-style pages

* Building page tidy

* Revise principles section

* More directory page structure work

* Developing page cleanup

Deprecates `vf-box`. Most use cases should now use the `vf-card` component. A new layout-specific `vf-box` may be made in the future.

Closes #1667

Addresses issues when showing remote content on EMBL sites; https://gitlab.ebi.ac.uk/emblorg/backlog/-/issues/583

- when no results, embl-content-hub-loader would error if an empty message is not set
- embl-notifications was still using the deprecated `vf-banner--phase` variant

* Accessibility: When section header is a link, it should still be wrapped an `h2`
  * https://github.com/visual-framework/vf-core/issues/1683
* Whitespace control

* chore: drop-down and progress component cleanup

Following work in #1682 and #1679 to introduce the new alpha components this cleans up a pair of rough edges.

- css custom prop usage
- ie11 fallback
- njk typo
- njk whitespace control
- add aria progress  bar role
  - maybe more work to do there in the future https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_progressbar_role
- add context conditionals

* Update vf-progress-indicator.jsx

* CSS linting and nesting

* More linting

* Use z-index tokens, context

* Small typo fixes

* Remove unused event handler

fixes a few edge cases in the not-yet-release vf-bookmark.

- icon colour inheritance
- icon outline size
- icon positioning
- star vs heart icon

* Initial commit for progress indicator

* Implemented some review comments, which were left untreated in hurry

* Added css variable for with: 100%

* first commit for vf-dropdown

* Removed unwanted icon

* Move about line down

About should be one short sentence.

* Fixes some review comments

* Don't announce svg

* Update z-index tokens
Co-authored-by: Ken Hawkins <khawkins98@gmail.com>

Resolves an accessibility issue with contrast for the striped card subheading variant.

Closes #1657

Co-authored-by: Renovate Bot <bot@renovateapp.com>

Fixed some typos.

* draft home page and card improvements

vf-hero+search and directory pages still to be done

* vf-hero bottom margin refinement

* Spacing refinements

* News container as 4 columns, summary with optional paragraph text

* Add news to landing page layout

* Landing page buildout

* Add vf-stack--400 to most body tags

* Revise scientific resource page to include prototype search box

* Update CHANGELOG.md

* vf-hero--search protyping

* Component: vf-bookmark

Creates an initial vf-bookmark with a few options:

- label_inactive: Add as bookmark
- label_active: Bookmarked
- is_active: false
- modifier: button or inline
- icon: heart or star

for #1654

* Add bookmark_href

* Adds css, docs

* Show sample active/inactive states

* add aria-hidden="true"

* Update README.md

Co-authored-by: Renovate Bot <bot@renovateapp.com>

Co-authored-by: Renovate Bot <bot@renovateapp.com>

Co-authored-by: Renovate Bot <bot@renovateapp.com>

Co-authored-by: Renovate Bot <bot@renovateapp.com>

Adds experimental angular support. See README.md for more.

The README was missing it's `## Usage` header.

Co-authored-by: Renovate Bot <bot@renovateapp.com>

Co-authored-by: Renovate Bot <bot@renovateapp.com>

Co-authored-by: Renovate Bot <bot@renovateapp.com>

Co-authored-by: Renovate Bot <bot@renovateapp.com>

The `html:not(.vf-disable-deprecated)` is now  disabled as it causes a specificity issue with vf-footer.

No changelog as the latest changes have not been shipped.

This deprecates vf-link-list as many components are either widely unused or only seldom used — for the components that aren't yet used much we also have major revisions coming and we wish to discourage use of components that are about to be overhauled.

- Links List Default: use vf-list + vf-heading
- Links List no heading: use vf-list
- Links List Tight: use vf-list  (we may add a vf-list--tight variant subject to demand)
- Links List Very Easy: see above
- Links List Easy: to be overhauled as vf-navigation--on-page
- Links List Has Images: use vf-summary--has-image or vf-flag--middle

Additionally there has been a confusion between when to use vf-list and vf-link-list that we're want to address.

Closes #1649

* Deprecate: vf-header

vf-header was an early concept on how we might accommodate multi-layers of branding ... but:

- It was never successfully used in production
- Is out of date technically and visually
- Has questionable IA/UX merit in the current context

Therefore it is being deprecated.

No migration guidance is supplied as it is not used in production.

It is also being removed from the default rollup Sass/CSS.

These two components never saw wide adoption and neither the technical tooling nor use case was ever proven.

- https://stable.visual-framework.dev/components/vf-activity-list/
- https://stable.visual-framework.dev/components/vf-activity-group/

This deprecates them by following the guide at https://stable.visual-framework.dev/guidance/deprecating-components/

Co-authored-by: Renovate Bot <bot@renovateapp.com>

Co-authored-by: Renovate Bot <bot@renovateapp.com>

* Bug: unused gulp-watch dependency

This issue addresses #1644 by removing the unused `gulp-watch` dependency.

(It seems the reporting account for ticket #1644 has been deleted, taking the ticket with it.)

* Update _gulp_rollup.js