feat: Migrate development/assistant guide from v8 to v9 with klarspråk

[Ildest]

Innhold

Migrerer development/assistant-veiledningen fra v8 til v9 med fullstendig klarspråk-vask.

Filer lagt til

• content/altinn-studio/v9/new-from-v8/development/assistant/_index.nb.md
  • Migrated from v8 guides/development/assistant
  • Full klarspråk revision:
    • ✅ Eliminert s-passiv: "ville bli behandlet" → "kan vi behandle"
    • ✅ Endret til du-perspektiv: "Vi anbefaler å" → "Vi anbefaler at du bruker"
    • ✅ Fjernet substantiveringer: "går over til behandling" → "skal gå over til å behandle"
    • ✅ Forbedret naturlig språk: "samt" → "og også", "Etterpå" → "Etter betaperioden"
    • ✅ Produktnavn rettelse: "altinn-studio-repoet" → "Altinn Studio-repoet"
  • Lenke til v8 branching-guide (v9 versjon ikke migrert ennå)

Filer endret

• themes/hugo-theme-altinn/layouts/partials/header.html
  • Produktnavn: 'altinn-studio' → 'Altinn Studio'
  • Version alert: 'pre-release' → 'under utvikling' (mer naturlig norsk)

Testing

• Lenke til localhost: http://localhost:1313/nb/altinn-studio/v9/new-from-v8/development/assistant/
• Alle lenker fungerer (branching-link peker til v8)
• Infoboks viser rett tekst

Tags: development, assistant, klarspråk, v8-to-v9-migration

[coderabbitai]

Warning

Review limit reached

@Ildest, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 17 minutes

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 8fb4b1da-85cd-4f91-9752-aa3cbb23c8cb

📥 Commits

Reviewing files that changed from the base of the PR and between f9bec57 and b417b8e.

📒 Files selected for processing (2)

• content/altinn-studio/v9/new-from-v8/development/assistant/_index.nb.md
• themes/hugo-theme-altinn/layouts/partials/header.html

---

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.}

[nkylstad]

Denne ser fin ut, jeg tenker vi kan flytte den direkte til f.eks.
`content/altinn-studio/v9/getting-started/ai/assistant

[nkylstad]

Bør (enn så lenge) ha med draft: true i front matter.

Suggested change

	tags: [needsReview]
	tags: [needsReview]
	draft: true