docs: make getting started a real grading workflow

[ArthurCRodrigues]

Summary

• replace docs-first getting started page with a true first grading run
• guide users through API startup, config creation, submission, and result retrieval
• move MkDocs authoring instructions to a dedicated docs contributor guide
• update MkDocs nav labels accordingly

Validation

• python scripts/validate_docs.py
• mkdocs build --strict

[ArthurCRodrigues]

OK

[Copilot]

Pull request overview

This PR updates the documentation “Getting Started” flow to walk users through a real end-to-end grading run (API start → config creation → submission → result retrieval), while moving MkDocs authoring instructions into a dedicated contributor guide.

Changes:

• Replaced the previous “Local Docs Development” getting-started page with a first grading workflow quickstart.
• Added a new “Docs Site Development (MkDocs)” guide for documentation contributors.
• Updated MkDocs navigation labels/entries to reflect the new doc structure.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 4 comments.

File	Description
mkdocs.yml	Updates the MkDocs nav to surface the new getting-started workflow and adds the docs contributor guide to Guides.
docs/guides/docs-site-development.md	New contributor-focused guide for running/building the docs site locally.
docs/getting-started/mkdocs-local-development.md	Rewritten into a full first grading workflow quickstart (API/config/submission/results).

[Copilot]

The guide points to the API running on http://localhost:8080, but the Docker Compose service exposes port 8000 (docker-compose.yml maps 8000:8000 and healthcheck hits localhost:8000). This will cause the example curl commands to fail unless the user manually remaps ports. Please update the URLs/port throughout this page (or explicitly document how to configure the port).

[Copilot]

setup_config is shown as a flat object with required_files/setup_commands, but the runtime pre-flight code expects setup_config to be keyed by language (e.g., { "python": { "required_files": [...], "setup_commands": [...] } }). With the current example shape, the pre-flight step will not enforce main.py or run setup commands because it won’t find the language key.

Suggested change

	"required_files": ["main.py"],
	"setup_commands": []
	"python": {
	"required_files": ["main.py"],
	"setup_commands": []
	}

[Copilot]

In Markdown, the <submission_id> placeholder in the URL will be treated as an HTML tag and may not render as visible text. Use a non-angle-bracket placeholder (e.g., {submission_id} / SUBMISSION_ID) or escape the angle brackets so users can copy/paste the command correctly.

Suggested change

	curl http://localhost:8080/api/v1/submissions/<submission_id>
	curl http://localhost:8080/api/v1/submissions/{submission_id}

[Copilot]

This page is now a grading-workflow quickstart, but the underlying filename/path is still getting-started/mkdocs-local-development.md, which is misleading for future maintenance and linkability. Consider renaming the markdown file/path to match the new topic (and update the nav entry accordingly).