Kevin Roche

It's been pointed out that we should perhaps include a bit in the overview section about our related projects, perhaps like this 

> I think the getting started & setting up kubestellar need to be restructured. Seems too lengthy and broken I absolutely agree. There have been many updates to that section...

@eaepstein Good points and I have incorporated them into a new draft.

For reference, the website may now be viewed *without* requiring local download and running of mkdocs by visiting one of the rendered staging copies: As of 12 June 2024, the...

> I was told that I should have written [#2183 (comment)](https://github.com/kubestellar/kubestellar/pull/2183#issuecomment-2164783157) here. A general design comment -- After designing many websites, and fielding the user complaints/confusion which arise, I have...

> @KPRoche: sure, adding some direct links into subsections is OK. I think we are agreed on the important point, which is that describing how to setup is logically part...

OK, I can indeed pull portions of the larger setup instruction files into a quickstart file, combined with additional interstitial text. I have a sample at https://kproche.github.io/kubestellar/doc-new-v2b/direct/get-started/ **IMPORTANT** I do...

@MikeSpreitzer regarding your comment in #2183 about the **User Guide** page under "Using KubeStellar" -- Would *Usage Notes* be an appropriate retitling of that page?

> "Usage Notes" sounds, to me, less comprehensive and organized than "User Guide" or "Using KubeStellar". While the current reality is indeed not comprehensive and not well organized, I think...

After conversations about potential applications for satellite workload deployment, security is an existing worry in that use case (people hacking satellite software), so not inadvertently leaving a backdoor by giving...