diff --git a/README.html b/README.html index d4d4480a..13f2ce3d 100644 --- a/README.html +++ b/README.html @@ -14,7 +14,7 @@
Go to the main website [http://se-education.org/guides]
Go to the main website [http://se-education.org/guides]
This is a sub-project of the se-education.org.
Suggestions, questions, and bug reports can be posted in our issue tracker.
Alternatively, contact project mentor Damith C. Rajapakse. -
This work is released under the MIT OSS license.
PRs to improve/add content are welcome.
This website uses MarkBind documentation tool. This document has some guidance on how to use it when updating contents.
Follow the Markdown style guide in your PR.
The favicon.ico
is based on an icon made by Dave Gandy from www.flaticon.com
This work is released under the MIT OSS license.
PRs to improve/add content are welcome.
This website uses MarkBind documentation tool. This document has some guidance on how to use it when updating contents.
Follow the Markdown style guide in your PR.
The favicon.ico
is based on an icon made by Dave Gandy from www.flaticon.com
We recommend using java.util.logging
package for logging.
Logging Levels
SEVERE
: A critical problem detected which may cause the termination of the application.WARNING
: Can continue, but with caution.INFO
: Information showing the noteworthy actions by the App.FINE
: Details that is not usually noteworthy but may be useful in debugging e.g. print the actual list instead of just its size.We recommend using java.util.logging
package for logging.
Logging Levels
SEVERE
: A critical problem detected which may cause the termination of the application.WARNING
: Can continue, but with caution.INFO
: Information showing the noteworthy actions by the App.FINE
: Details that is not usually noteworthy but may be useful in debugging e.g. print the actual list instead of just its size.AddressBook-Level3 (AB3) is a brownfield project template used by SE courses. Given below are some tutorials to help students understand how to navigate and modify the existing AB3 codebase.
Person
class.Authors:
AddressBook-Level3 (AB3) is a brownfield project template used by SE courses. Given below are some tutorials to help students understand how to navigate and modify the existing AB3 codebase.
Person
class.Authors:
GitHub Actions is CI/CD tool integrated into GitHub.
In the simplest case, setting up is a matter of adding a .yml
file into the [root]\.github\workflows
folder (example).
GitHub Actions will run the workflow (as per the .yml
file) every time certain project events are triggered (e.g., when a PR is updated, or the master
branch is updated).
GitHub Actions is CI/CD tool integrated into GitHub.
In the simplest case, setting up is a matter of adding a .yml
file into the [root]\.github\workflows
folder (example).
GitHub Actions will run the workflow (as per the .yml
file) every time certain project events are triggered (e.g., when a PR is updated, or the master
branch is updated).
Please refer to Intellij's own documentation here.
Please refer to Intellij's own documentation here.
If you are working with a forked repo that is using MarkBind already, refer to this guide instead.
MarkBind is a tool for generating static websites from markdown-like text, particularly suitable for text-heavy websites such as software project documentation.
Given below are some information useful for when you want to update documentation in a project that uses MarkBind.
MarkBind is a superset of Markdown. Refer the MarkBind user guide for more details.
First, start the live preview: Unless it is a trivial change, you would want to see how your change to the documentation source files will reflect in the generated website. You can use the MarkBind live preview mode to preview the generated website as you update the source file. To start the live preview mode,
[project root]/docs
-- if you are not sure, look for the folder containing the site.json
file).markbind serve
command. That will open the generated website in your default browser.Next, edit the files you want:
.md
files).While live preview can pick up most changes, it may not be able to pick up certain changes (e.g., changes to files in the _markbind
folder or changes to nunjucks macros). Furthermore, some syntax errors in your code can cause the live preview to crash. In those cases, just stop the server (Ctrl+C on Windows) and start it again.
Project admins can,
If you are working with a forked repo that is using MarkBind already, refer to this guide instead.
MarkBind is a tool for generating static websites from markdown-like text, particularly suitable for text-heavy websites such as software project documentation.
Given below are some information useful for when you want to update documentation in a project that uses MarkBind.
MarkBind is a superset of Markdown. Refer the MarkBind user guide for more details.
First, start the live preview: Unless it is a trivial change, you would want to see how your change to the documentation source files will reflect in the generated website. You can use the MarkBind live preview mode to preview the generated website as you update the source file. To start the live preview mode,
[project root]/docs
-- if you are not sure, look for the folder containing the site.json
file).markbind serve
command. That will open the generated website in your default browser.Next, edit the files you want:
.md
files).While live preview can pick up most changes, it may not be able to pick up certain changes (e.g., changes to files in the _markbind
folder or changes to nunjucks macros). Furthermore, some syntax errors in your code can cause the live preview to crash. In those cases, just stop the server (Ctrl+C on Windows) and start it again.
Project admins can,