Re-present Site Starter to Viget

[stephaniefois]

Overview

The last update the company was given about Site Starter was after the Content Team's initial work to produce V1 of that Wordpress theme, before we even had a real project using it. Now we multiple sites under our belt and several iterations, Viget at large could use an update.

[bd-viget]

Somewhat related, with the publishing of this blog post about the Blocks Toolkit, I think we should submit the plugin to the WordPress.org Plugin Repository. In order to do that, we'll need to fill out the plugin's readme.txt file (standards), which populates the plugin page (example here). This includes, but is not limited to:

• Icon
• Cover Image
• Description
• Screenshots
• FAQ
• WordPress.org accounts of those that have contributed (briandichiara, Nathan Schmidt, Nevin Morgan)

[bd-viget]

I wanted to note I submitted the Viget Blocks Toolkit to the WordPress.org Plugin repo last week, the credentials for the account I created are in 1Password. Here are the details I put in the readme.txt:

Short Description

Simplifying Block Registration and other block editor related features.

Full Description

Enhancements to the block editor as well as simplifying custom block registration with Advanced Custom Fields Pro.

See full features and documentation in the GitHub README file.

FAQs

Is Advanced Custom Fields Pro required?

No. There are several features of this plugin that can be used without Advanced Custom Fields Pro. However, to utilize the block registration feature, Advanced Custom Fields Pro is required at this time.

Screenshots

1. Block Icons

2. Breakpoint Visibility Settings

3. Media Position Example