Chore/studio getting started structure

[nkylstad]

Switched some folders in getting-started for a more task-based setup

Summary by CodeRabbit

• Documentation
  • Expanded getting-started guides with new sections for user creation, development tasks, service maintenance, organization administration, and API integration.
  • Added introduction page for development guides.
  • Reorganized documentation structure for improved navigation flow.
  • Updated section titles for clarity.

[coderabbitai]

Note

.coderabbit.yaml has unrecognized properties

CodeRabbit is using all valid settings from your configuration. Unrecognized properties (listed below) have been ignored and may indicate typos or deprecated fields that can be removed.

⚠️ Parsing warnings (1)

Validation error: Unrecognized key(s) in object: 'auto_resolve_threads'

⚙️ Configuration instructions

• Please see the configuration documentation for more information.
• You can also validate your configuration using the online YAML validator.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

📝 Walkthrough

Walkthrough

The changes reorganize and expand the Altinn Studio getting-started documentation by introducing five new role-specific guidance sections (user creation, service development, maintenance, organization administration, and platform integration), while adjusting navigation weights and refining page titles for better content hierarchy.

Changes

Cohort / File(s)	Summary
Documentation Index Expansion content/altinn-studio/v10/getting-started/_index.nb.md	Introduces five new role-focused guidance sections with checklist items and reference links for user creation, service development, operations management, organizational administration, and platform integration.
Navigation Weight & Metadata Updates content/altinn-studio/v10/getting-started/create-user/_index.nb.md, content/altinn-studio/v10/getting-started/development/test/_index.nb.md, content/altinn-studio/v10/getting-started/receive-data/_index.nb.md	Adjusts navigation weights (create-user: 10→1, test: 30→20, receive-data: 50→20) and refines page title (receive-data: "Motta data via API"→"Motta data") for improved content hierarchy and navigation order.
New Development Guide Page content/altinn-studio/v10/getting-started/development/_index.nb.md	Creates new introductory documentation page for development guides with standard front matter (title, weight, draft status) and references to development concepts with child page rendering.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Poem

📚 Five pathways bloom within the guide,
Where users, builders, keepers reside,
With weights reordered, titles refined,
A clearer journey for each kind. ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Chore/studio getting started structure' accurately reflects the main change: reorganizing the getting-started documentation structure for a more task-based setup.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/studio-getting-started-structure

📝 Coding Plan

• Generate coding plan for human review comments

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Tip

You can get early access to new features in CodeRabbit.

Enable the early_access setting to enable early access features such as new models, tools, and more.

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@content/altinn-studio/v10/getting-started/_index.nb.md`:
- Line 10: Replace all empty markdown link targets `[]()` in this document (e.g.
the entry starting with "[Følg denne veiledningen for å komme i gang]()") with
the correct URLs or explicit TODO placeholders; update each `[]()` instance to
either the known target URL now or a clear "[TODO: add link]" target so the
overview page becomes navigable, and ensure you handle the other occurrences of
empty links elsewhere in the file consistently.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 157962c0-b4e0-425e-bebf-9ebc832d87be

📥 Commits

Reviewing files that changed from the base of the PR and between 6f3f22f and f433493.

⛔ Files ignored due to path filters (16)

• content/altinn-studio/v10/getting-started/development/basic-form/build-version.mp4 is excluded by !**/*.mp4
• content/altinn-studio/v10/getting-started/development/basic-form/create-form.mp4 is excluded by !**/*.mp4
• content/altinn-studio/v10/getting-started/development/basic-form/create-service.mp4 is excluded by !**/*.mp4
• content/altinn-studio/v10/getting-started/development/basic-form/policy-rules.mp4 is excluded by !**/*.mp4
• content/altinn-studio/v10/getting-started/development/basic-form/publish-version.mp4 is excluded by !**/*.mp4
• content/altinn-studio/v10/getting-started/development/basic-form/reset-local-changes.mp4 is excluded by !**/*.mp4
• content/altinn-studio/v10/getting-started/development/basic-form/save-changes.mp4 is excluded by !**/*.mp4
• content/altinn-studio/v10/getting-started/development/basic-form/set-service-name.mp4 is excluded by !**/*.mp4
• content/altinn-studio/v10/getting-started/development/test/local-dev/changes-validated.png is excluded by !**/*.png
• content/altinn-studio/v10/getting-started/development/test/local-dev/commit-message.png is excluded by !**/*.png
• content/altinn-studio/v10/getting-started/development/test/local-dev/copy-repo-link.png is excluded by !**/*.png
• content/altinn-studio/v10/getting-started/development/test/local-dev/find-app-in-dashboard.png is excluded by !**/*.png
• content/altinn-studio/v10/getting-started/development/test/local-dev/pull-successful.png is excluded by !**/*.png
• content/altinn-studio/v10/getting-started/development/test/local-dev/push-successful.png is excluded by !**/*.png
• content/altinn-studio/v10/getting-started/development/test/local-dev/toolbar-hent.png is excluded by !**/*.png
• content/altinn-studio/v10/getting-started/development/test/local-dev/toolbar-last-opp.png is excluded by !**/*.png

📒 Files selected for processing (12)

• content/altinn-studio/v10/getting-started/_index.nb.md
• content/altinn-studio/v10/getting-started/create-user/_index.nb.md
• content/altinn-studio/v10/getting-started/development/_index.nb.md
• content/altinn-studio/v10/getting-started/development/basic-form/_index.nb.md
• content/altinn-studio/v10/getting-started/development/custom-development/_index.nb.md
• content/altinn-studio/v10/getting-started/development/test/_index.nb.md
• content/altinn-studio/v10/getting-started/development/test/local-dev/_index.en.md
• content/altinn-studio/v10/getting-started/development/test/local-dev/_index.nb.md
• content/altinn-studio/v10/getting-started/development/test/local-dev/analysis/_index.nb.md
• content/altinn-studio/v10/getting-started/development/test/local-dev/analysis/rules/ALTINNAPP0500/_index.en.md
• content/altinn-studio/v10/getting-started/development/test/local-dev/analysis/rules/ALTINNAPP0500/_index.nb.md
• content/altinn-studio/v10/getting-started/receive-data/_index.nb.md