{"_id":"57333d01a6a9c40e00e1396f","project":"56682f6c1fb5701900f893a0","category":{"_id":"5703c7f2903e330e002d8709","version":"5703c7f2903e330e002d8703","project":"56682f6c1fb5701900f893a0","__v":0,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-12-15T15:46:45.260Z","from_sync":false,"order":6,"slug":"web-professionals","title":"Web Professionals"},"user":"56684a10ee1dbf0d008f621d","__v":15,"parentDoc":null,"version":{"_id":"5703c7f2903e330e002d8703","__v":4,"hasDoc":true,"hasReference":true,"project":"56682f6c1fb5701900f893a0","createdAt":"2016-04-05T14:13:06.422Z","releaseDate":"2016-04-05T14:13:06.422Z","categories":["5703c7f2903e330e002d8704","5703c7f2903e330e002d8705","5703c7f2903e330e002d8706","5703c7f2903e330e002d8707","5703c7f2903e330e002d8708","5703c7f2903e330e002d8709","5703c7f2903e330e002d870a","5703c7f2903e330e002d870b","5703c7f2903e330e002d870c","573d96148ca48f320093ed5b","573dd2e38cf1492400bba6e0","57a9cc1f5b1ace0e00de743e"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"2.0.0","version":"2"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-05-11T14:09:05.002Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":1,"body":"[block:callout]\n{\n  \"type\": \"info\",\n  \"body\": \"Familiarity with HTML/CSS, terminal, Git and other web technologies is required.\",\n  \"title\": \"This document is for web professionals\"\n}\n[/block]\n##Contents\n1. Basic Terminal Commands\n2. Partner environments\n\t1. Partner types\n\t2. Brands / packages\n\t3. Template tagging\n\n##1: Basic Terminal Commands\n\n###Git Commands\n*You should expect to be familiar with these terminal commands*\nOpen the 'Terminal' application. By default you will be looking at your local user directory (e.g. dominics-imac:~ DominicHickey…)\n\n**Enter a local folder: **\n`cd foldername`\n\n**Previous folder:**\n`cd ..`\n\n**Cloning a Repository**\n`git clone repositoryurl` \n\n**Check the Repository Status**\n`git status`\n\n**Make a Commit:**\n```\ngit add .\ngit commit -am \"Your commit message goes here\"\n```\n\n**Push a Commit**\n`git push origin branchname`\n\n**Pull a Repository**\n`git pull origin branchname`\n\n**Switching Branch**\n`git checkout branchname`\n\n**Create a New Branch**\n`git checkout -b newbranchname`\n\n**Track an existing Branch**\n```\ngit fetch -a\ngit checkout -b branchname --track origin/branchname\ngit pull origin branchname\n```\n**Temporarily Save Changes**\n`git stash`\n \n\f\n##2. Partner Environments\n\n**Partner types**\n  * On-premise: have their own environment / control panel\n  * SaaS: shared partner environment\n     * EMEA (bkpam2)\n     * US (bk-paus)\n     * Asia (bkasia)\n\n**Brands / packages**\n  * An environment can have multiple brands. A brand is typically used for partner campaigns that could be directed at different groups of customers.\n  * Within a brand, there are packages. These are pulled in from the manifest, e.g. SaaS US 25: 10 Standard + 5 Blog + 5 Menu + 5 Ecommerce. \n  * Template groups within packages relate to the manifest groups\n\n**Tagging templates**\n  * During the build process, templates are automatically tagged for partner releases. \n  * Prior to V7.79, templates are tagged as the minor version number (e.g. 78)\n     * E.g. https://github.com/basekit-templates/kings/tree/78\n  * From V79+, templates are tagged as the full version (e.g. 7.79)\n     * E.g. https://github.com/basekit-templates/kings/tree/7.81","excerpt":"Process information for design teams using BaseKit applications","slug":"design-process-training","type":"basic","title":"Design Process Training"}

Design Process Training

Process information for design teams using BaseKit applications

[block:callout] { "type": "info", "body": "Familiarity with HTML/CSS, terminal, Git and other web technologies is required.", "title": "This document is for web professionals" } [/block] ##Contents 1. Basic Terminal Commands 2. Partner environments 1. Partner types 2. Brands / packages 3. Template tagging ##1: Basic Terminal Commands ###Git Commands *You should expect to be familiar with these terminal commands* Open the 'Terminal' application. By default you will be looking at your local user directory (e.g. dominics-imac:~ DominicHickey…) **Enter a local folder: ** `cd foldername` **Previous folder:** `cd ..` **Cloning a Repository** `git clone repositoryurl` **Check the Repository Status** `git status` **Make a Commit:** ``` git add . git commit -am "Your commit message goes here" ``` **Push a Commit** `git push origin branchname` **Pull a Repository** `git pull origin branchname` **Switching Branch** `git checkout branchname` **Create a New Branch** `git checkout -b newbranchname` **Track an existing Branch** ``` git fetch -a git checkout -b branchname --track origin/branchname git pull origin branchname ``` **Temporarily Save Changes** `git stash` ##2. Partner Environments **Partner types** * On-premise: have their own environment / control panel * SaaS: shared partner environment * EMEA (bkpam2) * US (bk-paus) * Asia (bkasia) **Brands / packages** * An environment can have multiple brands. A brand is typically used for partner campaigns that could be directed at different groups of customers. * Within a brand, there are packages. These are pulled in from the manifest, e.g. SaaS US 25: 10 Standard + 5 Blog + 5 Menu + 5 Ecommerce. * Template groups within packages relate to the manifest groups **Tagging templates** * During the build process, templates are automatically tagged for partner releases. * Prior to V7.79, templates are tagged as the minor version number (e.g. 78) * E.g. https://github.com/basekit-templates/kings/tree/78 * From V79+, templates are tagged as the full version (e.g. 7.79) * E.g. https://github.com/basekit-templates/kings/tree/7.81