Front-end Development - Setting Up Foundation Access Theme:

  1. Install dependencies
  2. Git
  3. Node
  4. Npm
  5. SASS
  6. Grunt
  7. Bower
  8. git clone --recursive elmsln
  9. cd elmsln/system
  10. git pull origin master (or 1.x.x or whatever branch you want)
  11. cd core/dslmcode/shared/drupal-7.x/themes/elmsln_contrib/foundation_access/legacy
  12. npm install
  13. bower install
  14. grunt
  15. Work from Foundation Access theme directory in SublimeText
  16. SFTP grunt-compiled theme CSS, icons, or [template].tpl.php files into vagrant to make changes
  17. To make template changes to a sub-theme, you must also sftp the desired sub-theme's .tpl files into vagrant

Note: to work on the templates of the various sub-themes, navigate to elmsln/core/dslmcode/profiles/... As of now, due to the Zurb Foundation breakpoints mixins being compiled in Foundation Access, all theme CSS is handled in the Foundation Access theme, and templates (IE - page.tpl.php) are modified in the individual service sub-themes. Compiling SASS in a sub-theme and uploading the CSS would double the amount of CSS loaded for each theme and would override Foundation Access styles back to stock Zurb Foundation. Perhaps a better workflow can be figured out to distribute the css in a more efficient manner.

Service / Authority sub theming

For a starting point Sub-theme to work from, see core/dslmcode/profiles/ulmus-7.x-1.x/themes/SUB_foundation_access. Rename all SUB in the files to whatever the service name is. OR, if you are sub-theming a service's sub-theme then you can name this to whatever make sense for your group. Just make sure that the file is updated to reflect it being a sub-theme of a sub-theme.

Viewing an ELMSLN theme in a browser

  1. cd elmsln
  2. vagrant up
  3. To see the various themes in use: (combination of foundation_access and SERVICE_foundation_access themes)
  4. CIS: online.elmsln.local
  5. Course (MOOC) courses.elmsln.local/COURSENAMEHERE
  6. Media media.elmsln.local

Commit and Pull Request Instructions

  1. Fork the repo by clicking fork in the top right.
  2. take your changes you've worked on, overwrite the files in the fork repo
  3. create an issue in the issue queue
  4. commit to the fork repo using a commit message of the format #123: Issue Queue Title
  5. go to and click Pull requests.
  6. enter a description of the commit in the PR and issue it
  7. Wait for travis-ci to test to ensure the build passes, then wait for a maintainer to merge your PR
  8. Do a happy dance, you've made education better looking