GitLab

Updates the roadmap following the April consultation.

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

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

* tidies up variants and normalises font sizes

* tidies up variants and normalises font sizes

* Patterns: refresh example boilerplates

* Added react button component

* Added missing prop to vf-button react and updated docs

* fixed unnecessory version bump

* Reverted some incorrect versions
Co-authored-by: Nitin Jadhav <nitin@ebi.ac.uk>

* Docs: usage guidance position

As discussed in previous vf-ux conversations, this moves the "usage" section higher up the page; part of #1175

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

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

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

* changes how width works so it responds to viewport

* updates changelog to correct the versioning

* First commit for back-to-top component

* Added css styles for component and floating variant

* Implemented floating behaviour and fixed lots of issues in intial implementation

* Fixed bugs and implemented some new features. Added react version.

* Implemented Ken's comments

* Removed unneccessory condition

* Reverted siteConfig version which is unncessory

* Component: vf-back-to-top refinements (#1493)

Looking good, thanks
Co-authored-by: Nitin Jadhav <nitin@ebi.ac.uk>
Co-authored-by: Ken Hawkins <khawkins98@gmail.com>

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

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

* enhancement: component structure

After recent conversations, it's become clear that:

1. examples/boilerplates are overlooked in their current location
2. most users not deeply familiar with the VF need broader guidance first
3. we should present broader component, blocks guidance before elements

This should make using the "correct" things more obvious.

* Update index.njk

* Components and patterns

* Use dev css

- use blobl links to github
- put link about creating components in a more visible spot

I expect this PR will grow as we go through the sprint with Nitin.

* corrects link colour when hovering on visited link

* corrects link colour when hovering on visited link

* updates and deprecates bits of the table

* some adjustments after feedback

* enhancement: vf-hero safe text

Allows html (for links) in vf-hero__subheading (and a few other fields) when using the Nunjucks template.

This reverts commit b99f5f9e.

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

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

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

Non-logged users won't be blocked.

As discussed in #1443 and the VF-UX clinics, this introduces some text about accessibility in the VF, and adds a section to the README.md template.

Will trigger a re-release of 3.0.0-beta.0 to fix garbled version number.

* Bug: garbled version number of vf-navigation

Will trigger a re-release of 3.0.0-beta.0 to fix garbled version number.

* Bug: Broken Sass imports, variables

Closes #1469

Also does some linting and a formatting fix fro the component library.`

This reverts commit 81a0c0bd.

`mixins/vf-utility-mixins.scss` was missing from the rollup import, which breaks use in some projects (like vf-react that use the React sass build)

In React (and I imagine other places) they're more particular about the location of the JS module, by adding a `try/catch` we can improve the ability to use VF JS in places.

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

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