Codeinwp / Codeinwp/neve

Add Google Sans to available Customizer typography fonts

Open
#4,500 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

customer report feature-request-triage
Dominant language
PHP
Stars
306
Forks
88
Avg merge
2d 16h
Merged PRs (30d)
12

Description

Impact: 30 · Confidence: 95 · Complexity: 10

Description

Problem:
The Neve customizer typography options currently lack the base "Google Sans" font, although variants like "Google Sans Code" and "Google Sans Flex" are available. Customers who wish to use this standard typography are blocked from doing so without resorting to custom font workarounds.

Desired Behavior:
"Google Sans" should be natively available within the typography dropdown in the Neve customizer, allowing users to easily select and apply it to their elements.

Acceptance Criteria:

  • Verify availability and licensing of "Google Sans" via the Google Fonts API.
  • Update the theme's bundled font definition list to include "Google Sans" so it appears in the customizer dropdown.
  • Verify the font correctly enqueues and renders on the frontend when active.
  • (If the font cannot be included due to proprietary licensing, the engineering team should close the issue with an explanation so support can relay the information).

Customer Context

The customer is on Lifetime Pro plans, has intermediate technical knowledge, and manages multiple sites. They want to use the "Google Sans" font natively from the customizer but noticed only its variants are available. They are requesting it be added to the built-in theme fonts.

Root Cause Analysis

The root cause is a gap in Neve's predefined list of selectable fonts. The customizer typography settings do not list "Google Sans", meaning the customer cannot select their desired typography natively and is forced to consider custom font integrations if they wish to proceed.

Reasoning

The customer is pointing out a gap in the theme's native font library: 'Google Sans' is missing from the typography dropdown, although its variants (Code and Flex) are present. While using a custom font module is a good support workaround, updating the native font list to include missing fonts (or syncing with the latest Google Fonts library) is a valid product enhancement.


Source: HelpScout #3323369891
Generated by feature-request-triage workflow (ID: feature-request-triage_6a070ad9941204.89001943)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the theme's bundled font definition list and checking the Google Fonts API for Google Sans availability and licensing. Add it only if licensing permits, then verify that it appears in the customizer typography dropdown and enqueues and renders on the frontend; otherwise document why it cannot be included.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.