Remove SPA GitHub Pages script from index.html

[choidabom]

What this PR does / why we need it?

This PR removes the single-page application (SPA) GitHub Pages script from the index.html file. This change is necessary to simplify the setup for the project and eliminate any potential conflicts or confusion caused by the unused script.

Any background context you want to provide?

The SPA script was previously included but has not been utilized in the current project implementation. Removing it will help streamline the codebase and ensure that only the necessary components are included.

What are the relevant tickets?

Fixes #

Checklist

• Added relevant tests or not required
• Didn't break anything

Summary by CodeRabbit

• Documentation

  • Updated the description of the application's static files in the project docs.

• Chores

  • Removed an outdated URL redirection mechanism for smoother navigation.
  • Eliminated a custom error handling page to streamline the user experience when a page isn’t found.

[coderabbitai]

Walkthrough

This pull request updates the frontend documentation and simplifies the SPA redirection logic. The README has a minor update in the public directory comment, removing the reference to index.html. Additionally, the redirection script in index.html has been removed, and the custom 404.html file designed for SPA routing on GitHub Pages has been deleted.

Changes

Files	Change Summary
frontend/README.md	Updated the public directory comment by removing reference to index.html from "Static files (index.html, images, etc.)".
frontend/index.html & frontend/public/404.html	Removed SPA URL redirection logic: deleted the redirection script in index.html and removed the custom 404.html page along with its redirection script.

Sequence Diagram(s)

Old SPA Redirection Flow

sequenceDiagram
    participant B as Browser
    participant I as index.html
    participant R as Redirection Script

    B->>I: Request SPA URL with query parameters
    I->>R: Detect redirection query string
    R->>B: Update URL via history API
    B->>I: Request updated URL content

Loading

New SPA Flow

sequenceDiagram
    participant B as Browser
    participant I as index.html

    B->>I: Request SPA URL (no redirection logic)
    I-->>B: Serve content directly

Loading

Possibly related PRs

• Fix typo in README and Contributing Guide #245: Updates the README file with correct file paths, which relates to the modifications in the frontend documentation in this PR.

Suggested reviewers

• hackerwins

Poem

I'm a rabbit with hops so bright,
Coding changes felt just right.
No redirection maze to confound,
Clean URLs happily abound.
I nibble bugs away with delight!
🐰✨

---

📜 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 db0bd94 and e338fd7.

📒 Files selected for processing (3)

• frontend/README.md (1 hunks)
• frontend/index.html (1 hunks)
• frontend/public/404.html (0 hunks)

💤 Files with no reviewable changes (1)

• frontend/public/404.html

✅ Files skipped from review due to trivial changes (1)

• frontend/README.md

🔇 Additional comments (1)

frontend/index.html (1)

1-24: LGTM! Clean removal of the SPA GitHub Pages script.

The removal of the unused SPA GitHub Pages script aligns with the PR objectives and helps simplify the codebase.

Please verify that the application's routing functionality is properly handled through an alternative mechanism. You can confirm this by:

1. Testing navigation through different routes
2. Checking that direct URL access works as expected
3. Ensuring browser refresh on any route works correctly

---

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.

[blurfx]

LGTM. Thanks for your contribution.