chore(docs): re-organize docs for docs website consumption

[brandtkeller]

Description

Attempt to set new docs organization for the lula-docs website.

Related Issue

Fixes #490

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Other (security config, docs update, etc)

Checklist before merging

• Test, docs, adr added or updated as needed
• Contributor Guide Steps followed

[netlify]

✅ Deploy Preview for lula-docs canceled.

Name	Link
🔨 Latest commit	75a5310
🔍 Latest deploy log	https://app.netlify.com/sites/lula-docs/deploys/667dcd6241ce650008c88494

[meganwolf0]

Is there a good example to look at for how the file/folder structure maps to the website UI?

[bdfinst]

Is there a good example to look at for how the file/folder structure maps to the website UI?

You can see an example here:
https://github.com/defenseunicorns/uds/tree/main/content/en

[meganwolf0]

I think this looks good, I have a few thoughts, but I know we don't really have the documentation to support yet so really just jotting down notes somewhere for discussion

• I think we need like a "what is lula/about" section that details more of the use cases and how to use Lula, perhaps a subsection we'd have "building a validation" or something similar. I'm thinking this could link to the other docs in oscal and references
• I think we probably need some more detailed information for the lula validation yaml, which could be an autodoc generated from the schema
• Wondering if we should repurpose the evaluate into like a quickstart with details on the validate command as well.

[brandtkeller]

I think this looks good, I have a few thoughts, but I know we don't really have the documentation to support yet so really just jotting down notes somewhere for discussion

• I think we need like a "what is lula/about" section that details more of the use cases and how to use Lula, perhaps a subsection we'd have "building a validation" or something similar. I'm thinking this could link to the other docs in oscal and references
• I think we probably need some more detailed information for the lula validation yaml, which could be an autodoc generated from the schema
• Wondering if we should repurpose the evaluate into like a quickstart with details on the validate command as well.

I completely agree - I believe we have more than a few efforts for documentation to support going forward. Let's get some structure in-place such that we can wire docs up to the website and iterate.