This tool is used to run the UX Team's build tools. Additionally, it can scaffold out a basic site structure if one does not already exist.
A one-time setup can be run to automatically get the requirements and to install the ux-cli tool. There are seperate commands to run on OS X and Windows.
Running the command below in a terminal will install Nvm, Node, and ux-cli (if needed). You may need to run this as
sudo user and enter your password.
bash -c "$(curl )"
Running the command below at your command prompt will install Git and Node (if needed), setup Git to use 'https' instead of 'ssh', and then install the latest version of ux-cli as a global package.
After the install is complete, you will need to close that command prompt window and open a new one before the tools are available for use.
@powershell -NoProfile -ExecutionPolicy unrestricted -Command "$wc=new-object net.webclient;$wc.DownloadString('') | iex"
Node v4.x.x is required. Node can be installed from: http://nodejs.org.
UX-CLI can be installed by opening your terminal (Command line in Windows) and running:
npm install -g @unumux/ux-cli
After installation of the tool, the tool can be used by using 'cd' to navigate to the folder you want to run the UI-Framework from and typing "ux".
On first run, the tool will ask several questions to create the configuration file. An explanation of each of those questions is below.
This requires a yes if you want to continue. It will install the UI-Framework in the current directory.
This is also required (and likely soon to be removed). It uses the following questions to create a ux.json configuration file.
This question is only asked if the tool is run in an empty folder. If you choose "Y", it will create a basic HTML, JS, and SCSS file.
The tool scans the folder for subfolders which contain SCSS files. If there are multiple folders with SCSS files, it will prompt you to choose the correct one.
The tool scans the folder for subfolders which contain JS files. If there are multiple folders with JS files, it will prompt you to choose the correct one.
These files, when changed, will trigger the browser to refresh. Automatically searches for HTML, ASPX, and CSS files.
If using Browserify, a "main" JS file is required. This file is the one that will be passed into Browserify. Multiple files are not yet supported.
If this is a Sitecore or ASP.NET site, you should answer no to this. Otherwise, answer yes.
Choose additional libraries to install. These are not automatically inserted into your styles, markup, or scripts. You will need to @import them for stylesheets. For example, to use colonial-branding in your SCSS files, type:
If you are using browserify, using JS files is just as easy. For example, to use jQuery, just type:
var $ = require "jquery";
If you are not using Browserify, or if you have any files that aren't SCSS/JS, then they will need to be copied from Bower to a folder in your project and then included using the appropriate tag inside of your markup.
The tool supports several options
Setup global login information.
This option allows you to recreate the ux.json configuration file. This is not needed if a ux.json file does not already exist
By default, the tool automatically installs npm and bower dependencies. This option will prevent those installs from running. Same as running
ux --no-bower --no-npm
--no-packages, but only disabled bower installations
--no-packages, but only disables npm installation.
UX can be passed the name of a gulp task, and it will pass it to gulp. For example,
ux styles would run a single SASS compilation.
During initial project setup, UX asks for a list of packages to install (such as colonial-branding and jQuery). This process can be run at a later time by using the --install switch.