Skip to content

[STUD-507][Enhancement]: Update tooltip copy within the distribution user flow -- follow-up - #982

Merged
ITurres merged 2 commits into
masterfrom
STUD-507-Update-Release-Track-tooltip-copy--follow-up
Feb 26, 2026
Merged

ITurres merged 2 commits into
masterfrom
STUD-507-Update-Release-Track-tooltip-copy--follow-up

Conversation

@ITurres

@ITurres ITurres commented Feb 25, 2026 •

Copy link
Copy Markdown
Member

Pull Request — Issue STUD-507

Overview

This PR centralizes and updates release/track tooltip copy in shared constants and replaces placeholder text in release details. It also aligns track copyright tooltip wording and links to the dedicated copyright FAQ anchor.

Clarification: for track-related fields in AdvancedTrackDetails that need inline links, we can keep the JSX inline as-is, or consider a React-node constants map. Adding the copy to shared constants and splitting strings at render time is possible but is not the ideal approach.


Files Summary

Total Changes: 3 files

Modified (3)
  • apps/studio/src/common/constants.ts
    • Added shared tooltip copy constants and a copyright FAQ URL.
  • apps/studio/src/pages/home/releases/release/ReleaseDetails.tsx
    • Replaced placeholder tooltips with shared constants.
  • apps/studio/src/pages/home/releases/release/tracks/AdvancedTrackDetails.tsx
    • Reused shared tooltip copy, refined wording, and switched FAQ link.

Impact

  • Tooltip copy is now consistent across release and track forms.
  • Release details fields no longer show placeholder text.
  • Copyright tooltips now link directly to the copyright FAQ section.

Testing

  • Not run (copy updates only).

Related Issues


Dependencies

  • No new dependencies.

Additional Notes

  • Follow-up work may remove some advanced track fields in phase 2 (existing TODOs).

--END--

@ITurres ITurres self-assigned this Feb 25, 2026
@ITurres
ITurres requested a review from a team as a code owner February 25, 2026 17:41
@github-actions

Copy link
Copy Markdown

Visit the studio preview URL for this PR 🚀 : https://982.artist.preview.newm.io/

@dmkirshon dmkirshon left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, no blocking comments.

Comment on lines +67 to +85
export const FIELDS_TOOLTIP_COPY_TEXT = {
instrumental: `Tracks without vocals or lyrics should be indicated as an instrumental.
Failure to accurately label the track could result in a declined distribution submission.`,

originalReleaseDate: `If your release has already been distributed on other platforms,
you may input the original release date here, but it's not required.`,

releaseCodeNumber: `A release code number is a unique code that identifies your release.
If you do not already have one, leave this field blank,
and a new release code number will be auto-generated for you.`,

releaseCodeType: `If you already have a release code,
select the code type here and enter the code in the next field. If not,
leave this field blank and a new release code will be auto-generated for you.`,

releaseDate: `When setting a release date, remember to factor in approval
from any collaborators and/or featured artists, as well as quality assurance checks,
which can take up to 15 days.`,
} as const;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I could see this living in it's own file in common for copy text or some other organization pattern. It can wait till later in the end of phase 2 when other structure gets consolidated.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree! I've updated STUD-560 to add this task as a cleanup.

@ITurres
ITurres merged commit 89b548d into master Feb 26, 2026
2 checks passed
@ITurres
ITurres deleted the STUD-507-Update-Release-Track-tooltip-copy--follow-up branch February 26, 2026 15:53
@ITurres ITurres mentioned this pull request Feb 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants