Cloning the Repository as a Git Submodule ![]() Feel free to move this anywhere, but please make note of where it’s stored. This will clone the Redux master repository into a folder called ReduxFramework. Using the Linux command line, type the following: cd my-project Assuming you now have a working understanding of Git, here is how to clone the master branch of Redux. For a more thorough understanding of Git, another excellent resource is Pro Git. If this is the case, it’s recommended beginners read Git Immersion. If you’re not familiar with Git, using this method can be a bit daunting. Grabbing it will result in the best possible experience for your clients. Our master branch is designed to be the most stable, up-to-date code. Installation through Git allows ensures you’ll always have the latest version of Redux. Redux may be placed into any directory or in any path (such as ~/admin or ~/framework). It’s important to choose a name for the folder in which Redux will be contained, as it could be difficult to change the name later. Here we’ll go over a few more advanced git methods. There are a variety of methods in which to acquire the Redux Framework source code. Let’s begin, shall we? Step 1: Get the Source ![]() This means your clients could – hypothetically – receive updates to Redux without any theme update from you. Even better, the Redux plug-in will always supersede your theme’s require of Redux. You might be wondering, what if your client also installs the Redux plugin? Will it conflict? The answer is no. Embedding Redux into your theme or plugin is as easy as 1, 2, 3. And of course you love Redux because – let’s face it – who doesn’t? You understand how the Redux plug-in works, but the concept of a theme or plugin installing another plugin escapes you, or perhaps you don’t really care for TGM or any of its variations. So you have this really cool Theme or Plugin.
0 Comments
Leave a Reply. |