chore: updated personal works pages

[hwakabh]

Issue/PR link

N/A

What does this PR do?

Describe what changes you make in your branch:

• fixed url of waseda-mochida, regarding domain migration to CloudFlare
• added mosaiqued works

(Optional) Additional Contexts

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

• e2e testings are not included in this PR, since this requires merge into main to confirm changes would be applied

Summary by CodeRabbit

• New Features

  • Introduced a new work entry titled "mosaiqued," highlighting a dynamic mosaic art generator built with modern technologies.

• Updates

  • Modified the URL of an existing work entry to simplify its address, ensuring a more streamlined user experience.

[coderabbitai]

Walkthrough

This pull request makes updates to the API server fixtures within the works.json5 file. It removes the "www" subdomain from the "waseda-mochida" entry URL and adds a new entry for "mosaiqued" that contains its title, URL, description, and a list of tech stacks.

Changes

File Path	Change Summary
api-server/.../works.json5	Updated the "waseda-mochida" URL by removing the "www" subdomain and added a new "mosaiqued" entry with title, URL, description, and tech stacks.

Possibly related PRs

• feat: updated portfolios. #472: Involves modifications to the "waseda-mochida" entry URL and related tech stack adjustments in the works.json5 file.
• chore: updated docs and links #458: Focuses on updates within the works.json5 file, aligning with the changes made in this pull request.

Suggested labels

app(api), app/ui)

---

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)

api-server/fixtures/payloads/works.json5 (1)

65-65: Consider using a custom domain for the Cloud Run service.

The URL contains a project number (1037550336239) which could be considered sensitive information. Consider using a custom domain instead.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 103a5c6 and 2760860.

📒 Files selected for processing (1)

• api-server/fixtures/payloads/works.json5 (2 hunks)

🔇 Additional comments (3)

api-server/fixtures/payloads/works.json5 (3)

66-66: Consider adding the GitHub repository URL if the project is open source.

The GitHub repository URL is empty. If this is an open-source project, adding the repository URL would help users explore the implementation details.

---

63-75: LGTM on the new project entry!

The new mosaiqued project entry is well-structured with appropriate tech stack for a mosaic art generator. The JSON5 format is maintained correctly.

---

42-42: Verify the updated domain is accessible.

The URL change from www.waseda-mochida.com to waseda-mochida.com aligns with the CloudFlare migration mentioned in the PR objectives.

✅ Verification successful

🏁 Script executed:

#!/bin/bash
# Check if the new domain is accessible and properly redirected
curl -I -L https://waseda-mochida.com

Length of output: 1025

---

Domain accessibility confirmed.
The updated URL "https://waseda-mochida.com" returns an HTTP/2 200 response, confirming that the domain update is working as intended for the CloudFlare migration.