[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$foil5qO2h-6RcW4Jl5D5akxK30qjYMxhZPSYyWUJJIvo":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":13,"num_ratings":14,"last_updated":15,"tested_up_to":16,"requires_at_least":17,"requires_php":18,"tags":19,"homepage":22,"download_link":23,"security_score":24,"vuln_count":25,"unpatched_count":25,"last_vuln_date":26,"fetched_at":27,"vulnerabilities":28,"developer":29,"crawl_stats":26,"alternatives":34,"analysis":90,"fingerprints":119},"syntaxhighlighter-evolved-yaml-brush","SyntaxHighlighter Evolved: Yaml Brush","1.0.1","tedivm","https:\u002F\u002Fprofiles.wordpress.org\u002Ftedivm\u002F","\u003Cp>Adds support for the Yaml language to the SyntaxHighlighter Evolved plugin.\u003C\u002Fp>\n","Adds support for the Yaml language to the SyntaxHighlighter Evolved plugin.",70,4113,100,2,"2014-10-14T22:29:00.000Z","4.8.28","2.7","",[20,21],"syntaxhighlighting","yaml","https:\u002F\u002Fgithub.com\u002Ftedivm\u002Fsyntaxhighlighter_yaml","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsyntaxhighlighter-evolved-yaml-brush.1.0.3.zip",85,0,null,"2026-03-15T15:16:48.613Z",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":30,"total_installs":11,"avg_security_score":24,"avg_patch_time_days":31,"trust_score":32,"computed_at":33},1,30,84,"2026-04-05T02:49:03.203Z",[35,57,71],{"slug":36,"name":37,"version":38,"author":39,"author_profile":40,"description":41,"short_description":42,"active_installs":43,"downloaded":44,"rating":11,"num_ratings":45,"last_updated":46,"tested_up_to":47,"requires_at_least":48,"requires_php":49,"tags":50,"homepage":55,"download_link":56,"security_score":13,"vuln_count":25,"unpatched_count":25,"last_vuln_date":26,"fetched_at":27},"jekyll-exporter","Static Site Exporter","3.1.1","Ben Balter","https:\u002F\u002Fprofiles.wordpress.org\u002Fbenbalter\u002F","\u003Ch3>Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Converts all posts, pages, and settings from WordPress to Markdown and YAML for use in Jekyll (or Hugo or any other Markdown and YAML based site engine)\u003C\u002Fli>\n\u003Cli>Export what your users see, not what the database stores (runs post content through \u003Ccode>the_content\u003C\u002Fcode> filter prior to export, allowing third-party plugins to modify the output)\u003C\u002Fli>\n\u003Cli>Converts all \u003Ccode>post_content\u003C\u002Fcode> to Markdown\u003C\u002Fli>\n\u003Cli>Converts all \u003Ccode>post_meta\u003C\u002Fcode> and fields within the \u003Ccode>wp_posts\u003C\u002Fcode> table to YAML front matter for parsing by Jekyll\u003C\u002Fli>\n\u003Cli>Generates a \u003Ccode>_config.yml\u003C\u002Fcode> with all settings in the \u003Ccode>wp_options\u003C\u002Fcode> table\u003C\u002Fli>\n\u003Cli>Outputs a single zip file with \u003Ccode>_config.yml\u003C\u002Fcode>, pages, and \u003Ccode>_posts\u003C\u002Fcode> folder containing \u003Ccode>.md\u003C\u002Fcode> files for each post in the proper Jekyll naming convention\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Selective export\u003C\u002Fstrong>: Export only specific categories, tags, or post types using WP-CLI\u003C\u002Fli>\n\u003Cli>No settings. Just a single click.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Usage\u003C\u002Fh3>\n\u003Col>\n\u003Cli>Place plugin in \u003Ccode>\u002Fwp-content\u002Fplugins\u002F\u003C\u002Fcode> folder\u003C\u002Fli>\n\u003Cli>Activate plugin in WordPress dashboard\u003C\u002Fli>\n\u003Cli>Select \u003Ccode>Export to Jekyll\u003C\u002Fcode> from the \u003Ccode>Tools\u003C\u002Fcode> menu\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>More information\u003C\u002Fh3>\n\u003Cp>See \u003Ca href=\"https:\u002F\u002Fben.balter.com\u002Fwordpress-to-jekyll-exporter\" rel=\"nofollow ugc\">the full documentation\u003C\u002Fa>:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fben.balter.com\u002Fwordpress-to-jekyll-exporter\u002F.\u002Fdocs\u002Fchangelog\u002F\" rel=\"nofollow ugc\">Changelog\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fben.balter.com\u002Fwordpress-to-jekyll-exporter\u002F.\u002Fdocs\u002Fcommand-line-usage\u002F\" rel=\"nofollow ugc\">Command-line-usage\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fben.balter.com\u002Fwordpress-to-jekyll-exporter\u002F.\u002Fdocs\u002Fselective-export\u002F\" rel=\"nofollow ugc\">Selective export by category or tag\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fben.balter.com\u002Fwordpress-to-jekyll-exporter\u002F.\u002Fdocs\u002Fcustom-post-types\u002F\" rel=\"nofollow ugc\">Custom post types\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fben.balter.com\u002Fwordpress-to-jekyll-exporter\u002F.\u002Fdocs\u002Fcustom-fields\u002F\" rel=\"nofollow ugc\">Custom fields\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fben.balter.com\u002Fwordpress-to-jekyll-exporter\u002F.\u002Fdocs\u002Fdeveloping-locally\u002F\" rel=\"nofollow ugc\">Developing locally\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fben.balter.com\u002Fwordpress-to-jekyll-exporter\u002F.\u002Fdocs\u002Frequired-php-version\u002F\" rel=\"nofollow ugc\">Minimum required PHP version\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Security Policy\u003C\u002Fh3>\n\u003Cp>To report a security vulnerability, please email \u003Ca href=\"mailto:ben@balter.com\" rel=\"nofollow ugc\">ben@balter.com\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Where to get help or report an issue\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>For getting started and general documentation, please browse, and feel free to contribute to \u003Ca href=\"http:\u002F\u002Fben.balter.com\u002Fwordpress-to-jekyll-exporter\u002F\" rel=\"nofollow ugc\">the project documentation\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>For support questions (“How do I”, “I can’t seem to”, etc.) please search and if not already answered, open a thread in the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fjekyll-exporter\" rel=\"ugc\">Support Forums\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>For technical issues (e.g., to submit a bug or feature request) please search and if not already filed, \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fbenbalter\u002F\u002Fwordpress-to-jekyll-exporter\u002Fissues\" rel=\"nofollow ugc\">open an issue on GitHub\u003C\u002Fa>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Things to check before reporting an issue\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Are you using the latest version of WordPress?\u003C\u002Fli>\n\u003Cli>Are you using the latest version of the plugin?\u003C\u002Fli>\n\u003Cli>Does the problem occur even when you deactivate all plugins and use the default theme?\u003C\u002Fli>\n\u003Cli>Have you tried deactivating and reactivating the plugin?\u003C\u002Fli>\n\u003Cli>Has your issue \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fbenbalter\u002Fwordpress-to-jekyll-exporter\u002Fissues\" rel=\"nofollow ugc\">already been reported\u003C\u002Fa>?\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>What to include in an issue\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>What steps can another user take to recreate the issue?\u003C\u002Fli>\n\u003Cli>What is the expected outcome of that action?\u003C\u002Fli>\n\u003Cli>What is the actual outcome of that action?\u003C\u002Fli>\n\u003Cli>Are there any screenshots or screencasts that may be helpful to include?\u003C\u002Fli>\n\u003Cli>Only include one bug per issue. If you have discovered two bugs, please file two issues.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Command-line Usage\u003C\u002Fh3>\n\u003Cp>If you’re having trouble with your web server timing out before the export is complete, or if you just like terminal better, you may enjoy the command-line tool.\u003C\u002Fp>\n\u003Cp>It works just like the plugin, but produces the zipfile on STDOUT:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>`\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>php jekyll-export-cli.php > jekyll-export.zip\u003Cbr \u002F>\n    `\u003C\u002Fp>\n\u003Cp>If using this method, you must run first \u003Ccode>cd\u003C\u002Fcode> into the wordpress-to-jekyll-exporter directory.\u003C\u002Fp>\n\u003Cp>Alternatively, if you have \u003Ca href=\"http:\u002F\u002Fwp-cli.org\" rel=\"nofollow ugc\">WP-CLI\u003C\u002Fa> installed, you can run:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>`\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>wp jekyll-export > export.zip\u003Cbr \u002F>\n    `\u003C\u002Fp>\n\u003Cp>The WP-CLI version will provide greater compatibility for alternate WordPress environments, such as when \u003Ccode>wp-content\u003C\u002Fcode> isn’t in the usual location.\u003C\u002Fp>\n\u003Ch3>Filtering by Category or Tag\u003C\u002Fh3>\n\u003Cp>You can export only specific categories or tags using the WP-CLI command. This is useful when you want to convert just one section of your WordPress site instead of the entire corpus.\u003C\u002Fp>\n\u003Ch4>Export posts from a specific category:\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>`bash\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>wp jekyll-export –category=technology > export.zip\u003Cbr \u002F>\n    `\u003C\u002Fp>\n\u003Ch4>Export posts from multiple categories:\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>`bash\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>wp jekyll-export –category=tech,news,updates > export.zip\u003Cbr \u002F>\n    `\u003C\u002Fp>\n\u003Ch4>Export posts with a specific tag:\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>`bash\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>wp jekyll-export –tag=featured > export.zip\u003Cbr \u002F>\n    `\u003C\u002Fp>\n\u003Ch4>Export only pages (or specific post types):\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>`bash\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>wp jekyll-export –post_type=page > export.zip\u003Cbr \u002F>\n    `\u003C\u002Fp>\n\u003Ch4>Combine filters:\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>`bash\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>wp jekyll-export –category=technology –tag=featured –post_type=post > export.zip\u003Cbr \u002F>\n    \u003Ccode>\u003Ch3>Using Filters in PHP\u003C\u002Fh3>\u003Cbr \u002F>\nIf you're using the plugin via PHP code or want more control, you can use the\u003C\u002Fcode>jekyll_export_taxonomy_filters` filter:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>`php\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>add_filter( ‘jekyll_export_taxonomy_filters’, function() {\u003Cbr \u002F>\n    return array(\u003Cbr \u002F>\n        ‘category’ => array( ‘technology’, ‘science’ ),\u003Cbr \u002F>\n        ‘post_tag’ => array( ‘featured’ ),\u003Cbr \u002F>\n    );\u003Cbr \u002F>\n} );\u003C\u002Fp>\n\u003Cp>\u002F\u002F Then trigger the export\u003Cbr \u002F>\nglobal $jekyll_export;\u003Cbr \u002F>\n$jekyll_export->export();\u003Cbr \u002F>\n    `\u003C\u002Fp>\n\u003Ch3>Custom fields\u003C\u002Fh3>\n\u003Cp>When using custom fields (e.g. with the Advanced Custom fields plugin) you might have to register a filter to convert array style configs to plain values.\u003C\u002Fp>\n\u003Ch4>Available Filters\u003C\u002Fh4>\n\u003Cp>The plugin provides two filters for customizing post metadata:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>\u003Ccode>jekyll_export_meta\u003C\u002Fcode>\u003C\u002Fstrong>: Filters the metadata for a single post before it’s merged with taxonomy terms. Receives \u003Ccode>$meta\u003C\u002Fcode> array as the only parameter.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>\u003Ccode>jekyll_export_post_meta\u003C\u002Fcode>\u003C\u002Fstrong>: Filters the complete metadata array (including taxonomy terms) just before it’s written to the YAML frontmatter. Receives \u003Ccode>$meta\u003C\u002Fcode> array and \u003Ccode>$post\u003C\u002Fcode> object as parameters. This is the recommended filter for most use cases.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Note:\u003C\u002Fstrong> As of the latest version, the plugin no longer automatically removes empty or falsy values from the frontmatter. All metadata is preserved by default. If you want to remove certain fields, you can use the \u003Ccode>jekyll_export_post_meta\u003C\u002Fcode> filter to customize this behavior.\u003C\u002Fp>\n\u003Cp>By default, the plugin saves custom fields in an array structure that is exported as:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>`php\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>[“my-bool”]=>\u003Cbr \u002F>\n    array(1) {\u003Cbr \u002F>\n        [0] => string(1) “1”\u003Cbr \u002F>\n    }\u003Cbr \u002F>\n[“location”]=>\u003Cbr \u002F>\n    array(1) {\u003Cbr \u002F>\n        [0] => string(88) “My address”\u003Cbr \u002F>\n    }\u003Cbr \u002F>\n    `\u003C\u002Fp>\n\u003Cp>And this leads to a YAML structure like:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>`yaml\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>my-bool:\u003Cbr \u002F>\n– “1”\u003Cbr \u002F>\nlocation:\u003Cbr \u002F>\n– ‘My address’\u003Cbr \u002F>\n    `\u003C\u002Fp>\n\u003Cp>This is likely not the structure you expect or want to work with. You can convert it using a filter:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>`php\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>add_filter( ‘jekyll_export_meta’, function($meta) {\u003Cbr \u002F>\n    foreach ($meta as $key => $value) {\u003Cbr \u002F>\n        if (is_array($value) && count($value) === 1 && array_key_exists(0, $value)) {\u003Cbr \u002F>\n            $meta[$key] = $value[0];\u003Cbr \u002F>\n        }\u003Cbr \u002F>\n    }\u003C\u002Fp>\n\u003Cpre>\u003Ccode>return $meta;\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>});\u003Cbr \u002F>\n    `\u003C\u002Fp>\n\u003Cp>A more complete solution could look like that:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>`php\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>add_filter( ‘jekyll_export_meta’, function($meta) {\u003Cbr \u002F>\n    foreach ($meta as $key => $value) {\u003Cbr \u002F>\n        \u002F\u002F Advanced Custom Fields\u003Cbr \u002F>\n        if (is_array($value) && count($value) === 1 && array_key_exists(0, $value)) {\u003Cbr \u002F>\n            $value = maybe_unserialize($value[0]);\u003Cbr \u002F>\n            \u002F\u002F Advanced Custom Fields: NextGEN Gallery Field add-on\u003Cbr \u002F>\n            if (is_array($value) && count($value) === 1 && array_key_exists(0, $value)) {\u003Cbr \u002F>\n                $value = $value[0];\u003Cbr \u002F>\n            }\u003Cbr \u002F>\n        }\u003Cbr \u002F>\n        \u002F\u002F convert types\u003Cbr \u002F>\n        $value = match ($key) {\u003Cbr \u002F>\n            \u002F\u002F Advanced Custom Fields: “true_false” type\u003Cbr \u002F>\n            ‘my-bool’ => (bool) $value,\u003Cbr \u002F>\n            default => $value\u003Cbr \u002F>\n        };\u003Cbr \u002F>\n        $meta[$key] = $value;\u003Cbr \u002F>\n    }\u003C\u002Fp>\n\u003Cpre>\u003Ccode>return $meta;\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>});\u003Cbr \u002F>\n    `\u003C\u002Fp>\n\u003Ch4>Removing Empty or Falsy Values\u003C\u002Fh4>\n\u003Cp>If you want to remove empty or falsy values from the frontmatter (similar to the pre-3.0.3 behavior), you can use the \u003Ccode>jekyll_export_post_meta\u003C\u002Fcode> filter:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>`php\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>add_filter( ‘jekyll_export_post_meta’, function( $meta, $post ) {\u003Cbr \u002F>\n    foreach ( $meta as $key => $value ) {\u003Cbr \u002F>\n        \u002F\u002F Remove falsy values except numeric 0\u003Cbr \u002F>\n        if ( ! is_numeric( $value ) && ! $value ) {\u003Cbr \u002F>\n            unset( $meta[ $key ] );\u003Cbr \u002F>\n        }\u003Cbr \u002F>\n    }\u003Cbr \u002F>\n    return $meta;\u003Cbr \u002F>\n}, 10, 2 );\u003Cbr \u002F>\n    `\u003C\u002Fp>\n\u003Ch3>Custom post types\u003C\u002Fh3>\n\u003Cp>To export custom post types, you’ll need to add a filter (w.g. to your themes config file) to do the following:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>`php\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>add_filter( ‘jekyll_export_post_types’, function() {\u003Cbr \u002F>\n    return array(‘post’, ‘page’, ‘you-custom-post-type’);\u003Cbr \u002F>\n});\u003Cbr \u002F>\n    `\u003C\u002Fp>\n\u003Cp>The custom post type will be exported as a Jekyll collection. You’ll need to initialize it in the resulting Jekyll site’s \u003Ccode>_config.yml\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Ch3>Developing locally\u003C\u002Fh3>\n\u003Ch4>Option 1: Using Dev Containers (Recommended)\u003C\u002Fh4>\n\u003Cp>The easiest way to get started is using \u003Ca href=\"https:\u002F\u002Fcode.visualstudio.com\u002Fdocs\u002Fdevcontainers\u002Fcontainers\" rel=\"nofollow ugc\">VS Code Dev Containers\u003C\u002Fa> or \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Ffeatures\u002Fcodespaces\" rel=\"nofollow ugc\">GitHub Codespaces\u003C\u002Fa>:\u003C\u002Fp>\n\u003Col>\n\u003Cli>Install \u003Ca href=\"https:\u002F\u002Fcode.visualstudio.com\u002F\" rel=\"nofollow ugc\">VS Code\u003C\u002Fa> and the \u003Ca href=\"https:\u002F\u002Fmarketplace.visualstudio.com\u002Fitems?itemName=ms-vscode-remote.remote-containers\" rel=\"nofollow ugc\">Dev Containers extension\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ccode>git clone https:\u002F\u002Fgithub.com\u002Fbenbalter\u002Fwordpress-to-jekyll-exporter\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Open the folder in VS Code\u003C\u002Fli>\n\u003Cli>Click “Reopen in Container” when prompted\u003C\u002Fli>\n\u003Cli>Wait for the container to build and dependencies to install\u003C\u002Fli>\n\u003Cli>Access WordPress at \u003Ccode>http:\u002F\u002Flocalhost:8088\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>The devcontainer includes:\u003Cbr \u002F>\n– Pre-configured WordPress and MySQL\u003Cbr \u002F>\n– All PHP extensions and Composer dependencies\u003Cbr \u002F>\n– VS Code extensions for PHP development, debugging, and testing\u003Cbr \u002F>\n– WordPress coding standards configured\u003C\u002Fp>\n\u003Cp>See \u003Ca href=\"https:\u002F\u002Fben.balter.com\u002Fwordpress-to-jekyll-exporter\u002F.\u002F.devcontainer\u002FREADME\u002F\" rel=\"nofollow ugc\">.devcontainer\u002FREADME.md\u003C\u002Fa> for more details.\u003C\u002Fp>\n\u003Ch4>Option 2: Manual Setup\u003C\u002Fh4>\n\u003Ch4>Prerequisites\u003C\u002Fh4>\n\u003Col>\n\u003Cli>\u003Ccode>sudo apt-get update\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>sudo apt-get install composer\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>sudo apt-get install php7.3-xml\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>sudo apt-get install php7.3-mysql\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>sudo apt-get install php7.3-zip\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>sudo apt-get install php-mbstring\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>sudo apt-get install subversion\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>sudo apt-get install mysql-server\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>sudo apt-get install php-pear\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>sudo pear install PHP_CodeSniffer\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Bootstrap & Setup\u003C\u002Fh4>\n\u003Col>\n\u003Cli>\u003Ccode>git clone https:\u002F\u002Fgithub.com\u002Fbenbalter\u002Fwordpress-to-jekyll-exporter\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>cd wordpress-to-jekyll-exporter\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>script\u002Fbootstrap\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>script\u002Fsetup\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Option 3: Docker Compose Only\u003C\u002Fh4>\n\u003Col>\n\u003Cli>\u003Ccode>git clone https:\u002F\u002Fgithub.com\u002Fbenbalter\u002Fwordpress-to-jekyll-exporter\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>docker-compose up\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>open localhost:8088\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>Running tests\u003C\u002Fh3>\n\u003Cpre>\u003Ccode>script\u002Fcibuild\u003Ch3>Performance Optimizations\u003C\u002Fh3>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>This document describes the performance optimizations implemented in Static Site Exporter to improve export speed and reduce resource usage, especially for large WordPress sites.\u003C\u002Fp>\n\u003Ch3>Overview\u003C\u002Fh3>\n\u003Cp>The following optimizations have been implemented to address performance bottlenecks identified in the export process:\u003C\u002Fp>\n\u003Ch4>1. Optimized Database Queries\u003C\u002Fh4>\n\u003Cp>\u003Cstrong>Problem\u003C\u002Fstrong>: The original \u003Ccode>get_posts()\u003C\u002Fcode> method executed a separate SQL query for each post type, then merged the results using \u003Ccode>array_merge()\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>`php\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u002F\u002F Before (inefficient)\u003Cbr \u002F>\nforeach ( $post_types as $post_type ) {\u003Cbr \u002F>\n    $ids   = $wpdb->get_col( $wpdb->prepare( “SELECT ID FROM {$wpdb->posts} WHERE post_type = %s”, $post_type ) );\u003Cbr \u002F>\n    $posts = array_merge( $posts, $ids );\u003Cbr \u002F>\n}\u003Cbr \u002F>\n    `\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Solution\u003C\u002Fstrong>: Changed to a single SQL query using an IN clause.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>`php\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u002F\u002F After (optimized)\u003Cbr \u002F>\n$placeholders = implode( ‘, ‘, array_fill( 0, count( $post_types ), ‘%s’ ) );\u003Cbr \u002F>\n$query        = “SELECT ID FROM {$wpdb->posts} WHERE post_type IN ($placeholders)”;\u003Cbr \u002F>\n$posts        = $wpdb->get_col( $wpdb->prepare( $query, $post_types ) );\u003Cbr \u002F>\n    `\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Impact\u003C\u002Fstrong>: Reduces database round trips from N (number of post types, typically 3) to 1, significantly improving performance on sites with many posts.\u003C\u002Fp>\n\u003Ch4>2. User Data Caching\u003C\u002Fh4>\n\u003Cp>\u003Cstrong>Problem\u003C\u002Fstrong>: The \u003Ccode>convert_meta()\u003C\u002Fcode> method called \u003Ccode>get_userdata()\u003C\u002Fcode> for every post, resulting in redundant database queries for posts by the same author (N+1 query problem).\u003C\u002Fp>\n\u003Cpre>\u003Ccode>`php\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u002F\u002F Before (inefficient)\u003Cbr \u002F>\n‘author’  => get_userdata( $post->post_author )->display_name,\u003Cbr \u002F>\n    `\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Solution\u003C\u002Fstrong>: Implemented a static cache to store user data across post conversions.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>`php\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u002F\u002F After (optimized)\u003Cbr \u002F>\nstatic $user_cache = array();\u003Cbr \u002F>\nif ( ! isset( $user_cache[ $post->post_author ] ) ) {\u003Cbr \u002F>\n    $user_data                        = get_userdata( $post->post_author );\u003Cbr \u002F>\n    $user_cache[ $post->post_author ] = $user_data ? $user_data->display_name : ”;\u003Cbr \u002F>\n}\u003Cbr \u002F>\n‘author’ => $user_cache[ $post->post_author ],\u003Cbr \u002F>\n    `\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Impact\u003C\u002Fstrong>: Eliminates redundant database queries for author information. On a site with 1000 posts by 10 authors, this reduces queries from 1000 to 10.\u003C\u002Fp>\n\u003Ch4>3. HTML to Markdown Converter Reuse\u003C\u002Fh4>\n\u003Cp>\u003Cstrong>Problem\u003C\u002Fstrong>: A new \u003Ccode>HtmlConverter\u003C\u002Fcode> instance was created for every post, wasting memory and CPU cycles on object initialization.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>`php\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u002F\u002F Before (inefficient)\u003Cbr \u002F>\n$converter = new HtmlConverter( $converter_options );\u003Cbr \u002F>\n$converter->getEnvironment()->addConverter( new TableConverter() );\u003Cbr \u002F>\n    `\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Solution\u003C\u002Fstrong>: Reuse a single static instance across all post conversions.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>`php\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u002F\u002F After (optimized)\u003Cbr \u002F>\nstatic $converter = null;\u003Cbr \u002F>\nif ( null === $converter ) {\u003Cbr \u002F>\n    $converter_options = apply_filters( ‘jekyll_export_markdown_converter_options’, array( ‘header_style’ => ‘atx’ ) );\u003Cbr \u002F>\n    $converter         = new HtmlConverter( $converter_options );\u003Cbr \u002F>\n    $converter->getEnvironment()->addConverter( new TableConverter() );\u003Cbr \u002F>\n}\u003Cbr \u002F>\n    `\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Impact\u003C\u002Fstrong>: Reduces object creation overhead. On a site with 1000 posts, this eliminates 999 unnecessary object instantiations.\u003C\u002Fp>\n\u003Ch4>4. Improved File Operations\u003C\u002Fh4>\n\u003Cp>\u003Cstrong>Problem\u003C\u002Fstrong>: The \u003Ccode>copy_recursive()\u003C\u002Fcode> method used the legacy \u003Ccode>dir()\u003C\u002Fcode> API which is slower than modern alternatives.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>`php\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u002F\u002F Before (inefficient)\u003Cbr \u002F>\n$dir = dir( $source );\u003Cbr \u002F>\nwhile ( $entry = $dir->read() ) {\u003Cbr \u002F>\n    \u002F\u002F process files\u003Cbr \u002F>\n}\u003Cbr \u002F>\n$dir->close();\u003Cbr \u002F>\n    `\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Solution\u003C\u002Fstrong>: Replaced with \u003Ccode>scandir()\u003C\u002Fcode> which is faster and more memory-efficient.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>`php\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u002F\u002F After (optimized)\u003Cbr \u002F>\n$entries = @scandir( $source );\u003Cbr \u002F>\nif ( false === $entries ) {\u003Cbr \u002F>\n    return false;\u003Cbr \u002F>\n}\u003Cbr \u002F>\nforeach ( $entries as $entry ) {\u003Cbr \u002F>\n    \u002F\u002F process files\u003Cbr \u002F>\n}\u003Cbr \u002F>\n    `\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Impact\u003C\u002Fstrong>: Improves directory traversal speed, particularly noticeable when copying large upload directories.\u003C\u002Fp>\n\u003Ch4>5. Upload Directory Filtering\u003C\u002Fh4>\n\u003Cp>\u003Cstrong>New Feature\u003C\u002Fstrong>: Added filters to allow skipping or excluding directories during the upload copy process.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Skip Entire Uploads\u003C\u002Fstrong>:\u003Cbr \u002F>\n    \u003Ccode>php\u003Cbr \u002F>\nadd_filter( 'jekyll_export_skip_uploads', '__return_true' );\u003C\u002Fcode>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Exclude Specific Directories\u003C\u002Fstrong> (e.g., cache or temporary files):\u003Cbr \u002F>\n    \u003Ccode>php\u003Cbr \u002F>\nadd_filter( 'jekyll_export_excluded_upload_dirs', function( $excluded ) {\u003Cbr \u002F>\n    return array_merge( $excluded, array( '\u002Fcache\u002F', '\u002Ftmp\u002F', '\u002Fbackup\u002F' ) );\u003Cbr \u002F>\n} );\u003C\u002Fcode>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Impact\u003C\u002Fstrong>: Allows large sites to:\u003Cbr \u002F>\n– Skip uploads entirely if they’re served from a CDN\u003Cbr \u002F>\n– Exclude cache directories that aren’t needed in the export\u003Cbr \u002F>\n– Reduce export time and file size for very large installations\u003C\u002Fp>\n\u003Ch3>Performance Benchmarks\u003C\u002Fh3>\n\u003Ch4>Estimated Improvements\u003C\u002Fh4>\n\u003Cp>Based on the optimizations, expected performance improvements for a typical WordPress site:\u003C\u002Fp>\n\u003Cp>  Site Size\u003Cbr \u002F>\n  Before\u003Cbr \u002F>\n  After\u003Cbr \u002F>\n  Improvement\u003C\u002Fp>\n\u003Cp>  Small (100 posts, 5 authors)\u003Cbr \u002F>\n  ~5s\u003Cbr \u002F>\n  ~3s\u003Cbr \u002F>\n  40% faster\u003C\u002Fp>\n\u003Cp>  Medium (1000 posts, 20 authors)\u003Cbr \u002F>\n  ~45s\u003Cbr \u002F>\n  ~20s\u003Cbr \u002F>\n  55% faster\u003C\u002Fp>\n\u003Cp>  Large (10000 posts, 50 authors)\u003Cbr \u002F>\n  ~8min\u003Cbr \u002F>\n  ~3min\u003Cbr \u002F>\n  63% faster\u003C\u002Fp>\n\u003Cp>\u003Cem>Note: Actual performance depends on server hardware, database configuration, and content complexity.\u003C\u002Fem>\u003C\u002Fp>\n\u003Ch4>Database Query Reduction\u003C\u002Fh4>\n\u003Cp>  Operation\u003Cbr \u002F>\n  Queries Before\u003Cbr \u002F>\n  Queries After\u003Cbr \u002F>\n  Reduction\u003C\u002Fp>\n\u003Cp>  Get posts (3 post types)\u003Cbr \u002F>\n  3\u003Cbr \u002F>\n  1\u003Cbr \u002F>\n  67%\u003C\u002Fp>\n\u003Cp>  User data (100 posts, 5 authors)\u003Cbr \u002F>\n  100\u003Cbr \u002F>\n  5\u003Cbr \u002F>\n  95%\u003C\u002Fp>\n\u003Cp>  \u003Cstrong>Total for 100 posts\u003C\u002Fstrong>\u003Cbr \u002F>\n  \u003Cstrong>103\u003C\u002Fstrong>\u003Cbr \u002F>\n  \u003Cstrong>6\u003C\u002Fstrong>\u003Cbr \u002F>\n  \u003Cstrong>94%\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Ch3>Backward Compatibility\u003C\u002Fh3>\n\u003Cp>All optimizations maintain backward compatibility:\u003Cbr \u002F>\n– All existing WordPress hooks and filters continue to work\u003Cbr \u002F>\n– No changes to the exported file format\u003Cbr \u002F>\n– No changes to the public API\u003Cbr \u002F>\n– New filters are opt-in and don’t affect default behavior\u003C\u002Fp>\n\u003Ch3>Additional Optimization Tips\u003C\u002Fh3>\n\u003Cp>For even better performance on large sites:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\n\u003Cp>\u003Cstrong>Increase PHP memory limit\u003C\u002Fstrong>: Add to \u003Ccode>wp-config.php\u003C\u002Fcode>:\u003Cbr \u002F>\n   \u003Ccode>php\u003Cbr \u002F>\ndefine( 'WP_MEMORY_LIMIT', '512M' );\u003C\u002Fcode>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Use WP-CLI\u003C\u002Fstrong>: The command-line interface bypasses web server timeouts:\u003Cbr \u002F>\n   \u003Ccode>bash\u003Cbr \u002F>\nwp jekyll-export > export.zip\u003C\u002Fcode>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Skip uploads if using CDN\u003C\u002Fstrong>: If your uploads are served from a CDN, you can skip copying them:\u003Cbr \u002F>\n   \u003Ccode>php\u003Cbr \u002F>\nadd_filter( 'jekyll_export_skip_uploads', '__return_true' );\u003C\u002Fcode>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Enable object caching\u003C\u002Fstrong>: Use Redis or Memcached to speed up WordPress core queries.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>Technical Notes\u003C\u002Fh3>\n\u003Ch4>Why Static Variables?\u003C\u002Fh4>\n\u003Cp>Static variables in PHP persist across function calls within the same request. This makes them ideal for caching data during a batch export process where the same function is called many times (once per post).\u003C\u002Fp>\n\u003Ch4>Thread Safety\u003C\u002Fh4>\n\u003Cp>These optimizations are safe for:\u003Cbr \u002F>\n– Single-threaded PHP execution (standard)\u003Cbr \u002F>\n– WordPress multisite installations\u003Cbr \u002F>\n– WP-CLI execution\u003C\u002Fp>\n\u003Cp>They are NOT designed for:\u003Cbr \u002F>\n– Multi-threaded or async PHP environments (not common in WordPress)\u003Cbr \u002F>\n– Long-running daemon processes (not the intended use case)\u003C\u002Fp>\n\u003Ch3>Future Optimization Opportunities\u003C\u002Fh3>\n\u003Cp>Potential areas for future improvement:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Bulk metadata loading\u003C\u002Fstrong>: Pre-load all post meta in a single query\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Taxonomy term caching\u003C\u002Fstrong>: Pre-load all terms to avoid per-post queries\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Streaming ZIP creation\u003C\u002Fstrong>: Write directly to ZIP instead of creating temp directory\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Parallel processing\u003C\u002Fstrong>: Use multiple processes for very large exports (WP-CLI only)\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>Questions?\u003C\u002Fh3>\n\u003Cp>For questions about these optimizations or to report performance issues:\u003Cbr \u002F>\n– \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fbenbalter\u002Fwordpress-to-jekyll-exporter\u002Fissues\" rel=\"nofollow ugc\">Open an issue\u003C\u002Fa>\u003Cbr \u002F>\n– \u003Ca href=\"https:\u002F\u002Fben.balter.com\u002Fwordpress-to-jekyll-exporter\u002F\" rel=\"nofollow ugc\">View the documentation\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch3>Performance Tips for Large Sites\u003C\u002Fh3>\n\u003Cp>If you’re running a large WordPress site with thousands of posts or gigabytes of uploads, here are some tips to make the export process faster and more efficient.\u003C\u002Fp>\n\u003Ch3>Quick Wins\u003C\u002Fh3>\n\u003Ch4>1. Use WP-CLI Instead of Browser Export\u003C\u002Fh4>\n\u003Cp>Browser-based exports are subject to PHP execution time limits (typically 30-300 seconds). Use WP-CLI for unlimited execution time:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>`bash\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>wp jekyll-export > export.zip\u003Cbr \u002F>\n    `\u003C\u002Fp>\n\u003Ch4>2. Skip Uploads if You Don’t Need Them\u003C\u002Fh4>\n\u003Cp>If your images and files are served from a CDN or you plan to handle them separately, you can skip the uploads directory entirely:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>`php\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u002F\u002F Add to your theme’s functions.php or a custom plugin\u003Cbr \u002F>\nadd_filter( ‘jekyll_export_skip_uploads’, ‘__return_true’ );\u003Cbr \u002F>\n    `\u003C\u002Fp>\n\u003Cp>This can save significant time and disk space, especially if you have gigabytes of media files.\u003C\u002Fp>\n\u003Ch4>3. Exclude Cache and Temporary Directories\u003C\u002Fh4>\n\u003Cp>Many sites accumulate cache files and temporary uploads that aren’t needed in the export:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>`php\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>add_filter( ‘jekyll_export_excluded_upload_dirs’, function( $excluded ) {\u003Cbr \u002F>\n    return array_merge( $excluded, array(\u003Cbr \u002F>\n        ‘\u002Fcache\u002F’,\u003Cbr \u002F>\n        ‘\u002Ftmp\u002F’,\u003Cbr \u002F>\n        ‘\u002Fbackup\u002F’,\u003Cbr \u002F>\n        ‘\u002Fwc-logs\u002F’,  \u002F\u002F WooCommerce logs\u003Cbr \u002F>\n        ‘\u002Fwpml\u002F’,     \u002F\u002F WPML cache\u003Cbr \u002F>\n    ) );\u003Cbr \u002F>\n} );\u003Cbr \u002F>\n    `\u003C\u002Fp>\n\u003Ch3>Performance Improvements in Version 2.4.3+\u003C\u002Fh3>\n\u003Cp>Recent optimizations  …\u003C\u002Fp>\n","Features",500,41801,12,"2026-02-09T20:04:00.000Z","6.9.4","4.4","7.2",[51,52,53,54,21],"export","github","github-pages","jekyll","https:\u002F\u002Fgithub.com\u002Fbenbalter\u002Fwordpress-to-jekyll-exporter\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fjekyll-exporter.3.1.1.zip",{"slug":58,"name":59,"version":60,"author":61,"author_profile":62,"description":63,"short_description":64,"active_installs":31,"downloaded":65,"rating":25,"num_ratings":25,"last_updated":66,"tested_up_to":67,"requires_at_least":17,"requires_php":18,"tags":68,"homepage":18,"download_link":70,"security_score":24,"vuln_count":25,"unpatched_count":25,"last_vuln_date":26,"fetched_at":27},"syntax-highlighter-evolved-typescript","SyntaxHighlighter Evolved: Typescript Brush","1.6.0","knarfalingus","https:\u002F\u002Fprofiles.wordpress.org\u002Fknarfalingus\u002F","\u003Cp>Adds support for the TypeScript language to the SyntaxHighlighter Evolved plugin.\u003C\u002Fp>\n","Adds support for the TypeScript language to the SyntaxHighlighter Evolved plugin.",2428,"2018-08-05T18:54:00.000Z","4.9.29",[20,69],"typescript","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsyntax-highlighter-evolved-typescript.zip",{"slug":72,"name":73,"version":74,"author":75,"author_profile":76,"description":77,"short_description":78,"active_installs":25,"downloaded":79,"rating":25,"num_ratings":25,"last_updated":18,"tested_up_to":47,"requires_at_least":80,"requires_php":81,"tags":82,"homepage":87,"download_link":88,"security_score":13,"vuln_count":25,"unpatched_count":25,"last_vuln_date":26,"fetched_at":89},"yaml-custom-fields","YAML Custom Fields","1.2.7","starbist","https:\u002F\u002Fprofiles.wordpress.org\u002Fstarbist\u002F","\u003Cp>YAML Custom Fields allows you to define structured content schemas with an intuitive interface and ACF-like template functions. Perfect for theme developers who want flexible, schema-based content management without the complexity.\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Define YAML schemas for page templates and template partials\u003C\u002Fli>\n\u003Cli>15+ field types including string, rich-text, images, blocks, taxonomies, data objects, and more\u003C\u002Fli>\n\u003Cli>Easy-to-use admin interface for managing schemas and data\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Three-level data hierarchy:\u003C\u002Fstrong>\n\u003Cul>\n\u003Cli>Per-page data for individual customization (stored in post meta)\u003C\u002Fli>\n\u003Cli>Per-template global data shared across all posts using the same template\u003C\u002Fli>\n\u003Cli>Site-wide global data for partials like headers and footers\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Per-field global\u002Flocal toggle:\u003C\u002Fstrong> Each field can independently use template global data or page-specific data\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Visual dual-field interface:\u003C\u002Fstrong> See both template global and page-specific values side-by-side\u003C\u002Fli>\n\u003Cli>Data Objects for managing structured, reusable data (universities, companies, etc.)\u003C\u002Fli>\n\u003Cli>Data Validation page for reviewing imported content\u003C\u002Fli>\n\u003Cli>Consolidated Export\u002FImport page for all data types (settings, page data, data objects)\u003C\u002Fli>\n\u003Cli>Simple template functions with ACF-like syntax and auto-merge behavior\u003C\u002Fli>\n\u003Cli>Administrator-only access for security\u003C\u002Fli>\n\u003Cli>Clean uninstall removes all database records\u003C\u002Fli>\n\u003Cli>WordPress Coding Standards compliant\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Supported Field Types\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>String\u003C\u002Fstrong> – Single-line text with min\u002Fmax length\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Text\u003C\u002Fstrong> – Multi-line textarea\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Rich Text\u003C\u002Fstrong> – WordPress WYSIWYG editor\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Code\u003C\u002Fstrong> – Code editor with syntax highlighting\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Boolean\u003C\u002Fstrong> – Checkbox for true\u002Ffalse values\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Number\u003C\u002Fstrong> – Number input with min\u002Fmax constraints\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Date\u003C\u002Fstrong> – Date picker with optional time\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Select\u003C\u002Fstrong> – Dropdown with single\u002Fmultiple selection\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Taxonomy\u003C\u002Fstrong> – WordPress categories, tags, or custom taxonomies with single\u002Fmultiple selection\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Post Type\u003C\u002Fstrong> – Dropdown to select registered post types (Post, Page, custom post types)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Data Object\u003C\u002Fstrong> – Reference to structured data objects managed independently (universities, companies, team members, etc.)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Image\u003C\u002Fstrong> – WordPress media uploader for images\u003C\u002Fli>\n\u003Cli>\u003Cstrong>File\u003C\u002Fstrong> – WordPress media uploader for any file\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Object\u003C\u002Fstrong> – Nested group of fields\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Block\u003C\u002Fstrong> – Repeatable blocks for flexible page builders\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Usage Example\u003C\u002Fh4>\n\u003Cp>In your theme template:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003C?php\n$hero_title = ycf_get_field('hero_title');\n$hero_image = ycf_get_image('hero_image', null, 'full');\n$category = ycf_get_term('category');\n$post_type = ycf_get_post_type('content_type');\n$university = ycf_get_data_object('university');\n$features = ycf_get_field('features');\n?>\n\n\u003Cdiv class=\"hero\">\n  \u003C?php if ($hero_image): ?>\n    \u003Cimg src=\"\u003C?php echo esc_url($hero_image['url']); ?>\" alt=\"\u003C?php echo esc_attr($hero_image['alt']); ?>\">\n  \u003C?php endif; ?>\n  \u003Ch1>\u003C?php echo esc_html($hero_title); ?>\u003C\u002Fh1>\n  \u003C?php if ($category): ?>\n    \u003Cspan class=\"category\">\u003C?php echo esc_html($category->name); ?>\u003C\u002Fspan>\n  \u003C?php endif; ?>\n  \u003C?php if ($university): ?>\n    \u003Cp>\u003C?php echo esc_html($university['name']); ?>\u003C\u002Fp>\n  \u003C?php endif; ?>\n\u003C\u002Fdiv>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3>Developer Documentation\u003C\u002Fh3>\n\u003Ch4>Template Functions\u003C\u002Fh4>\n\u003Cp>\u003Cstrong>Get a single field value:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$value = ycf_get_field('field_name');\n$value = ycf_get_field('field_name', 123); \u002F\u002F Specific post ID\n$value = ycf_get_field('logo', 'partial:header.php'); \u002F\u002F From partial\n$value = ycf_get_field('title', null, $block); \u002F\u002F From block context\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Get image field with details:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$image = ycf_get_image('field_name', null, 'full');\n$image = ycf_get_image('field_name', 123, 'thumbnail'); \u002F\u002F Specific post ID\n$image = ycf_get_image('icon', null, 'medium', $block); \u002F\u002F From block context\n\n\u002F\u002F Returns: array('id', 'url', 'alt', 'title', 'caption', 'description', 'width', 'height')\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Get file field with details:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$file = ycf_get_file('field_name', null);\n$file = ycf_get_file('field_name', 123); \u002F\u002F Specific post ID\n$file = ycf_get_file('document', null, $block); \u002F\u002F From block context\n\n\u002F\u002F Returns: array('id', 'url', 'path', 'filename', 'filesize', 'mime_type', 'title')\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Get taxonomy field (term or terms):\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$term = ycf_get_term('field_name', null);\n$term = ycf_get_term('field_name', 123); \u002F\u002F Specific post ID\n$term = ycf_get_term('category', null, $block); \u002F\u002F From block context\n\n\u002F\u002F Returns: WP_Term object or array of WP_Term objects (for multiple selection)\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Get post type field:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$post_type = ycf_get_post_type('field_name', null);\n$post_type = ycf_get_post_type('field_name', 123); \u002F\u002F Specific post ID\n$post_type = ycf_get_post_type('content_type', null, $block); \u002F\u002F From block context\n\n\u002F\u002F Returns: WP_Post_Type object or null\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Get data object field:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$university = ycf_get_data_object('field_name', null);\n$university = ycf_get_data_object('field_name', 123); \u002F\u002F Specific post ID\n$university = ycf_get_data_object('university', null, $block); \u002F\u002F From block context\n\n\u002F\u002F Returns: Array with data object entry fields or null\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Get all entries of a data object type:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$all_universities = ycf_get_data_objects('universities');\nforeach ($all_universities as $entry_id => $university) {\n    echo esc_html($university['name']);\n}\n\n\u002F\u002F Returns: Array of all entries for the specified data object type\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Get all fields:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$fields = ycf_get_fields();\n$fields = ycf_get_fields(123); \u002F\u002F Specific post ID\n$fields = ycf_get_fields('partial:footer.php'); \u002F\u002F From partial\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Check if field exists:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>if (ycf_has_field('hero_title')) {\n    echo ycf_get_field('hero_title');\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Working with Block fields:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$blocks = ycf_get_field('features');\n\nif (!empty($blocks)) {\n    foreach ($blocks as $block) {\n        \u002F\u002F Access nested fields using context_data parameter\n        $title = ycf_get_field('title', null, $block);\n        $icon = ycf_get_image('icon', null, 'thumbnail', $block);\n        $category = ycf_get_term('category', null, $block);\n\n        echo '\u003Ch3>' . esc_html($title) . '\u003C\u002Fh3>';\n        if ($icon) {\n            echo '\u003Cimg src=\"' . esc_url($icon['url']) . '\">';\n        }\n        if ($category) {\n            echo '\u003Cspan>' . esc_html($category->name) . '\u003C\u002Fspan>';\n        }\n    }\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Sample YAML Schema\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>fields:\n  - name: hero_title\n    label: Hero Title\n    type: string\n    required: true\n    options:\n      maxlength: 100\n  - name: hero_image\n    label: Hero Image\n    type: image\n  - name: category\n    label: Category\n    type: taxonomy\n    options:\n      taxonomy: category\n  - name: tags\n    label: Tags\n    type: taxonomy\n    multiple: true\n    options:\n      taxonomy: post_tag\n  - name: content_type\n    label: Content Type\n    type: post_type\n  - name: university\n    label: University\n    type: data_object\n    options:\n      object_type: universities\n  - name: features\n    label: Features\n    type: block\n    list: true\n    blockKey: type\n    blocks:\n      - name: feature\n        label: Feature Block\n        fields:\n          - name: title\n            label: Title\n            type: string\n          - name: icon\n            label: Icon\n            type: image\n          - name: description\n            label: Description\n            type: text\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Working with Partials\u003C\u002Fh4>\n\u003Cp>For custom partials, add the @ycf marker in the file header:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003C?php\n\u002F**\n * Custom Navigation Partial\n * @ycf\n *\u002F\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Then click “Refresh Template List” in the YAML Custom Fields admin page.\u003C\u002Fp>\n\u003Ch4>Template Global Fields\u003C\u002Fh4>\n\u003Cp>Template Global Fields allow you to define default values that are shared across all posts using the same template, while still allowing individual posts to override specific fields.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Setting up Template Global:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Col>\n\u003Cli>Go to \u003Cstrong>YAML Custom Fields\u003C\u002Fstrong> admin page\u003C\u002Fli>\n\u003Cli>Enable YAML for your template (e.g., page.php)\u003C\u002Fli>\n\u003Cli>Click \u003Cstrong>Add Template Global\u003C\u002Fstrong> to define the template global schema\u003C\u002Fli>\n\u003Cli>Define fields that should have shared default values\u003C\u002Fli>\n\u003Cli>Click \u003Cstrong>Manage Template Global Data\u003C\u002Fstrong> to set the default values\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>\u003Cstrong>Using Template Global in Posts:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>When editing a post that uses a template with Template Global fields, you’ll see a dual-field interface for each field:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Template Global (All Pages)\u003C\u002Fstrong> – Read-only display showing the default value (with Edit link)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Page-Specific Value\u003C\u002Fstrong> – Editable field for this post only\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Checkbox\u003C\u002Fstrong> – “Use template global for this field” – Toggle per field\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Benefits:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Consistency:\u003C\u002Fstrong> Set default values once, use across all posts\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Flexibility:\u003C\u002Fstrong> Override any field on any post individually\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Clarity:\u003C\u002Fstrong> See both global and local values side-by-side\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Efficiency:\u003C\u002Fstrong> Update template global to affect all posts at once\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Data Priority (when using template functions):\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>When a field uses template global, \u003Ccode>ycf_get_field()\u003C\u002Fcode> returns data in this priority order:\u003C\u002Fp>\n\u003Col>\n\u003Cli>Page-specific value (if “use template global” is unchecked)\u003C\u002Fli>\n\u003Cli>Template global value (if “use template global” is checked)\u003C\u002Fli>\n\u003Cli>Site-wide global value (if template has site-wide global enabled)\u003C\u002Fli>\n\u003Cli>null (if no value exists)\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Data Storage\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Page\u002FPost data:\u003C\u002Fstrong> Stored in post meta with key \u003Ccode>_yaml_cf_data\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Template Global preferences:\u003C\u002Fstrong> Stored in post meta with key \u003Ccode>_yaml_cf_use_template_global_fields\u003C\u002Fcode> (per-field array)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Template Global schemas:\u003C\u002Fstrong> Stored in options table with key \u003Ccode>yaml_cf_template_global_schemas\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Template Global data:\u003C\u002Fstrong> Stored in options table with key \u003Ccode>yaml_cf_template_global_data\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Site-wide global schema:\u003C\u002Fstrong> Stored in options table with key \u003Ccode>yaml_cf_global_schema\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Site-wide global data:\u003C\u002Fstrong> Stored in options table with key \u003Ccode>yaml_cf_global_data\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Partial data:\u003C\u002Fstrong> Stored in options table with key \u003Ccode>yaml_cf_partial_data\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Schemas:\u003C\u002Fstrong> Stored in options table with key \u003Ccode>yaml_cf_schemas\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Data Object Types:\u003C\u002Fstrong> Stored in options table with key \u003Ccode>yaml_cf_data_object_types\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Data Object Entries:\u003C\u002Fstrong> Stored in options table with keys \u003Ccode>yaml_cf_data_object_entries_{type_slug}\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Privacy Policy\u003C\u002Fh3>\n\u003Cp>YAML Custom Fields does not collect, store, or transmit any user data outside of your WordPress installation. All data is stored locally in your WordPress database.\u003C\u002Fp>\n\u003Ch3>Third-Party Libraries\u003C\u002Fh3>\n\u003Cp>This plugin includes the following third-party libraries:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Symfony YAML Component\u003C\u002Fstrong> (v6.4) – Licensed under MIT License (GPL-compatible)\n\u003Cul>\n\u003Cli>Homepage: https:\u002F\u002Fsymfony.com\u002Fcomponents\u002FYaml\u003C\u002Fli>\n\u003Cli>License: https:\u002F\u002Fgithub.com\u002Fsymfony\u002Fyaml\u002Fblob\u002F7.3\u002FLICENSE\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Credits\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Author: \u003Ca href=\"https:\u002F\u002Fwww.silvestar.codes\" rel=\"nofollow ugc\">Silvestar Bistrovic\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Support\u003C\u002Fh3>\n\u003Cp>For documentation, examples, and support, visit:\u003Cbr \u002F>\n* \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FmaliMirkec\u002Fyaml-custom-fields\" rel=\"nofollow ugc\">Plugin Documentation\u003C\u002Fa>\u003Cbr \u002F>\n* \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FmaliMirkec\u002Fyaml-custom-fields\u002Fissues\" rel=\"nofollow ugc\">Report Issues\u003C\u002Fa>\u003C\u002Fp>\n","A WordPress plugin for managing YAML frontmatter schemas in theme templates and partials.",252,"5.0","8.1",[83,84,85,86,21],"custom-fields","frontmatter","meta-fields","schema","https:\u002F\u002Fgithub.com\u002FmaliMirkec\u002Fyaml-custom-fields","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fyaml-custom-fields.1.2.7.zip","2026-03-15T10:48:56.248Z",{"attackSurface":91,"codeSignals":107,"taintFlows":114,"riskAssessment":115,"analyzedAt":118},{"hooks":92,"ajaxHandlers":103,"restRoutes":104,"shortcodes":105,"cronEvents":106,"entryPointCount":25,"unprotectedCount":25},[93,98],{"type":94,"name":95,"callback":96,"file":97,"line":45},"action","init","syntaxhighlighter_yaml_regscript","syntaxhighlighter_yaml.php",{"type":99,"name":100,"callback":101,"file":97,"line":102},"filter","syntaxhighlighter_brushes","syntaxhighlighter_yaml_addlang",15,[],[],[],[],{"dangerousFunctions":108,"sqlUsage":109,"outputEscaping":111,"fileOperations":25,"externalRequests":25,"nonceChecks":25,"capabilityChecks":25,"bundledLibraries":113},[],{"prepared":25,"raw":25,"locations":110},[],{"escaped":25,"rawEcho":25,"locations":112},[],[],[],{"summary":116,"deductions":117},"The plugin 'syntaxhighlighter-evolved-yaml-brush' v1.0.1 demonstrates an excellent security posture based on the provided static analysis.  The absence of any identified dangerous functions, SQL queries not using prepared statements, unescaped output, file operations, external HTTP requests, nonce checks, capability checks, or bundled libraries is highly commendable.  Furthermore, the lack of any recorded vulnerabilities in its history, including critical or high-severity ones, strongly suggests a well-maintained and secure codebase. The attack surface is completely protected, with no AJAX handlers, REST API routes, shortcodes, or cron events that lack proper authentication or permission checks.",[],"2026-03-16T21:37:34.593Z",{"wat":120,"direct":127},{"assetPaths":121,"generatorPatterns":123,"scriptPaths":124,"versionParams":125},[122],"\u002Fwp-content\u002Fplugins\u002Fsyntaxhighlighter-evolved-yaml-brush\u002FshBrushYaml.js",[],[122],[126],"syntaxhighlighter-brush-yaml?ver=",{"cssClasses":128,"htmlComments":129,"htmlAttributes":130,"restEndpoints":131,"jsGlobals":132,"shortcodeOutput":133},[],[],[],[],[],[]]