Closed what-does-that-do closed 11 months ago
It's just because the link includes the live url
why are we not using relative links? is there something I'm missing here?
Because for some reason, using relative links confuses the vue generator, and it just saves a massive headache of forcing vue to recognise the link inside the markdown. It seems to notice the https and decide it's a link. Don't ask me how it works - I have no idea! I tried using relative links, it didn't like them.
It's just because the link includes the live url
why are we not using relative links? is there something I'm missing here?
Because for some reason, using relative links confuses the vue generator, and it just saves a massive headache of forcing vue to recognise the link inside the markdown. It seems to notice the https and decide it's a link. Don't ask me how it works - I have no idea! I tried using relative links, it didn't like them.
Hmmmm... that's quite the conundrum
I'm really hesitant to have more absolute links to our own site. They come with all sorts of issues: harder to develop, harder to test, harder to migrate domains (e.g. from hr-robocon.org to robocon.uk).
They seem to have potential to cause a great deal of annoyance... but I know it must be possible to do something else! Your change adds some relative URLs and we already have some.
I'm not going to stop you- there are already links in the places you edited that use the absolute url -but I'd strongly recommend that we instead look at this closer (is it, for example, that we're using links in angle brackets rather than standard markdown links or a-tags?)
Let me know what you want to do 😄
It's just because the link includes the live url
why are we not using relative links? is there something I'm missing here?
Because for some reason, using relative links confuses the vue generator, and it just saves a massive headache of forcing vue to recognise the link inside the markdown. It seems to notice the https and decide it's a link. Don't ask me how it works - I have no idea! I tried using relative links, it didn't like them.
Hmmmm... that's quite the conundrum
I'm really hesitant to have more absolute links to our own site. They come with all sorts of issues: harder to develop, harder to test, harder to migrate domains (e.g. from hr-robocon.org to robocon.uk).
They seem to have potential to cause a great deal of annoyance... but I know it must be possible to do something else! Your change adds some relative URLs and we already have some.
I'm not going to stop you- there are already links in the places you edited that use the absolute url -but I'd strongly recommend that we instead look at this closer (is it, for example, that we're using links in angle brackets rather than standard markdown links or a-tags?)
Let me know what you want to do 😄
Ok, I'll have a look at trying to fix this later this week, but I could do with merging this PR so the presentation is available to teams that have requested it and dates are correct. Pls could you allow me to merge, but leave the branch alone so I can keep editing after merging?
Hot off the press and ready for publishing! Note that after you follow the link to the presentation in the kickoff blog post, you'll get a 404. If you paste the
/kickoff-2024-presentation.pdf
into the url to emulate what it would do, you won't get that error. It's just because the link includes the live url which obviously doesn't have this file yet.