Roadmap

Major projects and features planned for the next period of time.

This is a snapshot of work planned in the Visual Framework project milestones. These are in addition to ongoing feature development and support.

If you have a mjor idea not represented here, discuss it on Slack or raise an issue.

By the end of 2020

A selection of example pages and boilerplates

There are many ways to implement a "search" page and section. What is the most common and standardisable? What about for a research group? A user's profile page?

By end of March 2021

Create a training programme for developers

How to get started with the VF common scenarios specific use cases.

Create a desktop component library

That is: port the Sketch component library to Figma and update it to match changes.

Legacy browser support

Supporting older browsers (those without CSS grid and custom properties/variables) is a non-trivial task that needs constant monitoring and support.

By end of June 2021

Component long tail

There are several low-priority components that still need to be implemented, such as: data tables, definition lists, table of contents.

Forms on mobile

Establish and implement how to best handle long section of form options on mobile.

Explore internal and functional components and patterns

Most of the components and patterns in the VF 2.0 have been designed with the corporate EMBL websites in mind. Among the founding ideas was to have variants based on a two-dimensional axis (internal vs external, and functional vs inspirational). How would we deliver and document these? Is it the correct idea?

Introduce a type scale

The VF typography and spacing continues to be refined, however we're still lacking an explicit type scale.

No fixed date

These features and milestones are liking prioritisation, either due to a lack of major interest or team capacity to deliver. Code contributions and input are welcome.

Optimising the component library build efficiency

Currently, the component library relies on Fractal, this is helpful in many ways but also limits some options. In principle, we could solely rely on 11ty for our component library but there are performance questions.

contentHub metrics and editing

The contentHub allows us to pull content into any VF-powered page, however we can do more here: how to track where content is used? how to better support editing?

React and Angular components

While the Visual Framework does not require specific tooling, we know two of the places the VF will be used are in React and Angular. We could provide native templates as part of the individual components.

Find an issue on this page? Propose a change or discuss it.