Theme settings configuration: First decide what should be made into global settings.
Practical theme setup guide for Shopify theme developers: the relationship between settings_schema.json and settings_data.json, the required fields for theme_info, return values for common setting types, the division of labor between global settings and section settings, and real-world pitfalls such as losing configurations when changing the ID.
I. Relationship between the two files
The `settings_schema.json` file is an array, where each element is a settings category object that must have two fields: `name` and `settings`.
II. Commonly Used Setting Types and Their Return Values
Before writing a schema, it's more important to understand what you're retrieving than to remember the type name—many bugs stem from treating objects as strings.
III. Retrieving values from the template
Each nullable setting must have a fallback branch. If the logo above is not set, it should return the store name text instead of rendering an empty `<a>`. When a merchant installs a new theme, all settings are at their default values; this path must be visible.
IV. What to include and what not to include in global settings
The last line deserves special mention: Custom information at the product level belongs to metafields, not theme settings. Theme settings are a single site-wide format, while there are thousands of products. Making "This product's care instructions" a theme setting is a structural error. See Metafields and MetaObjects.




