Installation Profile for the Stanford VPGE.

Installs: 432

Dependents: 0

Suggesters: 0

Security: 0

Stars: 0

Watchers: 5

Forks: 1


11.2.0 2024-02-20 22:33 UTC





This is a fork main installation profile for VPGE platform.


WCAG Conformance 2.0 AA Badge This module conforms to level AA WCAG 2.0 standards as required by the university's accessibility policy. For more information on the policy please visit:


Install this installation profile like any other profile. See Drupal Documentation


There are config split configuration settings for their respective sites. Their configs exist in config/splits directory. These splits get enabled through settings.php files on their respective sites.

When creating any new custom configs (fields, views, content types, etc), prefix them with vpge. This will allow the config splits to export the configuration into the proper directory.

Upstream updates

Pull from stanford_profile by running the command git pull 11.x -X ours --no-edit.

There is possibly going to be some conflicts. Clear up those conflicts and commit the changes.


Steps to build a new release:

  • Checkout the latest commit from the 11.x branch.
  • Create a new branch for the release.
  • Commit any necessary changes to the release branch.
    • These may include, but are not necessarily limited to:
    • Update the version in any info.yml files, including in any submodules.
    • Update the CHANGELOG to reflect the changes made in the new release.
  • Make a PR to merge your release branch into master
  • Give the PR a semver-compliant label, e.g., (patch, minor, major). This may happen automatically via Github actions (if a labeler action is configured).
  • When the PR is merged to master, a new tag will be created automatically, bumping the version by the semver label.
  • The github action is built from: semver-release-action, and further documentation is available there.


If you are experiencing issues with this try posting an issue on the GitHub issues page.

Contribution / Collaboration

You are welcome to contribute functionality, bug fixes, or documentation to this module. If you would like to suggest a fix or new functionality you may add a new issue to the GitHub issue queue or you may fork this repository and submit a pull request. For more help please see GitHub's article on fork, branch, and pull requests