1.2.02 min read
Theme Review Compliance
WordPress.org review-relevant implementation notes for Epiktetos.
This page records review-relevant facts found in the inspected theme. It is not a substitute for running the current WordPress.org Theme Review checks.
Present in the inspected source
| Area | Finding |
|---|---|
| License | GPL v2 or later declared in style.css and readme.txt. |
| Theme metadata | Theme name, project URI, author URI, version, requirements, text domain, and tags are declared. |
| Screenshot | screenshot.png is present. |
| Readme | readme.txt is present. |
| PHPCS config | phpcs.xml.dist is present in source only and excluded from the clean release ZIP. |
| Text domain | epiktetos is declared and loaded. |
| Theme supports | Standard supports are registered in functions.php. |
| External fonts | Readme describes self-hosted fonts. |
| Nonces and capabilities | Admin tooling includes nonce and capability checks in inspected paths. |
| Activation behavior | The theme shows a setup notice; no forced automatic redirect was documented in inspected behavior. |
| Sample Content | Bundled local content is opt-in from the Epiktetos admin screens and uses local package files. |
Release ZIP checks
The 1.2.0 release ZIP was checked for common package issues:
- No macOS junk files.
- No
node_modulesorvendordirectories. - No
.envfiles or credentials. - No local WordPress runtime files.
- No
phpcs.xml.dist. - Root folder is
epiktetos/. - Version consistency:
style.css,readme.txt,functions.php, changelog, and release notes all use1.2.0.
Items to verify before submission
- Run Theme Check and PHP_CodeSniffer with the WordPress standards.
- Generate and include a translation template if the distribution target requires it.
- Confirm all output is escaped and all input is sanitized in current code.
- Confirm admin notices, wizard actions, and sample content actions are opt-in and capability protected.
- Confirm accessibility behavior with keyboard and screen-reader testing.
Guidelines change
WordPress.org theme review rules can change. Always compare the release package with the current guidelines before submission.