feat: delete unused components and redirect directly to /docs

[andostronaut]

This is an automated pull request for branch develop

Summary by CodeRabbit

• Configuration

  • Added permanent redirect from root URL to /docs

• Component Removals

  • Removed Footer component
  • Removed Header component
  • Removed Theme Provider
  • Removed Theme Toggle component

• Page Changes

  • Simplified home page layout, removing most content and user-facing elements

[coderabbitai]

Walkthrough

This pull request involves a significant simplification of the project's frontend structure. The changes primarily focus on removing several key components such as Footer, Header, ThemeProvider, and ToggleTheme. The next.config.mjs file has been updated to include a new redirect configuration that automatically routes the root URL to the /docs path. The index.tsx page has been stripped down, removing most of its previous content and layout components.

Changes

File	Change Summary
next.config.mjs	Added async redirects() function to redirect root URL ('/') to /docs
src/components/footer.tsx, src/components/header.tsx, src/components/theme-provider.tsx, src/components/toogle-theme.tsx	Completely removed the Footer, Header, ThemeProvider, and ToggleTheme components
src/pages/index.tsx	Simplified page structure, removed Header and Footer components

Sequence Diagram

sequenceDiagram
    participant User
    participant Next.js Router
    participant Docs Page

    User->>Next.js Router: Access root URL ('/')
    Next.js Router->>Docs Page: Permanent Redirect
    Docs Page-->>User: Render Documentation Page

Loading

Possibly related PRs

• feat: delete unused files and make ui more clean #66: Removal of Footer component, related to the simplification of the UI.
• feat: remove unused deps #67: Removal of unused dependencies that may relate to the overall structure of the application.
• docs: update drowser doc #70: Modifications in src/pages/index.tsx regarding the structure and layout of the page.
• docs: update code usage #71: Changes to the documentation in src/pages/docs/drowser.mdx, impacting the overall documentation structure.
• feat: update umami src and data web id #74: Updates to the src/pages/index.tsx file, relevant to the modifications made in the main PR.

Poem

🐰 Hop, hop, away we go!
Components stripped, no more to show
Redirects dance, pages bare
A minimalist's flair with rabbit's care
Simplicity reigns, clean and bright 🌟

---

📜 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 637b79d and e1d4ca5.

📒 Files selected for processing (1)

• src/pages/index.tsx (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• src/pages/index.tsx

---

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. (Beta)
• @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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

next.config.mjs (1)

10-18: Consider removing the async keyword if not needed
Since the redirects() function here merely returns a static array, the async keyword may not be necessary. If there is no asynchronous processing, you can simplify the code to a regular function for better readability.

-async redirects() {
+redirects() {
   return [
     {
       source: '/',
       destination: '/docs',
       permanent: true
     }
   ]
 }

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 135a5bd and 637b79d.

📒 Files selected for processing (6)

• next.config.mjs (1 hunks)
• src/components/footer.tsx (0 hunks)
• src/components/header.tsx (0 hunks)
• src/components/theme-provider.tsx (0 hunks)
• src/components/toogle-theme.tsx (0 hunks)
• src/pages/index.tsx (0 hunks)

💤 Files with no reviewable changes (5)

• src/components/footer.tsx
• src/components/theme-provider.tsx
• src/pages/index.tsx
• src/components/header.tsx
• src/components/toogle-theme.tsx

🔇 Additional comments (1)

next.config.mjs (1)

13-15: Validate permanent: true for SEO considerations
Declaring permanent: true typically results in a 308 redirect status code. Verify that this is the intended SEO behavior and that it aligns with how you want search engines to handle the root path.