MyVideoGameList/myvideogamelist.com
MyVideoGameList/myvideogamelist.com
Watch
3
0
Fork
You've already forked myvideogamelist.com
 0
Code Issues 33 Pull requests 3 Projects 2 Releases Activity Actions

Improve visibility of bold Markdown in game descriptions #927

New issue
Closed
opened 2026-08-10 06:46:22 -05:00 by Veilor · 2 comments
Veilor commented 2026-08-10 06:46:22 -05:00
Member
Copy link

Bold Markdown in game descriptions currently has insufficient visual emphasis according to the reported behavior.

The change belongs at the game-description rendering and presentation layer, with regression coverage for the rendered output.

Scope

  • Game description Markdown rendering in the relevant Blade view under resources/views/
  • Typography styles affecting rendered game-description emphasis under resources/css/
  • Focused feature coverage under tests/Feature/ for game-description rendering

Acceptance Criteria

  • Bold Markdown in a game description is visibly distinguishable from surrounding regular text.
  • Regular game-description text retains its existing appearance and readability.
  • Other supported game-description Markdown formatting continues to render correctly.
  • A focused automated test verifies the bold game-description behavior.

Test Coverage Required

  • Add or update a focused feature test for rendering bold Markdown in a game description.
  • Run the existing relevant game-description feature tests and the full test suite according to repository conventions.

Progress Checklist

  • Locate the game-description Blade rendering path and its associated typography styles.
  • Increase the visual emphasis of rendered bold text within game descriptions using the existing styling approach.
  • Add focused regression coverage for bold Markdown rendering.
  • Review adjacent Markdown formatting behavior for regressions.
Bold Markdown in game descriptions currently has insufficient visual emphasis according to the reported behavior. The change belongs at the game-description rendering and presentation layer, with regression coverage for the rendered output. ## Scope - Game description Markdown rendering in the relevant Blade view under resources/views/ - Typography styles affecting rendered game-description emphasis under resources/css/ - Focused feature coverage under tests/Feature/ for game-description rendering ## Acceptance Criteria - Bold Markdown in a game description is visibly distinguishable from surrounding regular text. - Regular game-description text retains its existing appearance and readability. - Other supported game-description Markdown formatting continues to render correctly. - A focused automated test verifies the bold game-description behavior. ## Test Coverage Required - Add or update a focused feature test for rendering bold Markdown in a game description. - Run the existing relevant game-description feature tests and the full test suite according to repository conventions. ## Progress Checklist - [x] Locate the game-description Blade rendering path and its associated typography styles. - [x] Increase the visual emphasis of rendered bold text within game descriptions using the existing styling approach. - [x] Add focused regression coverage for bold Markdown rendering. - [x] Review adjacent Markdown formatting behavior for regressions.
Codex changed title from Making text bold should be more visible to Improve visibility of bold Markdown in game descriptions 2026-08-11 18:10:27 -05:00
Codex self-assigned this 2026-10-28 12:04:45 -05:00
Codex commented 2026-10-28 13:40:15 -05:00
Member
Copy link

Implemented and merged in PR #1003 (master revision e2bdbd33).

Game descriptions now apply an explicit weight of 700 to Markdown bold text, including links nested inside bold text. The bold-link override matters because the existing link utility otherwise lowers the rendered weight to 500. Regular text, ordinary links, link colors, spacing, italics, and list styling retain their existing behavior; Markdown sanitization is unchanged. Tailwind generates the scoped typography rules from the Blade utilities, so no custom CSS rule is needed.

Regression coverage checks bold and bold, links inside bold, bold inside links, adjacent text/italics/lists, raw-script stripping, and unsafe-link rejection. All 18 game-profile tests passed. The full PHP suite passed with 1,453 passed and 2 skipped using a 512 MB limit; existing duplicate-constant warnings remain unrelated to this change. Pint, PHPStan, the frontend build, and diff checks passed. Chromium verified the rendered Blade wrapper with compiled assets at desktop/mobile widths in light/dark themes: bold weight 700, regular text 300, ordinary links 500, no overflow or relevant console errors. Remote fonts were excluded from those browser checks.

All four progress checklist items are complete. Deployment requires the updated Blade template and rebuilt Vite CSS/manifest; no migrations or dependency changes are needed. Dev and production deployment verification will follow separately.

Implemented and merged in PR #1003 (master revision e2bdbd33). Game descriptions now apply an explicit weight of 700 to Markdown bold text, including links nested inside bold text. The bold-link override matters because the existing link utility otherwise lowers the rendered weight to 500. Regular text, ordinary links, link colors, spacing, italics, and list styling retain their existing behavior; Markdown sanitization is unchanged. Tailwind generates the scoped typography rules from the Blade utilities, so no custom CSS rule is needed. Regression coverage checks **bold** and __bold__, links inside bold, bold inside links, adjacent text/italics/lists, raw-script stripping, and unsafe-link rejection. All 18 game-profile tests passed. The full PHP suite passed with 1,453 passed and 2 skipped using a 512 MB limit; existing duplicate-constant warnings remain unrelated to this change. Pint, PHPStan, the frontend build, and diff checks passed. Chromium verified the rendered Blade wrapper with compiled assets at desktop/mobile widths in light/dark themes: bold weight 700, regular text 300, ordinary links 500, no overflow or relevant console errors. Remote fonts were excluded from those browser checks. All four progress checklist items are complete. Deployment requires the updated Blade template and rebuilt Vite CSS/manifest; no migrations or dependency changes are needed. Dev and production deployment verification will follow separately.
Codex commented 2026-10-28 13:41:26 -05:00
Member
Copy link

Deployed PR #1003 to dev and production from merged master revision e2bdbd333ff34ee05e6f16b7c20412760b658eda.

The scoped release installed the updated game-description Blade template and rebuilt Vite manifest/assets, refreshed Blade caches, verified installed and publicly served asset checksums, and preserved 450 unrelated runtime/configuration/dependency files on each environment. Both environments passed description rendering checks for both bold syntaxes and nested bold links. Live homepage and game-profile checks returned HTTP 200, and both pages reference the current assets.

No migrations, dependency installations, environment changes, or domain-data writes were performed. Release manifests record the scoped update as ee6b2847+issue992-3d129125+pr1000-c0341df2+pr1001-7d34d5ab+pr1002-f264f6b6+pr1003-e2bdbd33.

Rollback backups contain the original files, checksums, and deployment receipts:

  • Dev: /home/mvgldev/deploy-backups/pr1003-e2bdbd33-xyhpik15
  • Production: /home/mvgl/deploy-backups/pr1003-e2bdbd33-fxwhjyey

All checklist items remain checked; the issue is closed with status/done.

Deployed PR #1003 to dev and production from merged master revision `e2bdbd333ff34ee05e6f16b7c20412760b658eda`. The scoped release installed the updated game-description Blade template and rebuilt Vite manifest/assets, refreshed Blade caches, verified installed and publicly served asset checksums, and preserved 450 unrelated runtime/configuration/dependency files on each environment. Both environments passed description rendering checks for both bold syntaxes and nested bold links. Live homepage and game-profile checks returned HTTP 200, and both pages reference the current assets. No migrations, dependency installations, environment changes, or domain-data writes were performed. Release manifests record the scoped update as `ee6b2847+issue992-3d129125+pr1000-c0341df2+pr1001-7d34d5ab+pr1002-f264f6b6+pr1003-e2bdbd33`. Rollback backups contain the original files, checksums, and deployment receipts: - Dev: `/home/mvgldev/deploy-backups/pr1003-e2bdbd33-xyhpik15` - Production: `/home/mvgl/deploy-backups/pr1003-e2bdbd33-fxwhjyey` All checklist items remain checked; the issue is closed with `status/done`.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
codex/issue-1014-verified-gamer-entries
renovate/npm/master/laravel-vite-plugin-3.2.1
renovate/npm/master/concurrently-10.0.7
dev
No results found.
Labels
Clear labels   
automated

   
code-quality

   
component: admin dashboard
The issue is related to the admin dashboard functionality.

  
component: backend
The issue is related to the backend code.

  
component: billing
The issue is related to our billing and payment system functionality.

  
component: content management
The issue is related to site content and moderation functionality.

  
component: faqs
The issue relates to our frequency asked questions and their categories.

  
component: game genres
The issue is related to genres in relation to games.

  
component: game lists
The issue is related to user-facing game list functionality.

  
component: game reviews
The issue relates to the game reviews functionality.

  
component: game search
The issue is related to the user-facing game search functionality.

  
component: games
The issue relates to games in our database.

  
component: internal notifications
The issue is related to the functionality of notifications sent for internal usage.

  
component: platforms
The issue is related to platform functionality.

  
component: security
The issue relates to the security issues within the app.

  
component: tests
The issue relates to unit and feature tests.

  
component: user api
The issue relates to the user-facing API.

  
component: user badges
The issue is related to our badge/achievements functionality.

  
component: user blogs
The issue is related to blogging functionality.

  
component: user consoles
The issue is related to user console lists functionality.

  
component: user favorites
This is issue is related to the favorites functionality.

  
component: user friends
The issue relates to the friending functionality.

  
component: user notifications
The issue is related to user-facing notifications functionality.

  
component: user profiles
The issue is related to user profile functionality.

  
component: user site notifications
The issue relates to the functionality of notifications shown to users directly on the website.

  
component: user wishlists
This issue is related to the wishlists functionality.

  
component: web design
This issue is related to the design of the website.

  
dependencies
Pull requests that update a dependency file.

  
javascript
Pull requests that update Javascript code

  
php
Pull requests that update PHP code.

  
priority
high
 The issue is considered a high priority.

  
priority
low
 This issue is considered a low priority.

  
priority
medium
 This issue is considered a medium priority.

  
security-hotspot

   
source: codex

   
source: sonarqube
  
status
awaiting feedback
 The issue is awaiting feedback from others.

  
status
backlog
 Issues that are in a backlog status.

  
status
done
 The issue has been completed and closed out.

  
status
in progress
 The issue is in progress and being actively worked on.

  
status
in queue
 The issue is in queue and will be worked on shortly.

  
status
in review
 The issue work has been completed and now the work needs to be reviewed.

  
status
needs codex review
 Use this tag to have Codex spiffy up your issue.

  
status
needs investigation
 The issue describes a problem which needs further investigation.

  
status
wontfix
 This issue will not be worked on.

  
type: bug
The issue describes something working the way it wasn't intended too.

  
type: documentation
Improvements or additions to site documentation.

  
type: feature
A new feature for the website.

  
type: improvement
An improvement on an existing feature.

  
type: regression
The issue describes a function that previously worked and no longer does.

  
type: task
A small-ish task.

No labels
automated
code-quality
component: admin dashboard
component: backend
component: billing
component: content management
component: faqs
component: game genres
component: game lists
component: game reviews
component: game search
component: games
component: internal notifications
component: platforms
component: security
component: tests
component: user api
component: user badges
component: user blogs
component: user consoles
component: user favorites
component: user friends
component: user notifications
component: user profiles
component: user site notifications
component: user wishlists
component: web design
dependencies
javascript
php
priority
high
priority
low
priority
medium
security-hotspot
source: codex
source: sonarqube
status
awaiting feedback
status
backlog
status
done
status
in progress
status
in queue
status
in review
status
needs codex review
status
needs investigation
status
wontfix
type: bug
type: documentation
type: feature
type: improvement
type: regression
type: task
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
New Features - Part 1
Assignees
Clear assignees
No assignees
Codex
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MyVideoGameList/myvideogamelist.com#927
No description provided.