Deep linking to runs on schedule pages

[Planks]

The schedule page should have two deep linking functions - individual runs via run UUID and #now

In page references often suffer from being implemented with no discovery, so we should address that as follows by exposing them to the user in the following places:

• Each run row should have a "share" link in the expanded view which simply links back to the row in question. It should be marked as rel="nofollow" as it is circular.
• #now should be able to be discovered from a similar link available close to the "now and next" box at the top of the page. Again, as it's circular, it should also be rel="nofollow"

[BobChao87]

We could also do #next, I can see that being useful for people. We also have the option of using the run's position in the marathon instead of the UUID, though I'm unsure if that's immutable or not.

[Planks]

We could also do #next, I can see that being useful for people. We also have the option of using the run's position in the marathon instead of the UUID, though I'm unsure if that's immutable or not.

Good point - I agree we should also have #next. In v1 we already have "now" and "next" highlight boxes at the top of each live schedule, but you can't click on them. So these wouldn't need extra share buttons, you'd just make the boxes hotspots.

[Planks]

We also have the option of using the run's position in the marathon instead of the UUID, though I'm unsure if that's immutable or not.

I don't think linking by any sort of relative ordering is useful because organisers move around runs so much. The use case for deep linking a row is mostly so people can link directly to a specific run in the schedule and we'd want that link to remain valid through all schedule edits.

[BobChao87]

We also have the option of using the run's position in the marathon instead of the UUID, though I'm unsure if that's immutable or not.

I don't think linking by any sort of relative ordering is useful because organisers move around runs so much. The use case for deep linking a row is mostly so people can link directly to a specific run in the schedule and we'd want that link to remain valid through all schedule edits.

I was afraid that was the case. Oh well, it was worth a shot as then the link would have been slightly more meaningful. Consistency is better.

[Planks]

If @duncte123 would be able to tweak the database, at submission time a "friendly uuid" could be generated and added to the submission row like

BobChao87-MickeyMouseGame-kasdjf where kasdjf is just some garbage to deduplicate

Seems a lot of work for a relatively minor feature but it would make the URLs much, much nicer particularly when linked on an instant messenger like Discord.

We don't want the URL to expire if any of the run properties are changed so this is something that would need to be locked in permanently when the submission is first created.

[BobChao87]

Yeah, I agree. We'll just stick with our existing immutable properties and maybe in the future we can revisit. I made them a little clearer by making the anchor be #run-UUID.

[BobChao87]

Will be considered resolved after this issue is fixed. #32 (comment)