PHPackages samikeijonen/uuups - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. samikeijonen/uuups ActiveWordpress-theme samikeijonen/uuups ================== A WordPress starter theme. 1.1.0(7y ago)44303[16 PRs](https://github.com/samikeijonen/uuups/pulls)GPL-2.0-or-laterCSSPHP >=5.6 Since Sep 2Pushed 3y ago6 watchersCompare [ Source](https://github.com/samikeijonen/uuups)[ Packagist](https://packagist.org/packages/samikeijonen/uuups)[ Docs](https://github.com/samikeijonen/uuups)[ RSS](/packages/samikeijonen-uuups/feed)WikiDiscussions master Synced 3d ago READMEChangelog (4)Dependencies (3)Versions (34)Used By (0) [![Build Status](https://camo.githubusercontent.com/8f63ea1b04961800dfab582cd72268ab8582660129074b81d7b2a8a58c47614a/68747470733a2f2f7472617669732d63692e6f72672f73616d696b65696a6f6e656e2f75757570732e7376673f6272616e63683d646576)](https://travis-ci.org/samikeijonen/uuups) Uuups – experimental WordPress Theme ==================================== [](#uuups--experimental-wordpress-theme) Uuups is an experiment how to bring your theme to the next level. 1. The theme uses modern PHP, JS, CSS, and other tools. 2. The theme also attempts to stick with WP standards so that it doesn't feel too foreign. Version from Mythic ------------------- [](#version-from-mythic) This is my playground from [Justin Tadlock's starter theme called Mythic](https://github.com/justintadlock/mythic). Most of the code is the same but I have small experiments here and there. Documentation ------------- [](#documentation) Read [documentation from Mythic Wiki](https://github.com/justintadlock/mythic/wiki). Demo ---- [](#demo) [Demo can be seen in Foxland site](https://foxland.fi/demo/uuups/). My wishlist ----------- [](#my-wishlist) I have hopes and dreams for the starter theme: - Accessibility ready out of the box. - Clean semantic HTML without lots of extra DIVs - Scalable, modular CSS/SASS architecture. It should guide developers how they write their CSS. - Ready for Gutenberg and a maximum WYSIWYG experience. - ES6 for JavaScript. - Gulp, Webpack, or npm scripts for automated tasks like - compiling assets. - optimising images and SVGs. - CSS, JS, and PHPCS linting. - SVG system. - Being design system ready. My workflow ----------- [](#my-workflow) I'll work on `dev` branch where I keep un-minified CSS, JS, SVGs etc. In `master` all assets are cleaned and compile when running `npm run build`. In other words `master` branch is ready for production. Accessibility testing --------------------- [](#accessibility-testing) [Pa11y](https://github.com/pa11y/pa11y) runs your code against [HTML CodeSniffer](http://squizlabs.github.com/HTML_CodeSniffer/). Check documentation from `pa11y` site. On the command line test any local or live URL: ``` pa11y http://example.com/ ``` I recommend also [aXe browser add-on](https://www.deque.com/aXe/) or [aXe-CLI](https://github.com/dequelabs/axe-cli). More info about [Frontend checks for web accessibility](https://make.wordpress.org/accessibility/handbook/best-practices/test-for-web-accessibility/test-for-web-accessibility-frontend-code/). CSS structure ------------- [](#css-structure) CSS structure is probably one of the biggest aspects of the front-end and theming. It should have scalable and modular architecture. Styles are written in `resources/css` folder. There are two separate stylesheets which are automatically compiled to `dist/css`: - `style.scss` – Main stylesheet for the theme. - `editor.scss` – Stylesheet only for the block editor (Gutenberg). ### Main stylesheet [](#main-stylesheet) Main stylesheet `style.scss` follows [ITCSS](https://www.xfive.co/blog/itcss-scalable-maintainable-css-architecture/) approach and [BEM](http://getbem.com/) naming convention. The main point of ITCSS is that it separates your CSS codebase to several sections (layers). It guides you to write CSS from low-specificity selectors to more specific ones. It also plays nicely with the new editor (Gutenberg) because block styles can be one of the layers. We should write separate documentation about SASS and CSS, it's that important. ### Styles for the editor [](#styles-for-the-editor) `editor.scss` tries to put all the necessary styles to the new editor without re-writing front-end styles. Note a little trick where we prefix all the styles with class `editor-styles-wrapper` using `postcss-editor-styles` plugin. New editor (Gutenberg) support ------------------------------ [](#new-editor-gutenberg-support) At the moment support for new editor means these things to me: - Add support for `editor-color-palette` to match theme colors. - Add support for `editor-font-sizes` to match theme font sizes. - Add support for `align-wide` blocks. - Dequeue Core block styles: - This is because I don't want to overwrite and add too spesific rules to main stylesheet. - Core blocks have their own CSS layer as mentioned before. It can be found in `recources/css/blocks`. - Get maximum WYSIWYG experience in the editor by enqueueing block related styles using `enqueue_block_editor_assets` hook. See previous chapter [styles for the editor](#styles-for-the-editor). Coding standards and linting ---------------------------- [](#coding-standards-and-linting) Theme mostly follows [WordPress coding standards](https://make.wordpress.org/core/handbook/best-practices/coding-standards/). There is `pre-commit` hook which runs PHP, Style, and JavaScript linting before new commits can be pushed to repo. For example if there are changes in CSS files, it runs `npm run lint:css` before the commit. You can use `--no-verify` flag to bypass linting check: ``` git commit --no-verify -m "Your commit message." ``` All lints can be run by command `npm run lint`. Or use any of the following lint commands. ### PHP linting [](#php-linting) NPM task `npm run lint:php` checks PHP files using [WordPress coding standars (WPCS)](https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards). In `.phpcs.xml.dist` there is custom PHP ruleset `Foxland-Default` which extends `WPCS`. This is loaded via [composer package](https://packagist.org/packages/samikeijonen/phpcs-composer). ### Style linting [](#style-linting) NPM task `npm run lint:css` checks CSS files using [stylelint](https://github.com/stylelint/stylelint). File `.stylelintrc` is the configuration file for stylelint. I also recommend installing stylelint extension to your IDE, for example [vscode-stylelint](https://marketplace.visualstudio.com/items?itemName=shinnn.stylelint). ### JavaScript linting [](#javascript-linting) NPM task `npm lint:js` checks JS files using [ESLint](https://eslint.org/). File `.eslintrc.js` is the configuration file for ESLint. And `.eslintignore` file for what files to ignore from linting. I also recommend installing ESLint extension to your IDE, for example [VS Code ESLint extension](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint). ### Run your code automatically through Travis CI [](#run-your-code-automatically-through-travis-ci) When you commit changes in Github, let [Travis CI](https://travis-ci.org/) run and test your code. File `.travis.yml` is the configuration file for setting up Travis. ### Editorconfig [](#editorconfig) Theme has an `.editorconfig` file that sets your code editor settings accordingly. [Download the extension to your editor](http://editorconfig.org/#download). The settings will automatically be applied when you edit code when you have the extension. New version ----------- [](#new-version) Generate `.zip` file using command: ``` npm run release -- --version={version-number} ``` For example: ``` npm run release -- --version=1.0.0 ``` This will generate zip file `releases/uuups-1.0.0.zip`. SVG system ---------- [](#svg-system) All the main SVG related functions can be found in the `app/functions-svg.php` file. It’s well-documented in the code, but here’s a summary: - Add SVG icons in `resources/svg` folder. `npm run dev` or `npm run build` copies these SVG files in `dist/svg` folder. - In the same cleans them up. - Adds attributes and classes for using these icons as decorative only. - `Uuups\get_svg()` function returns inline SVG icon markup by default. - For example `Uuups\get_svg( [ 'icon' => 'folder-open' ]`. - SVG icons are automatically used in Social links menu. If the SVG is not decorative, add SVG markup directly in the markup. FAQ --- [](#faq) > What about sidebars? For old themes I probably would not try to add align-wide support if child themes can be broken. For new themes you can definitely have "wide" and "full-width" blocks even if there is sidebar on the right or left. Yeah but how? Using CSS :) Other starter themes -------------------- [](#other-starter-themes) Check out - [Tonik](https://github.com/tonik/theme/). - [Sage](https://github.com/roots/sage/). ### Health Score 33 — LowBetter than 75% of packages Maintenance20 Infrequent updates — may be unmaintained Popularity19 Limited adoption so far Community13 Small or concentrated contributor base Maturity68 Established project with proven stability Bus Factor1 Top contributor holds 90.6% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~16 days Total 4 Last Release 2644d ago ### Community Maintainers ![](https://www.gravatar.com/avatar/ccaa88499ddddbbb1c5112a92e6b2f4e695ae1bf78135a548dda049c5025ef93?d=identicon)[samikeijonen](/maintainers/samikeijonen) --- Top Contributors [![samikeijonen](https://avatars.githubusercontent.com/u/1820415?v=4)](https://github.com/samikeijonen "samikeijonen (635 commits)")[![justintadlock](https://avatars.githubusercontent.com/u/1816309?v=4)](https://github.com/justintadlock "justintadlock (66 commits)") --- Tags wordpress-starter-themewordpress-themewordpress ### Embed Badge ![Health badge](/badges/samikeijonen-uuups/health.svg) ``` [![Health](https://phpackages.com/badges/samikeijonen-uuups/health.svg)](https://phpackages.com/packages/samikeijonen-uuups) ``` ### Alternatives [roots/bedrock WordPress boilerplate with Composer, easier configuration, and an improved folder structure 6.5k441.8k2](/packages/roots-bedrock)[humanmade/s3-uploads WordPress plugin to store uploads on S3 2.1k2.4M9](/packages/humanmade-s3-uploads)[wp-media/wp-rocket Performance optimization plugin for WordPress 7431.3M3](/packages/wp-media-wp-rocket)[10up/elasticpress Supercharge WordPress with Elasticsearch. 1.3k374.3k6](/packages/10up-elasticpress)[roots/wp-stage-switcher WordPress plugin that allows you to switch between different environments from the admin bar 382435.0k3](/packages/roots-wp-stage-switcher)[vinkla/wordplate The WordPlate boilerplate 2.2k5.1k](/packages/vinkla-wordplate) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)