Dome
9f92958651
This commit introduces a complete internal refactoring of the theme architecture, transitioning from a monolithic functions.php structure to a modular, scalable system. ### Key Changes #### 1. Modular Architecture - Extracted core logic into dedicated modules under `/inc/` - Introduced clear separation of concerns: - `helpers/` → shared utility functions - `performance/` → optimization and media processing logic - `customizer/` → fully modularized Customizer structure - `template-*` → presentation and template-related logic #### 2. Customizer Refactor - Replaced legacy monolithic customizer with modular system: - `core.php` → base setup - `general.php`, `layout.php`, `toc.php`, `social.php` → feature-based modules - Improved maintainability and extensibility for future settings #### 3. Performance Layer Separation - Moved performance-related logic into `/inc/performance/` - Clearly separated: - frontend performance tweaks (scripts, CSS, cleanup) - media optimization tools (batch processing, cleanup UI) - Reduced coupling between UI, logic, and processing #### 4. Media Optimization Pipeline Stabilization - Re-aligned upload pipeline with WordPress native flow - Restored proper use of `wp_generate_attachment_metadata` - Ensured compatibility with: - format conversion (AVIF/WebP) - responsive image generation - WordPress core image handling #### 5. Cleaner Hook Management - Removed duplicated hooks and redundant filters - Standardized hook priorities and responsibilities - Ensured consistent use of feature toggles (`get_theme_mod`) #### 6. Improved Code Quality - Reduced function duplication - Standardized naming conventions - Improved readability and inline documentation - Removed legacy patterns and implicit dependencies #### 7. Asset Handling Improvements - Introduced centralized asset versioning via `filemtime` - Improved script loading strategy (defer non-critical JS) - Cleaner enqueue structure for styles and scripts #### 8. Foundation for Future Development This refactor lays the groundwork for: - easier feature expansion - better testability - improved debugging capabilities - long-term maintainability ### Breaking Changes - Internal file structure has changed significantly - Direct modifications to old functions.php logic may no longer apply - Customizer extensions must now hook into modular structure --- This is a purely structural and architectural release. No intentional changes to frontend behavior were introduced, but the internal system is now significantly more robust and maintainable.
55 lines
1.3 KiB
PHP
55 lines
1.3 KiB
PHP
<?php
|
|
/**
|
|
* Layout / Container Settings
|
|
*
|
|
* @package zeitfresser
|
|
*/
|
|
|
|
add_action( 'customize_register', 'zeitfresser_layout_options' );
|
|
|
|
function zeitfresser_layout_options( $wp_customize ) {
|
|
|
|
/**
|
|
* Container Width
|
|
*/
|
|
$wp_customize->add_setting(
|
|
'container_width',
|
|
array(
|
|
'default' => 1400,
|
|
'sanitize_callback' => 'absint',
|
|
)
|
|
);
|
|
|
|
$wp_customize->add_control(
|
|
'container_width',
|
|
array(
|
|
'type' => 'number',
|
|
'section' => 'ztfr_general',
|
|
'label' => esc_html__( 'Container Width', 'zeitfresser' ),
|
|
'description' => esc_html__( 'Maximum width of the content container in pixels.', 'zeitfresser' ),
|
|
'priority' => 10,
|
|
'input_attrs' => array(
|
|
'min' => 800,
|
|
'max' => 2000,
|
|
'step' => 10,
|
|
),
|
|
)
|
|
);
|
|
}
|
|
|
|
/**
|
|
* Apply container width via CSS variable
|
|
*/
|
|
add_action( 'wp_head', 'zeitfresser_container_width_dynamic_css' );
|
|
|
|
function zeitfresser_container_width_dynamic_css() {
|
|
|
|
$container_width = (int) get_theme_mod( 'container_width' );
|
|
|
|
if ( $container_width <= 0 ) {
|
|
$container_width = 1140;
|
|
}
|
|
|
|
echo '<style>:root{--container-width:' . esc_attr( $container_width ) . 'px;}</style>';
|
|
}
|