Docs improvements?

[withinboredom]

Describe you feature request

Is your feature request related to a problem? Please describe.

I was shoulder-surfing a colleague today while I had them install frankenphp for a quick PHP server. There wasn't a clear way to download FrankenPHP, and they got a bit lost on frankenphp.dev.

Describe the solution you'd like

• Perhaps add a top-nav called "Download" that simply navigates to the latest release or getting-started page.
• On the getting started page, most of the above-the-fold is taken up by a logo, forcing the person to scroll quite a ways down the page to actually get started. The logo is nice, but huge.

Describe alternatives you've considered

This was just from shoulder-surfing a dev, it might be worth shoulder-surfing more devs.

[aszenz]

@withinboredom I think the docs should also clarify whether frankenphp can work with normal php + extensions installation.

To me their are four use cases of franken php that can be separately documented:

1. Replacement for php-fpm+nginx/caddy/apache, with host php+extensions untouched (not sure if this is supported)
2. Statically bundling php+extensions with webserver
3. Static binary for the whole app
4. Embedding php inside golang