| 1 |
# Content Control |
| 2 |
Content Control is a lightweight and powerful plugin that allows you to take complete control of your website’s content by restricting access to pages/posts to logged in users, specific user roles or to logged out users. |
| 3 |
|
| 4 |
Feel free to browse the code and make suggestions/requests. Thanks! |
| 5 |
|
| 6 |
## Getting Started |
| 7 |
|
| 8 |
### Downloading And Using As A Plugin |
| 9 |
To use this plugin, this repo can be downloaded as a zip and installed as-is as a WordPress plugin. Once installed and activated, Go to wp-admin > Appearance > Menus and edit your menu. |
| 10 |
|
| 11 |
### Getting Set Up For Development |
| 12 |
|
| 13 |
#### Prerequisites |
| 14 |
In order to run our Gulp tasks, you will need Node.js and NPM installed. To do so, you can [](https://docs.npmjs.com/downloading-and-installing-node-js-and-npmfollow the NPM documentation's guide](https://docs.npmjs.com/downloading-and-installing-node-js-and-npm](https://docs.npmjs.com/downloading-and-installing-node-js-and-npm). |
| 15 |
If you have not used NPM before, you can [](https://www.sitepoint.com/beginners-guide-node-package-manager/refer to this beginner's guide to NPM](https://www.sitepoint.com/beginners-guide-node-package-manager/](https://www.sitepoint.com/beginners-guide-node-package-manager/). |
| 16 |
|
| 17 |
This plugin uses a series of [](https://gulpjs.comGulp](https://gulpjs.com](https://gulpjs.com) tasks to clean and prepare builds. To get started, run `npm install` to get the necessary gulp dependencies. |
| 18 |
|
| 19 |
#### Gulp Tasks |
| 20 |
As normal, we have our gulp tasks in the gulpfile.js file. |
| 21 |
|
| 22 |
Task info coming soon.... |
| 23 |
|
| 24 |
## Built With |
| 25 |
* [](https://sass-lang.comSASS](https://sass-lang.com](https://sass-lang.com) - The CSS pre-processor we use. We use the SCSS syntax. |
| 26 |
|
| 27 |
## Deployment |
| 28 |
This is a WordPress plugin that is hosted on the WordPress.org SVN repo. |
| 29 |
There is not currently any automated deployment. Instead, once a release is published on GitHub, that release is manually uploaded to the SVN. |
| 30 |
|
| 31 |
## Contributing |
| 32 |
Community made feature requests, patches, localizations, bug reports, and contributions are always welcome and are crucial to ensure Content Control continues to grow. |
| 33 |
|
| 34 |
When contributing please ensure you follow the guidelines below so that we can keep on top of things. |
| 35 |
|
| 36 |
Please Note: GitHub is not intended for support based questions. For those, please use the [](https://wordpress.org/plugins/content-control/support forums](https://wordpress.org/plugins/content-control/](https://wordpress.org/plugins/content-control/). |
| 37 |
|
| 38 |
### Creating Issues |
| 39 |
* If you have any bugs or feature requests, please [](https://github.com/JunglePlugins/Content-Control/issues/newcreate an issue](https://github.com/JunglePlugins/Content-Control/issues/new](https://github.com/JunglePlugins/Content-Control/issues/new) |
| 40 |
* For bug reports, please clearly describe the bug/issue and include steps on how to reproduce it |
| 41 |
* For feature requests, please clearly describe what you would like, how it would be used, and example screenshots (if possible) |
| 42 |
|
| 43 |
### Pull Requests |
| 44 |
* Ensure you stick to the [](https://codex.wordpress.org/WordPress_Coding_StandardsWordPress Coding Standards](https://codex.wordpress.org/WordPress_Coding_Standards](https://codex.wordpress.org/WordPress_Coding_Standards) |
| 45 |
* When committing, reference your issue (if present) and include a note about the fix |
| 46 |
* Push the changes to your fork and submit a pull request to the 'master' branch of this repository |
| 47 |
* We are trying to ensure that every function is documented well and follows the standards set by phpDoc going forward |
| 48 |
|
| 49 |
## Versioning |
| 50 |
We use [](http://semver.org/SemVer](http://semver.org/](http://semver.org/) for versioning. For the versions available, see [](https://github.com/JunglePlugins/Content-Control/releasesthe releases in this repository](https://github.com/JunglePlugins/Content-Control/releases](https://github.com/JunglePlugins/Content-Control/releases). |
| 51 |
|
| 52 |
## Developers |
| 53 |
* Daniel Iser - Lead Developer |
| 54 |
|
| 55 |
See also [](https://github.com/JunglePlugins/Content-Control/graphs/contributorsthe list of contributors](https://github.com/JunglePlugins/Content-Control/graphs/contributors](https://github.com/JunglePlugins/Content-Control/graphs/contributors) who participated in this project. |
| 56 |
|
| 57 |
## License |
| 58 |
This project is licensed under the GPLv3 License. |
| 59 |
|
| 60 |
## Support |
| 61 |
This is a developer's portal for Content Control and **should not** be used for support. Please [](https://wordpress.org/plugins/content-control/create a support ticket here](https://wordpress.org/plugins/content-control/](https://wordpress.org/plugins/content-control/). |
| 62 |
|
