silverbackstudio / theme_svbk
Silverback _svbk Theme
Installs: 48
Dependents: 0
Suggesters: 0
Security: 0
Stars: 1
Watchers: 3
Forks: 3 119
Open Issues: 2
Language:JavaScript
Type:wordpress-theme
Requires
- silverback/wp-helpers: ^5.4.0
Requires (Dev)
- dev-master
- v3.x-dev
- v3.6.0
- v3.5.4
- v3.5.3
- v3.5.2
- 3.5.1
- 3.5.0
- 3.4.2
- 3.4.1
- 3.4.0
- 3.3.2
- 3.3.1
- 3.3.0
- 3.2.0
- 3.1.0
- 3.0.2
- 3.0.1
- 3.0.0
- v2.x-dev
- 2.1.0
- 2.0.2
- 2.0.1
- 2.0.0
- v1.x-dev
- 1.2.0
- 1.1.0
- 1.0.0
- dev-issues/packages-update
- dev-issues/wc-style
- dev-test
- dev-features/blocks-translations
- dev-issues/theme-handle-formatting
- dev-chore/names-and-code-style
- dev-features/wc-critical-css
- dev-features/global-assets-version
- dev-features/lighthouse-v6
- dev-develop
- dev-index-202068
- dev-critical-2020526
- dev-dev
- dev-class-refactor
- dev-removedeps
- dev-new-blocks
- dev-blocks
- dev-testimonials-block
- dev-blocks-styles
- dev-fix-02012019
- dev-alpha
- dev-woocommerce-sensei
- dev-speed-update
- dev-gutenberg-blocks
This package is auto-updated.
Last update: 2024-10-22 16:59:21 UTC
README
Hi. I'm a starter theme called _svbk
, a superset of the popular _s
theme. I'm a theme meant for hacking so don't use me as a Parent Theme. Instead try turning me into the next, most awesome, WordPress theme out there. That's what I'm here for.
On top of the standard _s
I feature:
Gulp
for real-time SASS compilingComposer
for dependancy management- An installer script
- Few extras and customizations that makes me less raw
My ultra-minimal CSS might make me look like theme tartare but that means less stuff to get in your way when you're designing your awesome theme. Here are some of the other more interesting things you'll find here:
- A just right amount of lean, well-commented, modern, HTML5 templates.
- A helpful 404 template.
- A custom header implementation in
inc/custom-header.php
just add the code snippet found in the comments ofinc/custom-header.php
to yourheader.php
template. - Custom template tags in
inc/template-tags.php
that keep your templates clean and neat and prevent code duplication. - An
editor.php
to add and customize TinyMCE's editor buttons - Some small tweaks in
inc/template-functions.php
that can improve your theming experience. - A script at
js/navigation.js
that makes your menu a toggled dropdown on small screens (like your phone), ready for CSS artistry. It's enqueued infunctions.php
. - 2 sample CSS layouts in
layouts/
for a sidebar on either side of your content. Note:.no-sidebar
styles are not automatically loaded. - Smartly organized starter CSS in
style.css
that will help you to quickly get your design off the ground. - Licensed under GPLv2 or later. :) Use it to make something cool.
Install
Install Dependencies
npm install
I you don't aready have a gulp installed, you should install it via:
npm install -g gulp
Setup
Edit the config.json
file and customize all the parameters, primarly the theme_name
and theme_handle
parameters.
Run gulp setup
, this builds all the dist
files and customizes all the functions names with your theme prefix.
Development
This theme has many gulp
tasks to help development, you can find all of them in the gulpfile.js
.
Here some of the most useful ones:
# Compile SASS, Images and JS in real time. gulp serve # Replaces all function prefixes and text-domains with `theme_handle`, useful after git merges. gulp replaceMarkers # Compiles and overwrites all the assets in the `dist` folder for production. gulp build
When you have completed your sprint, should bump the theme_version
config entry in composer.json
, this will be automatically added to all assets URLs to help cache-busting.
Block Editor (Gutenberg) Blocks
This theme comes with many Blocks, you can find them in the blocks
folder.
You can compile theme Blocks with:
# In real time while developing npm run blocks # To build the optimized production code npm run blocks:build
wp-env
This theme is compatible with the wp-env environment.
You can test or develop for this theme by running:
# To start the WP server npm run wp-env start # To refresh the wp-env after some options changes (WP_HOME, etc) npm run wp-env start -- --update # To stop the WP server npm run wp-env stop
The website will be available by default at http://localhost.
If you need to run wp-cli
commands you can use the npm run wp
script helper.
Example:
# Outputs the current env user list
npm run wp user list
The .wp-env.json
file contains the configuration for the environment, but if you need to customize it just for your current projects need it's better to create a .wp-env.override.json file that isn't committed in the repo.