Website updates - Tag truncation

[majedelass]

📌 Summary

If merged, this PR will update the guidelines and code tabs of the Helio website.

🛠️ Detailed description

This is necessary for the truncation changes applied to the tag component.

🔗 External links

Jira ticket: HDS-4505
Figma file: File

---

💬 Please consider using conventional comments when reviewing this PR.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
hds-showcase	✅ Ready (Inspect)	Visit Preview	Feb 19, 2025 9:39pm
hds-website	✅ Ready (Inspect)	Visit Preview	Feb 19, 2025 9:39pm

[majedelass]

@dchyun it seems as though I may have ported in your work when I changed branches. Is there a way to remove them? @alex-ju maybe this is a task for you?

[alex-ju]

@dchyun it seems as though I may have ported in your work when I changed branches. Is there a way to remove them? @alex-ju maybe this is a task for you?

I imagine this branch was split off of dchyun/tag-text-truncation so I just changed its base to reflect that.

There are two possible scenarios now:

• this work gets reviewed/approved/merged into Dylan's branch, then that one gets merged to main
• Dylan's branch gets merged to main sooner than this one, in which case this branch will automatically update its base to be main

[shleewhite]

Overall seems fine. I just noticed one issue in the anatomy tab and had some non-blocking suggstions to simplify the language.

[dchyun]

@dchyun it seems as though I may have ported in your work when I changed branches. Is there a way to remove them? @alex-ju maybe this is a task for you?

I imagine this branch was split off of dchyun/tag-text-truncation so I just changed its base to reflect that.

There are two possible scenarios now:

• this work gets reviewed/approved/merged into Dylan's branch, then that one gets merged to main
• Dylan's branch gets merged to main sooner than this one, in which case this branch will automatically update its base to be main

I think we can keep this branch separate and merge it into main separately. It can be held back from merging into main until the release occurs with the tag changes.

[KristinLBradley]

Rebasing this branch off of the latest version of the dchyun/tag-text-truncation should get rid of the unrelated file diffs. You will need to fix conflicts as well.

@dchyun, perhaps you could help @majedelass with this?

[majedelass]

@KristinLBradley I think we decided to change the base to main so that merging the component updates doesn't merge these and put it on the website before release.

[KristinLBradley]

@KristinLBradley I think we decided to change the base to main so that merging the component updates doesn't merge these and put it on the website before release.

Ok well if this branch was created from the dchyun/tag-text-truncation branch you'll still need to rebase off of the latest code from it and fix the conflicts so that this branch reflects the actual intended changes. Although you could wait until the parent branch is merged into main (if that's going to be soon) and then rebase off of main. (Once the parent branch is merged the base for this branch will automatically change to main.)

The base branch was changed.