- Clone this repo.
- Run
git submodule update --init --recursive
to pull the content of the submodule. - Install MarkBind
- Checkout the branch of the module e.g.,
cs2103
- Update content using MarkBind syntax (How to use MarkBind)
markbind serve
to start the local server (to preview changes). This command also initiates the live-preview ability i.e. when any changes to the MarkBind code is saved, the site is auto-generated and the Web page (that was opened by theserve
command) auto-refreshes to show the new content. This works well for small websites but not so well for this website. Recommended to shutdown the server (Ctrl+C
) before doing further edits.- When you are happy with the edits, use the
markbind deploy
to deploy to the GitHub website at theorigin
repo.- If the deployment failed due to a 'caching' issue, try deleting the the cache generated by the previous deploy command (on Windows, the cache can be found in
/c/Users/{user-name}/AppData/Roaming/npm/node_modules/markbind-cli/node_modules/gh-pages/.cache
)
- If the deployment failed due to a 'caching' issue, try deleting the the cache generated by the previous deploy command (on Windows, the cache can be found in
- If you need to update contents inside the
book
folder,- Post an issue in the se-edu/se-book issue tracker to request for the change
- After the change has been done, pull the sub-module, and commit the changes to sub-module reference (when you pull a sub-module, Git automatically updates the submodule reference which is seen as a change in the enclosing repo).
cd book git pull origin master cd .. git commit -am "sync with book"
- Deploy the website to make the updated book content visible to students
- MarkBind bug reports and suggestions https://github.com/MarkBind/markbind/issues
- SE-Book bug reports and change requests se-edu/se-book issue tracker