Although your workflow will most likely vary based on the team you’re working with and some of the processes you already have in place for web development, we’ve listed several keys to think about when finding a workflow that is right for you and that fits the Moovweb development process.
We highly recommend using a version control system in your project workflow to take advantage of versioning and collaborative benefits. Moovweb is version control-agnostic, so you can pick any form of version control you want to integrate with your projects.
Moovweb recommends using an additional service other than the Moovweb cloud to host your code. Many developers use web-based services such as GitHub or Bitbucket to host their code and maintain synchronized codebases with their development team.
We refer to this separate service as the origin repository.
You can use the Moovweb cloud to setup both staging and production projects.
Staging projects can be used to test new changes you’ve made to your Moovweb experiences. Your team can test the site during the QA process by ensuring that the site is fully functional.
You can then deploy the same codebase to the production environment, which utilizes high-performing secure servers that handle all live traffic.
Here is what a typical development process with Moovweb may look like:
We recommend committing your code frequently. You can commit now, having just generated your project.
For example, this can be done in Git using:
$ git add . $ git commit -am "Initial commit"
For this course, we suggest committing whenever you’ve completed all the exercises in a given lesson.