↓Skip to main content
Dessky.org Dessky.org
  1. All Posts/

wpboot

Tools Open Source PHP WordPress 



<p>
  </a>
</p>

<h1 align="center" dir="auto">
  <a rel="nofollow noopener" target="_blank" id="user-content---------wpboot-cli----" class="anchor" aria-hidden="true" href="#--------wpboot-cli----"></a><br /> WPboot CLI<br />
</h1>

<h1 dir="auto">
  <a rel="nofollow noopener" target="_blank" id="user-content-wpboot" class="anchor" aria-hidden="true" href="#wpboot"></a>wpboot
</h1>

<p>
  WPboot is A Free and OpenSource Lightweight CLI app to bootstrap WordPress Theme and Plugin Development created by @zaghadon.<br /> This repository is the official repository for <code>wpboot</code> and a continuation of the previous Themeboot project.
</p>

<h2 dir="auto">
  <a rel="nofollow noopener" target="_blank" id="user-content-why-wpboot" class="anchor" aria-hidden="true" href="#why-wpboot"></a>Why wpboot
</h2>

<p>
  I build Plugins and Themes as a freelancer for different people and want to quickly start off with a simple project scaffold that is why I created wpboot, to help me start a new project easily by simply supplying the details of the Project and Initializing it in a boilerplate; if you use it and you like it, Just send me your project link let me list it on the <code>Created with</code>. Thank you <3
</p>

<h1 dir="auto">
  <a rel="nofollow noopener" target="_blank" id="user-content-getting-started" class="anchor" aria-hidden="true" href="#getting-started"></a>Getting Started
</h1>

<p>
  You&#8217;ll need <code>php-cli</code>, <a rel="nofollow noopener" target="_blank" href="https://getcomposer.org/">Composer</a> and A local <a rel="nofollow noopener" target="_blank" href="https://wordpress.org">WordPress</a> installation to get started.<br /> <strong>Simple Installation:</strong><br /> There are 2 easy ways to install WPBoot in your computer.
</p>

<p>
  First and the recommended way is through Composer Global Require, One Line Command.<br /> Make sure to place Composer&#8217;s system-wide vendor bin directory in your $PATH so the wpboot executable can be located by your system.<br /> This directory exists in different locations based on your operating system; however, some common locations include:<br /> macOS: <code>$HOME/.composer/vendor/bin</code><br /> Windows: <code>%USERPROFILE%AppDataRoamingComposervendorbin</code><br /> GNU / Linux Distributions: <code>$HOME/.config/composer/vendor/bin or $HOME/.composer/vendor/bin</code>
</p>

<p>
  Show me how<br /> If it&#8217;s not already there, add the following line to your Bash configuration file (usually <code>~/.bash_profile</code>, <code>~/.bashrc</code>, <code>~/.zshrc</code>, etc.):
</p>

<pre class="notranslate"><code>export PATH=~/.composer/vendor/bin:$PATH


<p>
  If the file doesn&#8217;t exist, create it.<br /> Run the following command on the file you&#8217;ve just updated for the change to take effect:
</p>

<pre class="notranslate"><code>source ~/.bash_profile


<p>
  You could also find the composer&#8217;s global installation path by running <code>composer global about</code> and looking up from the first line.
</p>

<p>
  TO INSTALL:
</p>

<ul dir="auto">
  <li>
    Run <code>composer global require topazdom/wpboot</code> to install WPboot Globally in your computer.
  </li>
  <li>
    Run <code>wpboot</code> to verify successful installation.
  </li>
</ul>

<p>
  Another Way is to clone the project directly to your computer. Change Directory to the cloned project and Install composer dependency.
</p>

<ul dir="auto">
  <li>
    Run <code>git clone https://github.com/topazdom/wpboot.git</code>
  </li>
  <li>
    Run <code>cd wpboot</code>
  </li>
  <li>
    Run <code>composer install</code>
  </li>
</ul>

<p>
  Manually export wpboot binary to your PATH to make it available globally by:
</p>

<ul dir="auto">
  <li>
    Windows : Adding the path to <code>wpboot</code> to system PATH variable.
  </li>
  <li>
    Linux : Run <code>sudo ln -s /usr/local/bin/wpboot /path/to/wpboot</code> replacing path to with your wpboot installation location. This would create a symlink between your local global bin folder and wpboot executable binary.
  </li>
  <li>
    Mac: Run <code>echo 'export PATH="$PATH:$HOME/path/to/wpboot"' &gt;&gt; ~/.zshrc</code> to export the binary to PATH. You&#8217;ll need to restart the terminal for the new bash file to take effect.
  </li>
  <li>
    Run <code>wpboot</code> to verify successful installation.
  </li>
</ul>

<p>
  <strong>Simple Usage:</strong><br /> Change Directory to the theme or plugin Folder of your wordpress installation.
</p>

<pre class="notranslate"><code>`cd **/wp-content/themes/` OR  `cd **/wp-content/plugins/`.

FOR THEME

Initialize new Theme development From a theme file directory. wpboot theme This would initialize the boilerplate scaffolding in the current directory or folder.

If Running from the /themes/ directory, specify theme folder name using the folder parameter e.g wpboot theme folder="newtheme" This would create the folder and initialize the boilerplate scaffolding in the created directory or folder.

FOR PLUGIN

Initialize new Plugin Development From the Plugin Directory wpboot plugin make sure you provide accurate plugin folder name in the Text Domain Field as this would be used programmatically to help you follow accordingly with the WordPress Naming Standards. 

<h1 dir="auto">
  <a rel="nofollow noopener" target="_blank" id="user-content-contributing" class="anchor" aria-hidden="true" href="#contributing"></a>Contributing
</h1>

<p>
  Contributions are very welcome! You can contribute with code, documentation, filing issues&#8230;
</p>

<h1 dir="auto">
  <a rel="nofollow noopener" target="_blank" id="user-content-to-do" class="anchor" aria-hidden="true" href="#to-do"></a>TO DO
</h1>

<ul dir="auto">
  <li>
    Plan and Write Unit Tests for testing the commands.
  </li>
  <li>
    Enforce compliance during inputs, by validating inputs and securing users against themselves.
  </li>
  <li>
    Help Share to many WordPress Developers communities.
  </li>
  <li>
    Star and Watch to keep up with the evoluton.
  </li>
</ul>

<h1 dir="auto">
  <a rel="nofollow noopener" target="_blank" id="user-content-credits" class="anchor" aria-hidden="true" href="#credits"></a>Credits
</h1>

<ul dir="auto">
  <li>
    WP Theme Scaffold created by @krafthaus_ is based on Underscores <a rel="nofollow noopener" target="_blank" href="http://krafthaus.co.id/">http://krafthaus.co.id/</a>, (C) 2012-2016 Automattic, Inc.<br /> Underscores is distributed under the terms of the GNU GPL v2 or later.
  </li>
  <li>
    <a rel="nofollow noopener" target="_blank" href="https://wppb.io">WordPressPluginBoilerplate</a> A foundation for WordPress Plugin Development that aims to provide a clear and consistent guide for building your plugins.<br /> A standardized, organized, object-oriented foundation for building high-quality WordPress Plugins.
  </li>
  <li>
    Minicli is an experimental dependency-free toolkit for building CLI-centric applications in PHP.<br /> Minicli was created as <a rel="nofollow noopener" target="_blank" href="https://dev.to/erikaheidi/bootstrapping-a-cli-php-application-in-vanilla-php-4ee">an educational experiment</a> and a way to go dependency-free when building simple command-line applications in PHP. It can be used for microservices, personal dev tools, bots and little fun things.
  </li>
</ul>

<h1 dir="auto">
  <a rel="nofollow noopener" target="_blank" id="user-content-created-with-wpboot" class="anchor" aria-hidden="true" href="#created-with-wpboot"></a>Created with WPboot
</h1>

<ul dir="auto">
  <li>
    Themester &#8211; a Multipurpose WordPress Theme for building beautiful dynamic&#8230;
  </li>
</ul>
↑