-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Figure out a replacement for #1 links in tables #8109
Comments
I read this as a non-issue, simply because there are no alternative solutions: if it's not going to be a website widget, however it may look, is a bit more useful, but I don't see much benefit in making it solely for the wiki purposes (not sure how often people share multiplayer links on forums -- supporting that widens the scope of work for whoever's in charge). I guess this is a direct consequence of the layout chosen for the tournament results. since real link title ( - [Germany 5 : 2 Australia](https://osu.ppy.sh/community/matches/100000001)
- [Malaysia 2 : 5 France](https://osu.ppy.sh/community/matches/100000002)
- [Austria 2 : 5 Norway](https://osu.ppy.sh/community/matches/100000003) |
#1
links in tables
#1
links in tables
71 out of 17876 in tournament articles. even if there are two of them... we could just have two widgets/images
yes, it would still be repetitive since it's a match link, but it would require orders of magnitude less work than hundreds of flag references. the point of this is to have something more pleasing/sensible than a "
it would just be for the wiki, yes. as you said, other places than the wiki would not have any immediate need/use for this.
going at this from an aesthetic point of view, tables are a must for the alignment of flags and country names. very long lists just look a lot worse. this is why i required the osu! originals article to have tables and (let me rant a bit) i hope my sentiment is understandable when i say that not using the features available would make for a wiki that is very unappealing to look at. i know we're limited by markdown but infoboxes and footnotes really were a step forward, and i'd encourage not just things that will make the osu! wiki look more like wikipedia. the wiki really needs more work on the graphical side (not just the myriad of outdated images). this is a long-term goal of mine - for example, i'd love for the judgement articles to have infographics that explain hit windows (imagine a ur bar), and the notelock article to have pictures that show how hit windows interact. things like this would really polish the usefulness of the wiki for beginner rhythm game players and players more familiar with other games. so no, this is not a non-issue. this is an area that can be improved (albeit by a small amount). |
I totally share your sentiment! |
thoughts basically the same idea as in https://osu.ppy.sh/wiki/en/osu!_originals. not sure if there's a better way to represent mp links (but they'd have tooltips) |
I'm fine with this suggestion too, but I can't understand why you'd prefer it over my PR you closed, that one has meaningful buttons instead of vague icon that you probably need to view the tooltip for |
they weren't buttons, just text links. the icon may be vague because there's no better signifier for "mp link" atm, but it's still better than spamming the same word for each line of each table. you already have enough bits of information to convey via text and what each of the same links point to is not one of them |
The recent Resurrection Cup 2024 Results news post used chainlink icons to indicate links to the beatmaps. Personally I think it looked great. I would be in favour of applying it in other locations, such as tournament wiki pages or the osu! originals page as well. |
i think this convention started in tournament articles as a way to prevent spamming "link" or some other wording in tables, for situations where any other name for the link isn't applicable since it's covered by the table header.
i can think of two solutions:
i'm imagining some kind of button- or card-looking thing, but if you have any good ideas they would be appreciated
The text was updated successfully, but these errors were encountered: