Development

This section will cover how as college developer you can enhance your specific college website. Some examples are:

• Create new functionality (like an RSS news feed)

• Add/change banner images to your theme

• Change the CSS

• and more

This section covers setting up your local machine to pull you website locally to develop on, creating new web environments (multidev) to test with, submitting changes for moving ‘code’ to production, and other thing to help you in this process.

TODO:// Merge these paragraphs into one

In order for you to get your changes up so we can test them, you need to deploy a Multidev and apply your changes there first. Once your changes are on the Multidev, test them against the latest available upstream updates. Then a Merge Multidev to Dev request needs to be submitted in your college Slack channel. You can expect your changes to be on the development environment by the end of the next business day. After your changes pass our code review process we will apply your changes to the staging/test environment for further review. Expect your changes to move from stage to the production environment usually with the next morning code push if everything goes well with the further review on stage.

Adding banner images is accomplished through SCSS changes that require Developer access to your college website on the Pantheon platform. The process involves creating a Multidev branch of your college website, cloning the Multidev locally using GIT, making the SCSS changes and compiling them with a SASS compiler, testing your changes locally, and pushing them into your Multidev branch for further online testing. Once you have tested your changes on the Multidev, you can submit a merge request via Slack to have your changes merged to the development environment.

Further Reading

• Environments

• Local Development Stack

• Multidev

Related Articles

Select the table below to edit…

• Page:
  Webform
• Page:
  Local Development Stack