Move updateInfo from footer to header #51
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.




Ref
#48
Why
What
Fix it.
How
This pull request refactors how the update information is displayed by reusing and customizing the existing
article-metadata-footerelement. Instead of always creating a new<p>tag, it now clones the footer, updates its attributes, and inserts the update information in a more structured way. This approach improves consistency with the page’s metadata layout and enhances maintainability.Improvements to metadata display:
article-metadata-footerelement to create a new container (custom-header-from-article-metadata-footer) for update information, ensuring consistent styling and structure with existing metadata.id,data-bi-name,data-test-id, andclassName) on the cloned container for better identification and styling.langattribute on the metadata list to match the current language.<p>tag after thespan.badgeinside the relevant list item, improving semantic placement.