without the dropdown to the old sections

disable temporary javascript part

…script

Co-authored-by: Samuel Dionne-Riel <samuel@dionne-riel.com>

LESS compiles out // comments, but keeps /**/ comments.

The /**/ comments are mainly used, here, to keep license attributions.

By prefixing `&` we can make styles in a namespace apply according to
external selectors.

Here `html.with-js &` makes is so that when the selector is expanded,
`&` is replaced with the parent selector (`.collapse`), so it ends up
being `html.with-js .collapse`.

This does have one caveat. The previous implementation would keep the
"un-enabled" variant for any collapse not already converted if the code
ended up stopping due to a crash. This is not something that we should
concern ourselves with, as if it crashes there's more to worry about.

Ideally we'll prefer implementing a generalized behaviour instead of
page-specific JS. But when it's needed, put it at the end so the file is
easier to go through.

Maybe we should invest some time into figuring out a palatable "packer"
for the JavaScript bits? Probably to be looked at later when we choose
the new tooling for the website.

This is because changing the wording of a section will keep deep links
working.

Additionally, I find the generated anchors quite unwieldy.

Using `$("<a />")` is perfectly fine. Even `$("<a class='something' />").
But the moment we want to include variable content, prefer using `.attr`
rather than hoping the content will not destroy our string's HTML.

Sure, we control the DOM, and *it shouldn't happen*. But as we're making
this generic enough, we can make it right at the same time.

Furthermore, this, in my opinion, removes the cognitive load of reading
the escaped and concatenated string. (This is why the double quotes were
replaced with single quotes).

This, coupled with the next change,  reduces confusion when mentally
mapping the model of the collapse.

We don't *really* care about titles, we care about the articles.

This is basically a useless diversion at this point in time, but when
we need to refer to the article in the future, we're already using the
article instead of targeting deeply for its title.

They are the headers, and not outright links. They will be wrapped in
links, though.

(See also the previous commit.)

Since `.wrap()` continues the pipeline returning the original selected
set, this didn't work as expected.

With RSCSS, "modifier" class names are prefixed with a dash.

I had to re-think about all of it before it made sense before the
comments. Not that it's badly done, but this sure will help the next one
who'll read this.

This is helping a bunch with understanding what is going on. Otherwise
`-selected` becomes quite overloaded between the "collapsible" behaviour
and the "selection" behaviour of the tabs-like navigation.

This fixes issues with collapse and passing *through* viewport widths.

The reason is that the activation logic, on load, depended entirely on
which view the site was viewed as!

With this, we instead rely on the behaviour that activating *all* links
is a safe activity.

This helps with synchronization issues by *completely ignoring* actually
synchronizing the elements.

So the behaviour now synchronizes its view *and* the other view in
different manners, depending on what is desired UX-wise.

Read the amended comments in the less file, as it describes the new
behaviour.