
Pre-configured Media Kit Page using Gutenberg Block Patterns.
Publisher Media Kit provides a quick and easy option for small to medium sized publishers to digitize their media kit. If you are a publisher hoping for a page like the NY Times’ Advertising Standard Units, but do not have a designer or developer on staff? Then this plugin is for you. If you are still using a print or PDF version of your media kit to sell space on your website, but want show advertisers looking to buy digital real estate that you are a digital-forward partner? Then this plugin is for you.
The plugin adds a new “Media Kit” page, block patterns, and placeholder content that can then be customized to fit your need (e.g., text, links, colors, images, adding page link to site footer).
We have tested the plugin with the following WordPress themes and have validated that the resulting Media Kit page renders as expected on the front-end and within the block editor. Please open an issue if you find an issue with any of these themes or have an alternate, public theme with a conflict that we can help resolve.

View of block patterns and placeholder content within the block editor running the Twenty Twenty One default theme.

Media Kit page on frontend of site running the Twenty Twenty One default theme.

View of block patterns and placeholder content within the block editor running the Newspack base theme.

Media Kit page on frontend of site running the Newspack base theme.
Click the block inserter (+ button) in the top left of the block editor, click the Patterns tab, select Publisher Media Kit in the dropdown, and select the specific Block Pattern that you want to add back to your page.
Click the block inserter (+ button) in the top left of the block editor, click the Patterns tab, select Publisher Media Kit in the dropdown, and select the specific Block Pattern that you want to add to your post/page.
The plugin specifically checks for the page slug media-kit, meaning that even if you modify the page name, the plugin will not generate a new page unless the page slug is altered or the page is moved to the trash.
@cypress/request from 2.88.12 to 3.0.1 (props @dependabot, @faisal-alvi, @dkotter, @jeffpaul via #166).cypress from 11.2.0 to 13.3.0 (props @dependabot, @faisal-alvi, @dkotter, @jeffpaul via #166).follow-redirects from 1.15.3 to 1.15.4 (props @dependabot, @faisal-alvi via #177).tough-cookie from 4.0.0 to 4.1.3 and @cypress/request from 2.88.10 to 2.88.12 (props @dependabot, @faisal-alvi via #156).simple-git from 3.15.1 to 3.16.0 (props @dependabot, @faisal-alvi via #130).http-cache-semantics from 4.1.0 to 4.1.1 (props @dependabot, @faisal-alvi via #131).dns-packet from 5.3.1 to 5.4.0 (props @dependabot, @faisal-alvi via #133).webpack from 5.73.0 to 5.76.1 (props @dependabot, @faisal-alvi via #134).got from 10.7.0 to 11.8.5 and @wordpress/env from 4.8.0 to 5.2.0 (props @dependabot via #100).loader-utils from 2.0.2 to 2.0.4 (props @dependabot, @faisal-alvi, @jeffpaul via #106, #109).minimatch from 3.0.4 to 3.1.2 (props @dependabot, @faisal-alvi, @jeffpaul via #107).simple-git from 3.14.0 to 3.15.1 (props @dependabot, @faisal-alvi via #124).json5 from 1.0.1 to 1.0.2 (props @dependabot, @faisal-alvi via #127).Note that this release bumps the minimum required version of WordPress from 5.5 to 5.7 and PHP from 7.0 to 7.4.
terser from 5.14.0 to 5.14.2 (props @dependabot, @faisal-alvi via #95).Further changelog entries can be found in the CHANGELOG.md file.