initialize 1.1.0

Automating Automation by creating automatic project structure

.. raw:: html

<h1 style="text-align:center; text-decoration:underline;color:green"> Initialize </h1>

A Template Project Creator for python, html, css, Javascript, Wordpress Plugin, Wordpress Theme

Benifits
--------

* Auto Creation Of Standard Document Structure
* Pre Initialised Git Repository
* Addition of Remote Repository After initialization
* Additon Of Tags From 0.1.0
* A Hour Start

Installation
============

The `Python Packaging Guide`_ contains general information about how to manage
your project and dependencies.

.. _Python Packaging Guide: https://packaging.python.org/current/

Released version
----------------

Install or upgrade using pip. ::

pip install -U initialize

Development
-----------

The latest code is available from `GitHub`_. Clone the repository then install
using pip. ::

git clone https://github.com/AngrySoilder/initialize
pip install -e ./initialize

Or install the latest build from an `archive`_. ::

pip install -U https://github.com/AngrySoilder/initialize/tarball/master

.. _GitHub: https://github.com/AngrySoilder/initialize
.. _archive: https://github.com/AngrySoilder/initialize/archive/master.tar.gz


Usage
=====

.. code-block:: bash

initialize javascript # initialize javascript library File Structure
initialize python # initial standard python package structure
initialize html # Html Library Structure
initialize shtml # Simple Html Css Javascript Website Structure
initialize wp_theme # Simple Wordpress Theme Development Structure
initialize wp_plugin # Simple Wordpress Plugin Development Structure



Contributing
=============

One Can Contribute to this project by **creating a issue at issue** at `https://github.com/AngrySoilder/initialize` Or **creating a pull request**

Pull Request Process
--------------------

1. Ensure any install or build dependencies are removed before the end of the layer when doing a
build.
2. Checkout pull requests list at `https://github.com/AngrySoilder/initialize/pulls` to ensure that you are not dublicating anybody's work
3. Update the README.md with details of changes to the interface, this includes new environment
variables, exposed ports, useful file locations and container parameters.
4. Increase the version numbers in any examples files and the README.md to the new version that this
Pull Request would represent. The versioning scheme we use is [SemVer](http://semver.org/).
5. You may merge the Pull Request in once you have the sign-off of by other developers, or if you
do not have permission to do that, you may request the one of maintainers of project to merge it for you.

Development Process
-------------------

* Create a local copy of repository in our machiene
* Install dependencies which are currently used by project
* Make Changes To your Project
* Write atleast Basic Test which covers your changes
* Improve docs with your changes
* Create a coverage report
* Pull...

How To issue
------------
While registering a issue it will be beneficial if creator of issue desribe following things about issue

* operating system he used
* steps to generte error or bug
* if not know steps in what function or method bug generated