remove guidance pages.

[DilwoarH]

This is served by main website

#933

Preview Link

https://submit-pr-915.herokuapp.com/

What type of PR is this? (check all applicable)

• Refactor
• Feature
• Bug Fix
• Optimization
• Documentation Update

Description

Remove guidance pages, as we no longer need this.

Summary by CodeRabbit

Summary by CodeRabbit

• Documentation
  • Removed legacy guidance pages and help content that previously provided planning and housing data instructions.
• Chores
  • Streamlined navigation by eliminating outdated guidance sections, resulting in a cleaner and more focused user interface.

[coderabbitai]

Walkthrough

The pull request removes the guidance navigation feature entirely. This involves deleting the guidanceNavigation section from the configuration files and its associated schema definitions. In addition, several Markdown guidance files have been removed from the views. The changes eliminate previously available guidance content and related routing schema entries, leaving only the remaining configurations and templates intact.

Changes

File(s)	Change Summary
config/default.yaml, config/util.js	Removed the guidanceNavigation configuration and its schema definition from the overall configuration.
src/routes/schemas.js	Removed exported guidance entities (GuidanceNavigationItem, GuidanceNavigation) and deleted corresponding template schema entries referencing guidance navigation.
src/views/guidance/...	Deleted multiple guidance Markdown files (e.g. index.md, keep-your-data-up-to-date.md, publish-data-on-your-website.md, and several files under specifications/), thereby removing the guidance documentation.

Possibly related PRs

• add dataset action section #652: Involves related removal of the guidanceNavigation property in configuration and schema updates.
• Redirect guidance pages to main website #693: Contains modifications that remove functions associated with guidance navigation, aligning with these changes.
• 572 move guidance pages into submit service #613: Directly related as it introduces a new guidanceNavigation section in the configuration and adjusts related schemas.

Suggested reviewers

• GeorgeGoodall-GovUk
• rosado

Poem

I'm a clever bunny, light of paw,
Hopping through config, without a flaw.
Guidance paths have left the scene,
Making our code fresh and lean.
With swift hops and ASCII cheer,
I celebrate clean code all year! 🐇

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f47073f and cfc034e.

📒 Files selected for processing (1)

• config/default.yaml (0 hunks)

💤 Files with no reviewable changes (1)

• config/default.yaml

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: run-tests / test

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• 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

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	65.91%	5199 / 7887
🔵	Statements	65.91%	5199 / 7887
🔵	Functions	64.26%	232 / 361
🔵	Branches	80.79%	715 / 885

File Coverage

File	Stmts	Branches	Functions	Lines	Uncovered Lines
Changed Files
config/util.js	93.49%	80%	100%	93.49%	123-130
src/routes/schemas.js	100%	100%	100%	100%

Generated in workflow #873 for commit cfc034e by the Vitest Coverage Report Action