Michael added a comment.
In T273039#6799614 <https://phabricator.wikimedia.org/T273039#6799614>, @Sarai-WMDE wrote: > Is it safe to assume that we'd probably need two link variants then? A //Link// (with its own, autonomous style – e.g. our "Show query in the Query Service") and an //Inline link// (which style blends with that of the text where it's embedded, but that it's still recognizable as a link, e.g. the "SPARQL" and "Feedback is welcomed here" links in the QB introductory description). It is entirely possible to instead have a prop that says something like `inheritStyles=true` or `isStandalone=false`. Rather, I wonder if a standalone component would make more sense in cases where the standalone-link is supposed to be more prominent. Like the "Get Started >"-Link on https://design-system.service.gov.uk/. It is clearly a link - conceptually, visually, behaviorally, technically: F34089032: image.png <https://phabricator.wikimedia.org/F34089032> TASK DETAIL https://phabricator.wikimedia.org/T273039 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: bete, Michael Cc: ItamarWMDE, bete, Michael, Sarai-WMDE, Aklapper, Ladsgroup, Lydia_Pintscher, Akuckartz, Nandana, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer, _jensen, rosalieper, Scott_WUaS, Volker_E, Wikidata-bugs, aude, Mbch331
_______________________________________________ Wikidata-bugs mailing list Wikidata-bugs@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
