You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a metadata component available in the publishing components gem that can be used in rendering applications.
However, several applications appear to also have their own metadata components, applications could be using their own variation of the component for several reasons, either because the metadata component was not available at the time, or it does not provide all the requirements.
We should look to either directly replace the metadata components in the rendering app with the one from the publishing components gem, or update the metadata component in the gem where appropriate, so the app component can be replaced.
Why
Help keep the UI consistent across applications
Helps to keep the codebase DRY, we only need to make changes in one place
Make it easier to know which component to choose from
We may improve the existing component by providing additional features identified in rendering applications
The screenshots below show examples of the varying implementation of the metadata component, as well as the different HTML used, visually they will have different font-size, color and spacing.
Silly question, what will the impact be once front-end apps merge?
I think this depends on the approach used when the frontend apps are merged, and if this only includes public facing frontend applications, is content-publisher included in the consolidation work for example. It's not something I've been directly involved in, but happy to discuss further, will provide any other info where I can 👍
What
We have a metadata component available in the publishing components gem that can be used in rendering applications.
However, several applications appear to also have their own metadata components, applications could be using their own variation of the component for several reasons, either because the
metadata
component was not available at the time, or it does not provide all the requirements.We should look to either directly replace the
metadata
components in the rendering app with the one from the publishing components gem, or update themetadata
component in the gem where appropriate, so the app component can be replaced.Why
The screenshots below show examples of the varying implementation of the
metadata
component, as well as the different HTML used, visually they will have different font-size, color and spacing.Screenshots Comparisons
Content Data Admin
Frontend
Content Publisher
Government Frontend
In this example, the
metadata
component from the gem is already included at the top of this page - https://www.gov.uk/government/case-studies/2013-elections-in-swaziland, but an additional request for thepublished-dates
is sent.The text was updated successfully, but these errors were encountered: