Stop hard-disabling WordPress Font Library for LT typography workflows

[georgeolaru]

Summary

Prepare LT themes for native WordPress font management so Fonto can become optional once Style Manager can consume core-registered fonts.

Why

A recent Felt LT support request asked for native WordPress font management, or at least a non-Fonto path, because the current setup feels unnecessarily plugin-heavy and fonts uploaded outside Fonto do not integrate with LT typography controls.

Current behavior

LT themes currently suppress the WordPress Font Library UI and related settings:

• theme.json sets settings.typography.fontFamilies to an empty list and fontLibrary to false.
• inc/block-editor.php forces $editor_settings['fontLibraryEnabled'] = false.
• Style Manager's block-editor integration also deregisters core font collections when SM font palettes are active.

That means LT themes block the native WordPress font workflow even before Style Manager has a chance to interoperate with it.

Requested outcome

Align Anima with a future Style Manager/core-font integration by removing theme-level blockers and defining the intended UX for LT themes.

Acceptance criteria

• LT users can manage custom fonts without installing Fonto.
• The editor does not expose duplicate or conflicting font UIs.
• LT typography settings still apply the selected font families consistently in the frontend and block editor.
• Theme defaults and theme.json settings match the supported product direction instead of disabling native font management unconditionally.
• The final UX is coordinated with the Style Manager work that adds support for core-registered fonts.

Implementation notes

Relevant code paths:

• theme.json
• inc/block-editor.php
• inc/integrations/style-manager/fonts.php

This issue should be coordinated with the companion pixelgrade/style-manager issue that adds a core font provider for SM controls.