Stanford Basic Branding Theme.
This package is auto-updated.
Last update: 2023-08-13 19:09:24 UTC
Primary development for the Stanford Basic theme has been consolidated and moved to the Stanford Profile.
Stanford Basic is a Stanford Branded Drupal 9 base theme that integrates with the Decanter Project.
Evaluation Date: 2020-02-05 This theme conforms to level AA WCAG 2.0 standards as required by the university's accessibility policy. For more information on the policy please visit: https://ucomm.stanford.edu/policies/accessibility-policy.html.
Install this theme like any other theme. See Drupal Documentation
This theme depends on the
Components module to register template
namespaces. If downloading this theme via composer, the module is already downloaded and simply needs to be enabled
before the theme can be enabled.
If using this theme in conjunction with configuration management and doing site install, a patch is included in the composer.json. Ensure that your project's root composer.json has patching enabled or download and patch Drupal Core manually.
Nothing special needed. Install, enable, and set as the default active theme. Once you have the theme enabled, be sure to check out the appearance settings for additional configuration items.
If you are experiencing issues with this theme try disabling and clear the cache first. If you are still experiencing issues try posting an issue on the GitHub issues page.
This theme is not intended to be used as an administration theme. Please use something else for that.
nvm use npm install
npm run publish
This script will compile all assets from
package.json for additional npm scripts and functionality.
You are welcome to contribute functionality, bug fixes, or documentation to this theme. 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
Steps to build a new release:
- Checkout the latest commit from the
- 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.ymlfiles, 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
- Give the PR a semver-compliant label, e.g., (
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.