service nav component + non GET links/forms

[asmega]

Ideally all service nav links would be simple GET links. However in reality it's never like that. We have add a Sign out link which does a DELETE action. Ideally this would be an actually form that supports DELETE but at the moment is reliant on javascript which I've done with the following below so it at least functions

https://github.com/DFE-Digital/claim-additional-payments-for-teaching/pull/3914/files#r2185014026

Not really sure how we should support this? or whether it should even be supported at all?

[asmega]

Someone suggested an option to link to a page which then has a normal form submit that would then sign out as an option

[peteryates]

Ah interesting. I think adding a form to the mix is likely going to have an impact on usability, especially if the button is styled to look like a regular nav link.

Did you try using the start/end slot?

They allow any bits of HTML to be injected before/after the nav

govuk-components/app/components/govuk_component/service_navigation_component.rb

Lines 43 to 47 in a4f4f3e

	start_slot,
	tag.div(class: "#{brand}-service-navigation__container") do
	safe_join([service_name, navigation].compact)
	end,
	end_slot

The Design System guidance says:

The Service navigation includes the option to use ‘slots’ to insert custom HTML code at specific points inside the component. This helps you extend the component to add custom elements, such as language selectors.

You must provide your own styles and JavaScript code for the content within a slot, particularly if you’re not using an existing component. You’ll need to decide on the most appropriate layout and positioning.

I think this might be the best bet for adding a signout link/button.