- Based on _s theme (underscores)
- Implements the elements styleguide
- Uses shortcodes to display special content served by EPFL APIs.
- production build files of elements located in
/assets
(create a new version if needed) - composer
- Copy (or symlink) the theme in the
/wp-content/themes
directory of your project - Nothing more, you're ready to go! 🚀
- Clone element repository
git clone git@github.com:epfl-si/elements.git
- Checkout the dist:
git checkout dist/frontend && git pull
- Go on wp-theme-2018 repository
- Update the theme with:
git pull
- Copy elements files from elements:dist/frontend to wp-theme-2018 cloned repository (in parent theme folder).
- Assuming you have both repositories cloned in the same parent directory, you can use following
commands:
rsync -av --progress ./elements/ wp-theme-2018/assets/ --exclude node_modules --exclude .git --exclude 'package.json' --exclude '.nojekyll'
- Assuming you have both repositories cloned in the same parent directory, you can use following
commands:
- Copy elements files from elements:dist/frontend to wp-theme-2018 cloned repository (in parent theme folder).
- Find the elements version in ./elements/package.json
- Commit the builds
git commit -am "New element version $elementversion"
- Push
git push
- Here you go, you just updated the styleguide version contained in this theme !
- update the following files:
wp-theme-2018/VERSION
with the version numberwp-theme-2018/style.css
with the version numberCHANGELOG.md
with a description of all the changes since last release
- commit them in a "Bump version" commit
git commit -am "Bump version"
- Push
git push
- head over this repo on github, on the release tab (or go directly using https://github.com/epfl-si/wp-theme-2018/releases)
- go to Draft a new release
- choose the release number you just changed, insert the changelog informations into the release description
- Publish the release
- congratulation, a new version has been released ! 🎉