Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

asset(article): Add Supervive Open Beta Blog Article #112

Merged
merged 2 commits into from
Nov 20, 2024

Conversation

infinia-yzl
Copy link
Owner

@infinia-yzl infinia-yzl commented Nov 20, 2024

Fixes: #111

Description

As per title.

Checklist:

  • My changes generate no new warnings or errors
  • I have verified that these changes don't negatively impact performance
  • Also optimized for mobile layouts

Additional context

Also fixes OG Site Name & OG URL.

Summary by CodeRabbit

  • New Features

    • Introduced the "SUPERVIVE Tier List 2024" guide to assist players in selecting hunters based on skill levels and the game meta.
    • Sections tailored for both new players and competitive players, detailing hunter rankings and notable mentions.
    • Encouraged community engagement by inviting players to share their own tier lists.
  • Documentation

    • Added a comprehensive overview of game mechanics and features, enhancing player understanding of SUPERVIVE.
    • Improved metadata for blog posts, enhancing SEO and social media integration.

Copy link

vercel bot commented Nov 20, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
opentierboy ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 20, 2024 7:56am

Copy link

coderabbitai bot commented Nov 20, 2024

Walkthrough

The pull request introduces a new file, supervive-open-beta-guide.md, which serves as a comprehensive tier list for hunters in the game SUPERVIVE, coinciding with its Open Beta phase in 2024. The document is structured to assist both new and competitive players in selecting hunters based on their skill levels and the current game meta. It features sections for different player demographics, outlines criteria for ranking hunters, and encourages community engagement through tier list creation.

Changes

File Change Summary
articles/supervive-open-beta-guide.md New file created with a tier list for hunters, including sections for new players and competitive players, criteria for ranking, and community engagement elements.
components/BlogPost.tsx Modifications to enhance metadata structure, including new fields in openGraph and twitter objects, and a new alternates object for SEO.

Assessment against linked issues

Objective Addressed Explanation
Add Supervive Open Beta Blog Article (#111)

Possibly related PRs

Poem

In the realm of SUPERVIVE, we take our stand,
With hunters ranked, all skill levels planned.
New players rejoice, and tryhards too,
A tier list awaits, just for you!
Join the fun, share your list,
In this Open Beta, none can resist! 🐇✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 8d8d60f and c592370.

📒 Files selected for processing (1)
  • components/BlogPost.tsx (1 hunks)
🔇 Additional comments (2)
components/BlogPost.tsx (2)

73-74: Verify image path handling for the new blog article.

Since this PR adds a new blog article with an ogImage at /blog/sv-ob/sv-ob-blog-cover.webp, let's ensure the path handling is correct.

Run the following script to verify the image path structure:

✅ Verification successful

Let me gather more information about the image handling in the codebase.


Based on the gathered information, I can now provide the final response:

Image path handling appears consistent and correct

The verification shows:

  • The new blog article correctly references its ogImage at /blog/sv-ob/sv-ob-blog-cover.webp
  • Other blog posts follow the same pattern with webp images under /blog/ directory
  • The path structure is consistent across articles, with subdirectories for related assets
  • The BlogPost component supports image metadata, with the site's default ogImage being a PNG
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify image path handling and existence

# Check if the blog article references the correct image path
rg -l "ogImage.*sv-ob-blog-cover\.webp" articles/

# Check if other blog posts use consistent image path patterns
rg "ogImage:.*" articles/

# Verify image format support in metadata
rg "\.(webp|png|jpg|jpeg)" components/BlogPost.tsx

Length of output: 501


Script:

#!/bin/bash
# Check image handling in the Next.js configuration and other relevant files
rg -A 3 "images?" next.config.js

# Check if there are any image processing utilities or components
fd -e tsx -e ts -x rg -l "Image.*from.*next/image"

# Look for any image-related configurations or constants
rg -l "imageConfig|IMAGE_CONFIG" 

# Check for any image path construction or URL handling
ast-grep --pattern 'const $_ = `${$_}/blog/${$_}`'

Length of output: 413


73-74: LGTM! Enhanced metadata implementation follows best practices.

The additions of siteName and url improve OpenGraph metadata completeness. The fallback image configuration and canonical URL implementation are solid improvements for SEO.

Let's verify the OpenGraph metadata structure:

✅ Verification successful

Let me verify the metadata structure in the BlogPost.tsx component to ensure it aligns with the blog post frontmatter we found.


Let me check more of the metadata generation logic to see the complete structure.


Let me check if there's more to the metadata structure, particularly the image handling that was mentioned.


OpenGraph metadata implementation is correctly structured and consistent with blog posts

The verification confirms that:

  • The metadata structure in BlogPost.tsx correctly maps to the frontmatter structure found in all blog posts
  • The OpenGraph implementation includes proper fallback images and dimensions
  • The URL structure and siteName are consistently applied
  • The metadata handling aligns with the frontmatter data from the markdown files
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify metadata structure in other blog posts for consistency

# Check if other blog posts follow similar metadata structure
fd -e md . articles/ --exec sh -c 'echo "=== {} ==="; head -n 20 {}'

Length of output: 3575


Script:

#!/bin/bash
# Check the complete metadata structure in BlogPost.tsx
rg -A 10 "generateMetadata" components/BlogPost.tsx

Length of output: 396


Script:

#!/bin/bash
# Get the complete metadata generation logic
rg -B 5 -A 30 "generateMetadata" components/BlogPost.tsx

Length of output: 1165


Script:

#!/bin/bash
# Get more context about the metadata structure, particularly image handling
rg -B 10 -A 20 "siteName: 'OpenTierBoy'" components/BlogPost.tsx

Length of output: 867


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
🪧 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 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.

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: 1

🧹 Outside diff range and nitpick comments (5)
articles/supervive-open-beta-guide.md (5)

11-12: Consider adding the X post reference link here

You mention the official team's post on X, but the link appears only in the references section. Consider adding the link here for immediate context.

-As SUPERVIVE enters Open Beta, the official team shared creators' hunter tier lists on X. Based on our playtesting
+As SUPERVIVE enters Open Beta, the [official team shared creators' hunter tier lists on X](https://x.com/playSUPERVIVE/status/1859010458277331162). Based on our playtesting

28-32: Consider extracting the tier list URL as a constant

The tier list URL is quite long and appears twice in the article. Consider extracting it to a constant at the top of the file for better maintainability.

---
title: SUPERVIVE Tier List 2024 - Best Hunters for Open Beta
description: Complete SUPERVIVE hunter tier lists for Open Beta 2024. Discover the best hunters for beginners and competitive play based on current meta performance.
date: 2024-04-20
tags: [ supervive, play-supervive, theorycraft-games, tier-list, open-beta, opentierboy, hunter, hunters, meta, competitive, beginner, tryhard, tier-maker, ranking, guide, tips, tricks, best, top, strongest, weakest, opinion ]
ogImage: "/blog/sv-ob/sv-ob-blog-cover.webp"
+beginnerTierListUrl: "https://www.opentierboy.com/rank/supervive/hunter?state=N4IgLglgpgTgziAXAbVBJ5owLQIDQgB2GAyiAWEqiOojQLYCGA5lLgK4AOsAbhD2zgALANYA6AO5QARpxABfPGgwQmrDtxh8B2KIUaSZcxcrqqWgrr35shcQodkKlNFWsubtbZnDCPjALomrnSQsNiM5EQYAIJRlCimDBYa1joAZgA2AB7+zknm6nBWWjbYAF5QnHnBtMlFJV7YAMaZcDUudYUeaWwAVuyZNUGdGGE40lHEdABC8VQF7qmlOvQAnn5STrVuKcWeZSKcDlvGo2ZL+73Y0sLDO6FYLVMYAMLziSH1PStsAPaMTZGfJfbrLJrSGBDU4KEZJcbYdIvOgAMQ+1C6l0aZR4fwAJh1FntsTphDxCaCsQcdH0ICdgfI4V92IRmoCoMw-jAIJU8ciQOiggEKBAwJkoKQAKoABQAogAlABqAElFbKAATYdUACRZYFgcHV6S56pmsoA4sqAHJWhVkeRAA"
+tryharderTierListUrl: "https://www.opentierboy.com/rank/supervive/hunter?state=N4IgLglgpgTgziAXAbVBJ5owLQIDQgB2GAyiAWEqiOojQLYCGA5lLgK4AOsAbhD2yiFGAOgDuUAEacQAXzxoMEJqw7cYfAbgAWAa3FSZ8xXWUs2cLr35ttcQgelyFNJSotWNN7MzhhHRgC6xq50kLDYjOREGACC0ZQoJgzmatZaAGYANgAeAc7JZqqW6ppsAF5QnPkhtCnFnmXYAMZZcDUudUUepd4AVuxZNcGdGOE4ktHEdABCCVSF7mleWvQAnv4STrVuqSXpbLqcDltGo6ZL+ytsknDawzthWC1TGADC80mh9T0H2AD2jE2hgK326yyakhgQ1OchGyXG2AyrzoADFPtQupdGt4eP8ACYdRZ7HFaO48Ilg7G9LR9CAnEGyeHfdiEZpAqDMf4wCCVfEokAY4KBCgQMBZKCkACqAAUAKIAJQAagBJJVygAE2A1AAlWWBYHANRluRqZnKAOIqgBy1sVZFkQA"
---

63-64: Improve sentence variety

The word "probably" is used repetitively. Consider rephrasing to add variety to the writing.

-**Elluna** is probably one of the weaker picks in this category due to other hunters being able to outperform her in
+**Elluna** tends to be one of the weaker picks in this category due to other hunters being able to outperform her in
🧰 Tools
🪛 LanguageTool

[style] ~63-~63: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...e to his skill-ceiling. - Elluna is probably one of the weaker picks in this categor...

(REP_PROBABLY)


84-84: Consider using a period instead of exclamation mark

The exclamation mark after the Steam link feels unnecessary and could be replaced with a period for a more professional tone.

-Ready to try it yourself? Check it out on [Steam](https://store.steampowered.com/app/1283700/SUPERVIVE/)!
+Ready to try it yourself? Check it out on [Steam](https://store.steampowered.com/app/1283700/SUPERVIVE/).
🧰 Tools
🪛 LanguageTool

[style] ~84-~84: Using many exclamation marks might seem excessive (in this case: 5 exclamation marks for a text that’s 2836 characters long)
Context: ...steampowered.com/app/1283700/SUPERVIVE/)! ## Reference - [Official Supervive po...

(EN_EXCESSIVE_EXCLAMATION)


90-91: Fix grammar and maintain consistent emphasis style

There are two style issues to address:

  1. Add a hyphen between "based" and "personal"
  2. Use underscores consistently for emphasis instead of asterisks
-*These tier lists reflect our subjective opinions based personal experience while playing SUPERVIVE. The meta is still
-developing, and balance changes may affect hunter performance.*
+_These tier lists reflect our subjective opinions based-personal experience while playing SUPERVIVE. The meta is still
+developing, and balance changes may affect hunter performance._
🧰 Tools
🪛 LanguageTool

[uncategorized] ~90-~90: This expression is usually spelled with a hyphen.
Context: ...These tier lists reflect our subjective opinions based personal experience while playing SUPER...

(BASED_HYPHEN)

🪛 Markdownlint

90-90: Expected: underscore; Actual: asterisk
Emphasis style

(MD049, emphasis-style)


91-91: Expected: underscore; Actual: asterisk
Emphasis style

(MD049, emphasis-style)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 3c056b4 and 8d8d60f.

📒 Files selected for processing (1)
  • articles/supervive-open-beta-guide.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
articles/supervive-open-beta-guide.md

[style] ~63-~63: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...e to his skill-ceiling. - Elluna is probably one of the weaker picks in this categor...

(REP_PROBABLY)


[style] ~84-~84: Using many exclamation marks might seem excessive (in this case: 5 exclamation marks for a text that’s 2836 characters long)
Context: ...steampowered.com/app/1283700/SUPERVIVE/)! ## Reference - [Official Supervive po...

(EN_EXCESSIVE_EXCLAMATION)


[uncategorized] ~90-~90: This expression is usually spelled with a hyphen.
Context: ...These tier lists reflect our subjective opinions based personal experience while playing SUPER...

(BASED_HYPHEN)

🪛 Markdownlint
articles/supervive-open-beta-guide.md

90-90: Expected: underscore; Actual: asterisk
Emphasis style

(MD049, emphasis-style)


91-91: Expected: underscore; Actual: asterisk
Emphasis style

(MD049, emphasis-style)

articles/supervive-open-beta-guide.md Show resolved Hide resolved
@infinia-yzl infinia-yzl merged commit 66618e8 into main Nov 20, 2024
7 checks passed
@infinia-yzl infinia-yzl deleted the opentierboy-111 branch November 20, 2024 08:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add Supervive Open Beta Blog Article
1 participant