New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Estimate effort to migrate to the new block editor #15
Comments
To evaluate the existing site content we'll develop a [content] shortcode that will count the number of posts for each registered post_type and determine how many posts there are which are potentially editable using the block editor. The [content] shortcode will produce a detailed report for each post type and a summary report grouping post types and counts. The totals from each report can be accumulated in a spread sheet to enable analysis of the current state of affairs and the predicted state when post types are enabled for the block editor. |
…s having analysed all potential posts
I recently published a blog post entitled The high level figures, were
The herbmiller.me site has Gutenberg activated, plus the oik-block plugin. The blog post uses the prototype CSV block multiple times. The post was initially written in a local version of the site ( qw/hm ) then the content was cloned using |
Migrating existing sites to use the new block editor could be a massive task.
Each developer / site owner will need to develop an implementation plan that evaluates the current situation and where they want to be some time in the future.
The effort to migrate varies from one site to another.
Requirement
Stages
1. Initial evaluation
Produce high level estimates of the effort involved
Initially assume the worst and that absolutely everything has to be done to avoid disaster.
Use finger in the air effort estimating based on recent experience, known issues and system complexity.
2. Adjust estimates
Drill down into the first sets of results to determine which tasks can be eliminated.
3. Prioritise effort
The text was updated successfully, but these errors were encountered: