Implement query to get the usage of different WordPress template types on the home page #150
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…s on the home page.
felixarntz
requested review from
westonruter,
joemcgill,
swissspidy and
adamsilverstein
swissspidy
approved these changes
Aug 20, 2024
joemcgill
approved these changes
Aug 21, 2024
| SELECT | ||
| date, | ||
| "WordPress" AS cms, | ||
| IF(client = "mobile", "phone", "desktop") AS device, |
There was a problem hiding this comment.
I don't see "mobile" show up in the query results you posted in the description. I'm curious why you've included it here?
Comment on lines
+36
to
+37
| CAST(JSON_EXTRACT_SCALAR(custom_metrics, "$.cms.wordpress.content_type.post_type") AS STRING) AS postType, | ||
| CAST(JSON_EXTRACT_SCALAR(custom_metrics, "$.cms.wordpress.content_type.taxonomy") AS STRING) AS taxonomy |
There was a problem hiding this comment.
Are either of these return values being used for something?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In recent years, it has been brought up several times to change the WordPress default of showing a blog on the home page by default to showing a static front page instead. This query looks at how common each variant is across the WordPress home pages indexed by HTTP Archive.
This is based on the detection implemented in the
httparchive/custom-metricsrepository, which relies on the WordPress-generated body classes.Query results
Summary
blog(i.e. not determined as the home blog), anarchive, orsingularcontent. Those are consistently far lower than 1% though, so it's not too relevant for the data. Possibly it happens because HTTP Archive considers some pages as root pages that are technically not the home page of the respective WordPress site.