Proper setup of a project based on Basis requires some common steps, such as setting up wordpress, forking this as a theme, configuring the database, and so on.
Deploying to staging or production (typically, from the develop or master branch, respectively) expects a few steps:
- Update the Changelog.
grunt changeloghas a lot of options for the curious. - Commit your changes, ensuring they're merged to
developormaster, as appropriate. Push them.git push origin developfor instance. - Update the version, which pushes the tag to the server.
grunt bumpcan take:patchor:minoror:majorfor example. - Deploy to the server via SFTP. Expect
grunt deployto handle this, but you have to set up logins and stuff. - Ideally, notify others of this deployment. Haven't figured this piece out yet.
Generally you will use the following tasks:
watch- This is the default task. Does the live reload stuff.build- This is how you build the site on your laptop. Alias for "sass", "autoprefixer", "uglify", "imagemin" tasks.stage- This is how you would get stuff ready for the staging server. This task is not yet complete and/or useful. Alias for "build", "bump", "changelog", "deploy" tasks.
Please add notes here as you learn how to get the FTP working and so forth. My stage task is a first attempt at making something so you can deploy the site, and it does all the appropriate tagging, changelog-generation, building files, committing and pushing, and FTP deploying.
We started with Underscores, and because of that, you'll want to replace needmore (not _s) in the following way if you need to rename the theme.
- Search for:
'needmore'and replace with:'megatherium' - Search for:
needmore_and replace with:megatherium_ - Search for:
Text Domain: needmoreand replace with:Text Domain: megatheriumin style.css. - Search for:
needmoreand replace with:Megatherium - Search for:
needmore-and replace with:megatherium-
Then, update the stylesheet header in style.css and the links in footer.php with your own information. Next, update or delete this readme.