Kudos for this PR! I'm glad you're getting some experience with Tachyons CSS and this PR generally does a great job of addressing the underlying issue we're having with our landing page, plus you are fixing or improving several other things.

One request before I test this PR more thoroughly, related to these changes:

I changed the search's type to overlay
I had to remove the search box from the landing

Can we put the search box on the landing page back to where it was, please? This also entails staying away from overlay, for good reason.

I'll explain:

• Good, easy search is a big deal: We should aim for the front page to become more functional over time, not less, and that includes giving people the easiest access to our search possible, with the fewest clicks. I'd argue the searchbox is one of the most important features on this page — I use it myself all the time, for example ("I wonder what our docs say about x?" --> docs.validmind.ai --> type into search box). The workaround of telling people how to search from the front page isn't really a solution because you're replacing functionality with an explanation for how our docs UI works — there's an important clue right there.

  (In contrast, including more context in the search results via this PR is a positive change, very much in the right direction.)

• Let's avoid adding complexity (phrased positively: add simplicity): The only reason you've had to remove the search box is because of overlay, but I think there's a usability trap hidden in that option that prioritizes aesthetics over usability. As much as I like the look of overlay and tested it with our docs site before, you now need to click before you can see the searchbox, on every docs page, for every search. Every. single. time. An extra click every time you want to see the searchbox is a small usability anti-pattern with a big impact over time, and it's completely unnecessary since a better option is readily available and already in use on our docs site. That search box should always be visible to entice people to use it.

  (Wherever possible, we should simplify the experience, similar to how getting to our recommended QuickStart now takes two clicks instead of five.)

EDIT: Rewrote this to focus on the visibility of the search box, as technically it's one click to put the search box into focus vs one click to click the icon and bring up the search box. That said, I still prefer that the search box always be visible — maybe related to having worked for a search company for quite a few years — and losing the search box from the home page is not an acceptable cost to switching to overlay.

I wonder if we can use non-html buttons so we can use the good links everywhere, but so far I haven't figured it out.

Simplified HTML buttons for sure, non-HTML with better linking possibly — I did experiment with what's available during the initial training module development a bit.

We should be able to use basic rounded buttons but our Quarto styling gets in the way, as you can see in these examples:

<button class="{ white bg-pink br3 bn f2 pv2 ph3 mt5 mb5 }" onclick="window.location.href='https://app.prod.validmind.ai/'; return false;">Log in</button>

:::{.dib .white .bg-pink .br3 .bn .f2 .pv2 .ph3 .mt5 .mb5}
[Log in](https://app.prod.validmind.ai/)
:::

The reason Quarto looks different is that it's not really a button as ::: is the equivalent of a div. I'm inclined to say even the HTML button in this example would be an improvement over the much more complex buttons we use today. Or, we could use a slightly different button in Quarto that works well with our existing CSS styling if we can figure out the vertical text alignment.

LGTM! 🚀 I pushed a9dfc87 to fix a couple of issues:

• The developer & validator links were broken, fixed (index.qmd is already a level above guide/ so no need for the ../).
• The images were missing fig-alt text, might as well fix while I was reviewing.

My only other comment is that it feels like there is just a bit too much whitespace in the navbar now. E.g. on a 1440x900 laptop screen, it feels like we're conceding just a bit too much whitespace to the words that matter, to the point where it detracts from the reading experience. Up to you if you want to make any additional changes or leave as-is, though.

(Granted, I feel about whitespace in the context of words much the same way some people might feel about the libretto in opera — it's just an excuse for the music. Too little and it's not opera; too much and it gets in the way. :P )