Description

I feel the Building a Native Executable page could use some rework to be more accessible to new users.

As an example, it leads with a long list of pre-requisites, which include "A working C development environment" - that surely looks intimidating to our target audience, and isn't actually the case since years.

Implementation ideas

I'm suggesting to lead with the super-simplified instructions which leverage container-based builds; this would just need a container engine as sole requirement, and a quick introductory example.

Keep the list of Prerequisites short and to the point - e.g. "An IDE" is not really required and seems to just add ammunition to the intimidation attempt.

We then follow this easy-starter with more details, including how to setup an environment for non-container builds.

Sections about Debugging native images, custom containers, compressed binaries, etc.. should belong on a different page - not least for better findability.