120-skiplinks-b: Alternative render.

[sherakama]

@JBCSU @yvonnetangsu @josephgknox

How about something like this. With this approach, the twig template is usable directly in your work and the rendered output has the example we want.

Thoughts?

[yvonnetangsu]

@JBCSU @yvonnetangsu @josephgknox

How about something like this. With this approach, the twig template is usable directly in your work and the rendered output has the example we want.

Thoughts?

I do like this approach! Btw, I just noticed this now, should we make this singular "skiplink" so it's consistent with all the other components?

[yvonnetangsu]

I think the id is actually something like "main-content" instead of "skip-to-x". The json file was updated so this markup in the styleguide should probably reflect that too.

[josephgknox]

@sherakama this approach also works well for me. I'll merge this into the other branch. We can continue discussion there if needed.

@yvonnetangsu it's a good question regarding the component naming convention. I'd argue that this accessibility-related component might be OK to leave as plural, as the chances of this not skipping more than one link (used primarily for skipping navigation) is rare. Also, it appears to most commonly be referred to as Skiplinks on the inter-webs. Willing to discuss this more, too. I might be crazy. :)

[yvonnetangsu]

@josephgknox I'm comfortable going with the most commonly known term 😸 Thanks for checking!

[JBCSU]

@sherakama @josephgknox I just committed to this branch an alternative that I think works quite well. Please let me know what you think.