Skip to content

Conversation

@hwakabh
Copy link
Owner

@hwakabh hwakabh commented Jul 28, 2025

Issue/PR link

N/A

What does this PR do?

Describe what changes you make in your branch:

  • made tidy with CSS for rendering the page properly
  • added scrollBehavior() to vue-router for displaying page properly in navigations

(Optional) Additional Contexts

Describe additional information for reviewers (i.e. What does not included)

  • Still we need to develop backend APIs and replace frontends for rendering/fetching actual blog post via Backend.

Summary by CodeRabbit

  • New Features

    • Introduced a new internal blog page accessible via the "/blog" route, featuring examples of text formatting, headings, blockquotes, code blocks, and lists.
  • Improvements

    • Updated navigation to direct users to the new internal blog page instead of an external blog link.
    • Enhanced routing behavior so that page scroll position is restored or reset to the top during navigation.
  • Removals

    • Removed the Help page that previously showcased various UI elements and style guide examples.

@coderabbitai
Copy link

coderabbitai bot commented Jul 28, 2025

Walkthrough

This change updates the blog navigation in the Vue frontend by switching the About page's blog link from an external Tumblr URL to an internal router-link targeting a new "/blog" route. It introduces a new static Blog.vue page, removes the Help.vue page, and updates the router configuration to reflect these changes, including scroll behavior.

Changes

Cohort / File(s) Change Summary
About page blog link update
web-frontend/src/pages/About.vue
Changes the blog link from an external Tumblr URL to an internal Vue router-link pointing to "/blog". The external link is commented out and the internal router-link is uncommented.
New blog page
web-frontend/src/pages/Blog.vue
Adds a new static Blog.vue component demonstrating various HTML elements and text formatting, serving as the internal blog page.
Help page removal
web-frontend/src/pages/Help.vue
Deletes the Help.vue component, which previously served as a static style guide and UI demonstration page.
Router updates
web-frontend/src/router/index.js
Replaces the "/help" route with a new "/blog" route pointing to Blog.vue, reformats route definitions, and adds a scrollBehavior function for navigation.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

  • feat: frontend enhancement #584: Modifies the About.vue blog link (but in the opposite direction, from internal to external) and involves related routing changes for the blog page.

Suggested labels

app(ui), app(api)

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch feat/blogs

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
🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests 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.

@hwakabh hwakabh changed the title feat: enabled routes to blog page with styles and navications feat: enabled routes to blog page with styles and navigations Jul 28, 2025
@github-actions github-actions bot added the app(ui) Issue or PR related to frontend UI label Jul 28, 2025
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
web-frontend/src/pages/About.vue (1)

89-91: Consider content alignment with "Blog" label.

The technical implementation is correct - the router-link properly navigates to the new "/blog" route with consistent styling. However, the new Blog.vue page appears to be a static elements showcase rather than actual blog content. Consider either:

  1. Renaming the link to better reflect the content (e.g., "Style Guide" or "Elements")
  2. Planning to replace the static content with actual blog posts in the future

The TODO comment suggests future Tumblr integration, which would align better with the "Blog" label.

web-frontend/src/pages/Blog.vue (1)

1-4: Consider semantic HTML structure and naming consistency.

The template structure is valid, but consider these improvements:

  1. Semantic HTML: Add <main> or <article> tags around the content for better accessibility
  2. Naming consistency: The file is named "Blog.vue" but the heading reads "Elements" - this appears to be a style guide rather than a blog
 <template>
-  <section class="wrapper fullscreen">
+  <main class="wrapper fullscreen">
     <div class="inner">
-      <h1 class="major">Elements</h1>
+      <h1 class="major">Style Guide</h1>
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between da22d25 and 245ac56.

⛔ Files ignored due to path filters (1)
  • web-frontend/package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (4)
  • web-frontend/src/pages/About.vue (1 hunks)
  • web-frontend/src/pages/Blog.vue (1 hunks)
  • web-frontend/src/pages/Help.vue (0 hunks)
  • web-frontend/src/router/index.js (1 hunks)
💤 Files with no reviewable changes (1)
  • web-frontend/src/pages/Help.vue
🔇 Additional comments (5)
web-frontend/src/router/index.js (3)

7-7: LGTM: Blog component import added correctly.

The import statement follows the established pattern and correctly references the new Blog.vue component.


10-14: LGTM: Route definitions are clean and consistent.

The single-line format for route objects improves readability and maintains consistency. The new "/blog" route is properly configured to use the Blog component.


20-26: LGTM: Scroll behavior implementation enhances UX.

The scrollBehavior function correctly handles scroll restoration:

  • Preserves scroll position when navigating back/forward via savedPosition
  • Defaults to top of page for new navigation
  • Implementation follows Vue Router best practices
web-frontend/src/pages/Blog.vue (2)

5-29: LGTM: Well-structured content demonstrations.

The text formatting examples, headings hierarchy, blockquote, and preformatted code block are all properly implemented. The content effectively demonstrates various HTML elements and text styling options.


31-63: LGTM: Comprehensive list examples with responsive layout.

The lists section effectively demonstrates different list types using a responsive grid layout. The use of framework CSS classes (col-4, col-12-medium) ensures proper responsive behavior.

@hwakabh hwakabh merged commit 0d60aea into main Jul 28, 2025
10 checks passed
@hwakabh hwakabh deleted the feat/blogs branch July 28, 2025 07:47
@coderabbitai coderabbitai bot mentioned this pull request Aug 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

app(ui) Issue or PR related to frontend UI

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants