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
Is your feature request related to a problem? Please describe.
How can we track relevant notes -- such as metadata nuances or specific guides for users on a per studio/performer/tag basis? We currently lack this capability. Generally the community discusses these nuances and we rely on those who are very active to convey this info back to the community when the topic arises again, or if this issue is detected during the voting process.
A real use case example could be performer X keeps getting confused for performer Y despite a differentiating image and disambiguation field. Therefore, users inevitably keep erroneously editing the details when confusing the two performers. While a prospective lock field feature could mitigate this specific example, it would also be beneficial to make a pinned comment about this issue, which would inform the user before they proceed to make an edit. Such as "Please be aware Performer Y is not to be confused with Performer X, blah blah blah."
Describe the solution you'd like
The ability for mods to pin (and edit) comments on performer, studio, and scene pages. And to priortize the placement of these pinned comments so they receive maximal attention.
Pinned comments would be presented on the ux in two locations:
Pinned comments are displayed at the top of all #edit comments on their respective pages
Pinned comments are displayed near the top of the landing page on their respective pages.
Displayed in a card container
Text displayed is limited to one line, such as text-overflow: ellipsis; -webkit-line-clamp: 1;. Excess characters get truncated
The entire card container is a hot link to the pinned comment on the #edit page
Pinned comments would act highly specified guides or important notes on a per studio/performer/tag/scene basis. While one could make amendments to the StashDB docs, those docs are more suitable for global guideline and would get very bogged down with the minutia of highly specified notes/guides for each studio/performer/tag/scene.
Example of pinned comment placement on the landing page:
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
How can we track relevant notes -- such as metadata nuances or specific guides for users on a per studio/performer/tag basis? We currently lack this capability. Generally the community discusses these nuances and we rely on those who are very active to convey this info back to the community when the topic arises again, or if this issue is detected during the voting process.
A real use case example could be performer X keeps getting confused for performer Y despite a differentiating image and disambiguation field. Therefore, users inevitably keep erroneously editing the details when confusing the two performers. While a prospective lock field feature could mitigate this specific example, it would also be beneficial to make a pinned comment about this issue, which would inform the user before they proceed to make an edit. Such as "Please be aware Performer Y is not to be confused with Performer X, blah blah blah."
Describe the solution you'd like
The ability for mods to pin (and edit) comments on performer, studio, and scene pages. And to priortize the placement of these pinned comments so they receive maximal attention.
#edit
comments on their respective pagestext-overflow: ellipsis; -webkit-line-clamp: 1;
. Excess characters get truncated#edit
pageExample of pinned comment placement on the landing page:
The text was updated successfully, but these errors were encountered: