GitLab

Which is about to be deleted from main

The Panfrost docs are now upstream in the Mesa docs, so we can link
directly there instead of via a redirect.

The subdir of the pages-domain used for serving up exposed artifacts
doesn't seem to support serving up index.html by default for a folder.
So let's instead disable pretty-URLs, so we at least get links that
work.

Erik Faye-Lund authored Nov 11, 2021 and Erik Faye-Lund committed Nov 16, 2021

Ideally, this would have worked better when using ugly-URLs, but it
doesn't. But it still seems better to do this than hard-coding, even if
it doesn't do what we want.

Erik Faye-Lund authored Nov 11, 2021 and Erik Faye-Lund committed Nov 16, 2021

This works better when we enable ugly URLs.

This makes links like stylesheets etc match where they get served up for
exposed artifacts, rendering things a bit more correctly.

The "Read more" buttons in the "Featured APIs" section used to be put at
some constant spacing after the description-text. This doesn't look very
nice when two APIs line up where the text differs enough in length to
cause the "Read more" buttons to not line up.

This uses the "display: flex" related utilities from Bootstrap to make
the "Read more" buttons align to the bottom of the div, which makes the
buttons line up. This leads to some reduction in visual noise when
skimming the page.

Erik Faye-Lund authored Oct 11, 2021 and Erik Faye-Lund committed Oct 13, 2021

It's not legal to place a div directly inside a dl-tag. Let's move it
outside instead.

This matches the behavior before dropping to use the Bootstrap jumbotron
component.

Now that Bootstrap has released the v5 series, let's upgrade.

Some noticable changes:
- A bit wider max-size for the main container, which is nice for bigger
  screens. This is due to the introduction of the xxl breakpoint.
- The dark navbar is a bit darker than before. This is a part of a
  general refresh of the Bootstrap palette. If wanted, we could avoid
  using the built-in colors and pick ourselves. But it's easier to just
  stick to the default, so that's what I'm doing for now ;)
- No more jQuery usage. This should save a nice amount of bandwidth.
Acked-by: Eric Engestrom <eric@engestrom.ch>

Erik Faye-Lund authored Jun 29, 2021 and Erik Faye-Lund committed Aug 12, 2021

Bootstrap 5 has some regressions in how it renders horizontal rules. See
this upstream ticket for details:

https://github.com/twbs/bootstrap/issues/34374



While this is being fixed, let's work around this on our own end.
Acked-by: Eric Engestrom <eric@engestrom.ch>

Bootstrap has removed the jumbotron-component from Bootstrap 5, so let's
implement our own instead.
Acked-by: Eric Engestrom <eric@engestrom.ch>

In commit d8b10296 ("footer: use h6 instead of strong"), I opted for a
bit more semantical HTML, but it seems that dropping the strong-tag here
had an unexpected side-effect; the boldness might have just been a bit
less on my system, but it seems on other systems it's a *lot* less bold.
In fact, not bold at all.

It turns out, this depends on the fonts installed on the system, and
Bootstrap uses a default font-weight of 500 for headings. This looks
fine most places, but in the footer here, we *really* want the headings
to stand out from the rest.

So let's add back some boldness. By doing this in the CSS instead, we
get to keep the semanticness of the HTML without having to sacrifice the
look. The value of 600 was picked by a bit of trial-and-error; both
systems I have where this doesn't render well as-is is fixed at 550 and
above, but let's bump it a bit more to be sure.

The columns look a bit confusing when they're not either fully
horizontal or fully vertical. So let's change this so they stack
horizontally on wide displays, and vertically on narrow displays.

The VMWare SVGA driver is a layered driver just like the others here, so
let's add it to the list.
Reviewed-by: Charmaine Lee <charmainel@vmware.com>
Reviewed-by: Jose Fonseca <jfonseca@vmware.com>

We're currently YOLOing the margins and padding around main pretty badly,
leading to slight inconsistencies between the different page-types.

This makes it consistent; we now have a margin of 3 (which is bootstrap
for 1rem) around all main-tags. To render more or less the same, we need
to make some page-specific adjustments, like reducing a jumbotron-margin
on the home-page.

The only functional change should be the margin at the bottom of the
404-page, which is not smaller, like on other pages. It seems better to
be consistent here.

This makes the headings a bit semantically stronger, but slightly
changes the styling; we now get some spacing under the headings, and
they're a bit less heavy.

Instead of setting the color everywhere just to avoid setting the color
on the headers, set the colors on the headers, and make links in the
footer inherit the color setting.

While we're at it, set the color to text-dark instead of text-body
(which is the default). This just decreases the contrast here ever so
slightly, to give these heading a tiny bit less emphasis. The difference
is almost impossible to see, but it makes a bit more semantic sense.

This isn't a list, so let's not use a list for it. It's just two
independent items, and it makes the hard-coded padding a bit less
awkward by turning them into paragraphs.

We never align these next to each other, because they're not in a
row-tag to start with. And that's fine, but these col-tags makes no
sense this way. So let's just remove them.

We don't really need to specify col-12 for this one, as it doesn't do
anyhing funky, it's just another div at the end.

But while we're at it, move it out of the row, because otherwise it'll
be a bit too large, due to negative margins. This makes this look a bit
less oddly sized compared to the rest of the content.