Skip to content

(SP: 1) [Frontend] Add Go, GraphQL, NestJS, and NuxtJS category icons and styles#454

Merged
ViktorSvertoka merged 1 commit into
developfrom
feat/add-go-graphql-nestjs-nuxtjs-categories
Jul 18, 2026
Merged

(SP: 1) [Frontend] Add Go, GraphQL, NestJS, and NuxtJS category icons and styles#454
ViktorSvertoka merged 1 commit into
developfrom
feat/add-go-graphql-nestjs-nuxtjs-categories

Conversation

@ViktorSvertoka

@ViktorSvertoka ViktorSvertoka commented Jul 18, 2026

Copy link
Copy Markdown
Member

Summary

  • add Go, GraphQL, NestJS, and NuxtJS SVG icons
  • register all four categories in categoryRegistry
  • add brand-aligned accent, hover, active, and glow styles
  • derive category style keys directly from the shared registry
  • preserve the existing categoryStyles API for current consumers

Changes

  • added Go category with #00ADD8 accent
  • added GraphQL category with #E434AA accent
  • added NestJS category with #DF234F accent
  • added NuxtJS category with #00C58E accent
  • changed categoryTabStyles typing from a partial map to a complete registry-driven record

Validation

  • SVG validation passed
  • ESLint passed
  • Q&A category tests passed: 2/2
  • git diff validation passed
  • full TypeScript check remains blocked by pre-existing errors in unrelated blog, quiz, and Q&A tests

Database Changes

  • no schema migration required
  • category records are generated through the existing category registry and seeding flow

Checklist

  • Code has been self-reviewed
  • Existing category style APIs remain compatible
  • New SVG files are valid
  • Relevant tests pass
  • Scope is limited to category icons and styles

#453

Summary by CodeRabbit

  • New Features
    • Added category options for Go, GraphQL, NestJS, and Nuxt.js.
    • Added matching icons, display ordering, and interactive styling for the new categories.
  • Improvements
    • Improved category styling consistency and completeness across the category navigation.
    • Preserved fallback styling for unrecognized categories.

@ViktorSvertoka ViktorSvertoka self-assigned this Jul 18, 2026
@ViktorSvertoka ViktorSvertoka added the enhancement New feature or request label Jul 18, 2026
@vercel

vercel Bot commented Jul 18, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated (UTC)
devlovers-net Ignored Ignored Jul 18, 2026 10:31am

Request Review

@coderabbitai

coderabbitai Bot commented Jul 18, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 814bebb5-0269-4bee-8c28-5f8af1da728c

📥 Commits

Reviewing files that changed from the base of the PR and between e758387 and 7d6483b.

⛔ Files ignored due to path filters (4)
  • frontend/public/icons/go.svg is excluded by !**/*.svg
  • frontend/public/icons/graphql.svg is excluded by !**/*.svg
  • frontend/public/icons/nestjs.svg is excluded by !**/*.svg
  • frontend/public/icons/nuxtjs.svg is excluded by !**/*.svg
📒 Files selected for processing (2)
  • frontend/data/categoryRegistry.ts
  • frontend/data/categoryStyles.ts

📝 Walkthrough

Walkthrough

The category registry now includes Go, GraphQL, NestJS, and NuxtJS. Category style typing derives slugs from registry entries and requires a complete style record while preserving fallback lookup behavior.

Changes

Category system

Layer / File(s) Summary
Registry entries and style contract
frontend/data/categoryRegistry.ts, frontend/data/categoryStyles.ts
Adds Go, GraphQL, NestJS, and NuxtJS registry entries with ordering, icons, and styles; derives CategorySlug from registry entries and changes categoryTabStyles to a complete Record.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related issues

Possibly related PRs

Suggested labels: UI, content

Suggested reviewers: am1007, lesiaukr, liudmylasovetovs

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly describes the main frontend change: adding Go, GraphQL, NestJS, and NuxtJS category icons and styles.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/add-go-graphql-nestjs-nuxtjs-categories

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

Comment @coderabbitai help to get the list of available commands.

@ViktorSvertoka
ViktorSvertoka merged commit 3ef9887 into develop Jul 18, 2026
7 of 8 checks passed
@ViktorSvertoka
ViktorSvertoka deleted the feat/add-go-graphql-nestjs-nuxtjs-categories branch July 18, 2026 10:41
ViktorSvertoka added a commit that referenced this pull request Jul 18, 2026
* fix(homepage): guard blog category load (#452)

- prevent optional blog category navigation data from crashing the localized homepage layout when database access fails
- normalize the homepage site URL before building canonical and alternate metadata links

* feat(categories): add Go, GraphQL, NestJS, and NuxtJS icons and styles (#454)

* chore(release): bump frontend to v1.0.13 and update changelog (#456)

---------

Co-authored-by: Oleksandr <82455382+OleksandrMrn@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant