wprig | A progressive theme development rig for WordPress | Content Management System library
kandi X-RAY | wprig Summary
kandi X-RAY | wprig Summary
wprig is a PHP library typically used in Telecommunications, Media, Media, Entertainment, Web Site, Content Management System, Wordpress applications. wprig has no bugs, it has no vulnerabilities, it has a Strong Copyleft License and it has medium support. You can download it from GitHub.
A progressive theme development rig for WordPress.
A progressive theme development rig for WordPress.
Support
Quality
Security
License
Reuse
Support
wprig has a medium active ecosystem.
It has 1245 star(s) with 275 fork(s). There are 69 watchers for this library.
It had no major release in the last 12 months.
There are 98 open issues and 373 have been closed. On average issues are closed in 406 days. There are 8 open pull requests and 0 closed requests.
It has a neutral sentiment in the developer community.
The latest version of wprig is v2.2.1
Quality
wprig has 0 bugs and 0 code smells.
Security
wprig has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
wprig code analysis shows 0 unresolved vulnerabilities.
There are 0 security hotspots that need review.
License
wprig is licensed under the GPL-3.0 License. This license is Strong Copyleft.
Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.
Reuse
wprig releases are available to install and integrate.
Installation instructions, examples and code snippets are available.
wprig saves you 1793 person hours of effort in developing the same functionality from scratch.
It has 4093 lines of code, 175 functions and 117 files.
It has medium code complexity. Code complexity directly impacts maintainability of the code.
Top functions reviewed by kandi - BETA
kandi has reviewed wprig and discovered the below as its top functions. This is intended to give you an instant insight into wprig implemented functionality, and help decide if they suit your requirements.
- Add editor support .
- Get css files .
- Get default js files .
- Render the comments list .
- Set template tags .
- Returns default components
- Get a component by its slug .
Get all kandi verified functions for this library.
wprig Key Features
No Key Features are available at this moment for wprig.
wprig Examples and Code Snippets
No Code Snippets are available at this moment for wprig.
Community Discussions
Trending Discussions on wprig
QUESTION
WP Rig: Error running npm run build: Cannot find "/vendor/bin/phpcs"
Asked 2020-Jun-22 at 19:00
I've installed WP Rig on a Windows development machine running WAMPserver.
I get to Step 5 at the URL above where I need to run npm run build, and then I receive an error:
...
ANSWER
Answered 2020-Jun-22 at 19:00Revert changes to composer.json file relating with the custom phpcs-dev script.
Your composer.json should have phpcs-dev script to be:
QUESTION
Using git rebase, how to squash a commit into a non-previous commit
Asked 2020-Jan-10 at 13:21
I know that using git rebase -i, I could squash a commit which will meld the commit message into the immediate previous commit.
https://github.com/wprig/wprig/wiki/How-to-squash-commits
But using git rebase -i, is it possible to squash a commit into not the previous commit but a commit even older? Lets say I want to squash a commit with a commit that is 3 commits prior to the commit being squashed. If yes, then how?
ANSWER
Answered 2020-Jan-10 at 13:21when you use git rebase -i you are able to reorder the commit if you want to a new order.
If you e.g. do git rebase -i HEAD~5 and end with this:
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install wprig
WP Rig has been tested on Linux, Mac, and Windows.
Here is an example of creating a custom theme config file for the project. In this example, we want a custom slug, name, and author. Place the following in your ./config/config.json file. This config will be versioned in your repo, so all developers use the same settings. Some theme settings should only be set for your local environment. For example, if you want to set local information for BrowserSync. Place the following in your ./config/config.local.json file. This config will not be tracked in your repo and will only be executed in your local development environment.
Clone or download this repository to the themes folder of a WordPress site on your development environment. DO NOT give the WP Rig theme directory the same name as your eventual production theme. Suggested directory names are wprig or wprig-themeslug. For instance, if your theme will eventually be named “Excalibur” your development directory could be named wprig-excalibur. The excalibur directory will be automatically created during the production process and should not exist beforehand.
Configure theme settings, including the theme slug and name. View ./config/config.default.json for the default settings. Place custom theme settings in ./config/config.json to override default settings. You do not have to include all settings from config.default.json. Just the settings you want to override. Place local-only theme settings in ./config/config.local.json, e.g. potentially sensitive info like the path to your BrowserSync certificate. Again, only include the settings you want to override.
In the command line, run npm run rig-init to install necessary node and Composer dependencies.
In the command line, run npm run dev to process source files, build the development theme, and watch files for subsequent changes. npm run build can be used to process the source files and build the development theme without watching files afterwards.
In WordPress admin, activate the WP Rig development theme.
Follow the steps above to install WP Rig.
Run npm run bundle from inside the wp-rig development theme.
A new, production-ready theme will be generated in wp-content/themes.
The production theme can be activated or uploaded to a production environment.
Here is an example of creating a custom theme config file for the project. In this example, we want a custom slug, name, and author. Place the following in your ./config/config.json file. This config will be versioned in your repo, so all developers use the same settings. Some theme settings should only be set for your local environment. For example, if you want to set local information for BrowserSync. Place the following in your ./config/config.local.json file. This config will not be tracked in your repo and will only be executed in your local development environment.
Clone or download this repository to the themes folder of a WordPress site on your development environment. DO NOT give the WP Rig theme directory the same name as your eventual production theme. Suggested directory names are wprig or wprig-themeslug. For instance, if your theme will eventually be named “Excalibur” your development directory could be named wprig-excalibur. The excalibur directory will be automatically created during the production process and should not exist beforehand.
Configure theme settings, including the theme slug and name. View ./config/config.default.json for the default settings. Place custom theme settings in ./config/config.json to override default settings. You do not have to include all settings from config.default.json. Just the settings you want to override. Place local-only theme settings in ./config/config.local.json, e.g. potentially sensitive info like the path to your BrowserSync certificate. Again, only include the settings you want to override.
In the command line, run npm run rig-init to install necessary node and Composer dependencies.
In the command line, run npm run dev to process source files, build the development theme, and watch files for subsequent changes. npm run build can be used to process the source files and build the development theme without watching files afterwards.
In WordPress admin, activate the WP Rig development theme.
Follow the steps above to install WP Rig.
Run npm run bundle from inside the wp-rig development theme.
A new, production-ready theme will be generated in wp-content/themes.
The production theme can be activated or uploaded to a production environment.
Support
We have a new Documentation area that can be found on the WP Rig website. If you would like to contribute to our documentation efforts, please submit a request on our contribute page on our website.
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page
