[Feature]: Decide whether this fork should own and publish its own docs

[YassineElbouchaibi]

Problem or motivation

This fork includes its own docs source in /docs, but the repo still points users to Loft-hosted devpod.sh docs from README.md.

The issue is that the Loft-hosted docs are unmaintained, so users may be sent to stale documentation that does not reflect this fork.

Proposed solution

I’d like to start the discussion on whether this fork should move away from Loft-hosted docs and treat its in-repo docs as the canonical source.

If the answer is yes, a follow-up could:

• update README links away from devpod.sh
• update docs/docusaurus.config.js and branding
• publish and maintain docs for this fork independently

Alternatives considered

N/A

Area

• Documentation
• Other

Acceptance criteria

• Users are not directed to unmaintained Loft-hosted docs for this fork
• This project has one clear canonical docs location

Additional context

Relevant files:

• README.md
• docs/docusaurus.config.js

[skevetter]

This is a good proposal. To avoid confusion, I intend to release this project under a different name. Once released, the documentation will make it clear that this is a standalone project.