-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
370 changed files
with
93,529 additions
and
182 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,174 +1,29 @@ | ||
# just-the-docs-template | ||
# SWAT Project Documentation Page | ||
|
||
This is a *bare-minimum* template to create a [Jekyll] site that: | ||
Welcome to the SWAT Project's GitHub Pages repository. This site hosts the comprehensive documentation for the SWAT Project. | ||
|
||
- uses the [Just the Docs] theme; | ||
- can be built and published on [GitHub Pages]; | ||
- can be built and previewed locally, and published on other platforms. | ||
## About This Repository | ||
|
||
More specifically, the created site: | ||
This GitHub Pages repository is dedicated to providing up-to-date documentation for the SWAT Project. It serves as the primary resource for information related to the project, including guides, tutorials, and API documentation. | ||
|
||
- uses a gem-based approach, i.e. uses a `Gemfile` and loads the `just-the-docs` gem; | ||
- uses the [GitHub Pages / Actions workflow] to build and publish the site on GitHub Pages. | ||
## Accessing the Documentation | ||
|
||
To get started with creating a site, simply: | ||
To explore our extensive documentation, please visit the SWAT Project Documentation site at [SWAT Project Documentation](https://swat-project.github.io/docs/). | ||
|
||
1. click "[use this template]" to create a GitHub repository | ||
2. go to Settings > Pages > Build and deployment > Source, and select GitHub Actions | ||
## Main Project Repository | ||
|
||
If you want to maintain your docs in the `docs` directory of an existing project repo, see [Hosting your docs from an existing project repo](#hosting-your-docs-from-an-existing-project-repo). | ||
For those interested in the source code, contributions, or more detailed information about the project itself, please visit our main GitHub repository at [SWAT Project Repository](https://github.com/SWAT-project/SWAT). | ||
|
||
After completing the creation of your new site on GitHub, update it as needed: | ||
## Contributing | ||
|
||
## Replace the content of the template pages | ||
We welcome and appreciate contributions from the community. If you're interested in contributing to our documentation or the main project, please check our [contributing guidelines]([link to contributing guidelines if available]). | ||
|
||
Update the following files to your own content: | ||
## Contact and Feedback | ||
|
||
- `index.md` (your new home page) | ||
- `README.md` (information for those who access your site repo on GitHub) | ||
For questions, feedback, or contacting the SWAT Project team, please [add contact information or link to contact page]. | ||
|
||
## Changing the version of the theme and/or Jekyll | ||
Thank you for your interest in the SWAT Project. Your support and contributions are what make this project a success! | ||
|
||
Simply edit the relevant line(s) in the `Gemfile`. | ||
--- | ||
|
||
## Adding a plugin | ||
|
||
The Just the Docs theme automatically includes the [`jekyll-seo-tag`] plugin. | ||
|
||
To add an extra plugin, you need to add it in the `Gemfile` *and* in `_config.yml`. For example, to add [`jekyll-default-layout`]: | ||
|
||
- Add the following to your site's `Gemfile`: | ||
|
||
```ruby | ||
gem "jekyll-default-layout" | ||
``` | ||
|
||
- And add the following to your site's `_config.yml`: | ||
|
||
```yaml | ||
plugins: | ||
- jekyll-default-layout | ||
``` | ||
Note: If you are using a Jekyll version less than 3.5.0, use the `gems` key instead of `plugins`. | ||
|
||
## Publishing your site on GitHub Pages | ||
|
||
1. If your created site is `YOUR-USERNAME/YOUR-SITE-NAME`, update `_config.yml` to: | ||
|
||
```yaml | ||
title: YOUR TITLE | ||
description: YOUR DESCRIPTION | ||
theme: just-the-docs | ||
url: https://YOUR-USERNAME.github.io/YOUR-SITE-NAME | ||
aux_links: # remove if you don't want this link to appear on your pages | ||
Template Repository: https://github.com/YOUR-USERNAME/YOUR-SITE-NAME | ||
``` | ||
|
||
2. Push your updated `_config.yml` to your site on GitHub. | ||
|
||
3. In your newly created repo on GitHub: | ||
- go to the `Settings` tab -> `Pages` -> `Build and deployment`, then select `Source`: `GitHub Actions`. | ||
- if there were any failed Actions, go to the `Actions` tab and click on `Re-run jobs`. | ||
|
||
## Building and previewing your site locally | ||
|
||
Assuming [Jekyll] and [Bundler] are installed on your computer: | ||
|
||
1. Change your working directory to the root directory of your site. | ||
|
||
2. Run `bundle install`. | ||
|
||
3. Run `bundle exec jekyll serve` to build your site and preview it at `localhost:4000`. | ||
|
||
The built site is stored in the directory `_site`. | ||
|
||
## Publishing your built site on a different platform | ||
|
||
Just upload all the files in the directory `_site`. | ||
|
||
## Customization | ||
|
||
You're free to customize sites that you create with this template, however you like! | ||
|
||
[Browse our documentation][Just the Docs] to learn more about how to use this theme. | ||
|
||
## Hosting your docs from an existing project repo | ||
|
||
You might want to maintain your docs in an existing project repo. Instead of creating a new repo using the [just-the-docs template](https://github.com/just-the-docs/just-the-docs-template), you can copy the template files into your existing repo and configure the template's Github Actions workflow to build from a `docs` directory. You can clone the template to your local machine or download the `.zip` file to access the files. | ||
|
||
### Copy the template files | ||
|
||
1. Create a `.github/workflows` directory at your project root if your repo doesn't already have one. Copy the `pages.yml` file into this directory. GitHub Actions searches this directory for workflow files. | ||
|
||
2. Create a `docs` directory at your project root and copy all remaining template files into this directory. | ||
|
||
### Modify the GitHub Actions workflow | ||
|
||
The GitHub Actions workflow that builds and deploys your site to Github Pages is defined by the `pages.yml` file. You'll need to edit this file to that so that your build and deploy steps look to your `docs` directory, rather than the project root. | ||
|
||
1. Set the default `working-directory` param for the build job. | ||
|
||
```yaml | ||
build: | ||
runs-on: ubuntu-latest | ||
defaults: | ||
run: | ||
working-directory: docs | ||
``` | ||
|
||
2. Set the `working-directory` param for the Setup Ruby step. | ||
|
||
```yaml | ||
- name: Setup Ruby | ||
uses: ruby/setup-ruby@v1 | ||
with: | ||
ruby-version: '3.1' | ||
bundler-cache: true | ||
cache-version: 0 | ||
working-directory: '${{ github.workspace }}/docs' | ||
``` | ||
|
||
3. Set the path param for the Upload artifact step: | ||
|
||
```yaml | ||
- name: Upload artifact | ||
uses: actions/upload-pages-artifact@v1 | ||
with: | ||
path: "docs/_site/" | ||
``` | ||
|
||
4. Modify the trigger so that only changes within the `docs` directory start the workflow. Otherwise, every change to your project (even those that don't affect the docs) would trigger a new site build and deploy. | ||
|
||
```yaml | ||
on: | ||
push: | ||
branches: | ||
- "main" | ||
paths: | ||
- "docs/**" | ||
``` | ||
|
||
## Licensing and Attribution | ||
|
||
This repository is licensed under the [MIT License]. You are generally free to reuse or extend upon this code as you see fit; just include the original copy of the license (which is preserved when you "make a template"). While it's not necessary, we'd love to hear from you if you do use this template, and how we can improve it for future use! | ||
|
||
The deployment GitHub Actions workflow is heavily based on GitHub's mixed-party [starter workflows]. A copy of their MIT License is available in [actions/starter-workflows]. | ||
|
||
---- | ||
|
||
[^1]: [It can take up to 10 minutes for changes to your site to publish after you push the changes to GitHub](https://docs.github.com/en/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll#creating-your-site). | ||
|
||
[Jekyll]: https://jekyllrb.com | ||
[Just the Docs]: https://just-the-docs.github.io/just-the-docs/ | ||
[GitHub Pages]: https://docs.github.com/en/pages | ||
[GitHub Pages / Actions workflow]: https://github.blog/changelog/2022-07-27-github-pages-custom-github-actions-workflows-beta/ | ||
[Bundler]: https://bundler.io | ||
[use this template]: https://github.com/just-the-docs/just-the-docs-template/generate | ||
[`jekyll-default-layout`]: https://github.com/benbalter/jekyll-default-layout | ||
[`jekyll-seo-tag`]: https://jekyll.github.io/jekyll-seo-tag | ||
[MIT License]: https://en.wikipedia.org/wiki/MIT_License | ||
[starter workflows]: https://github.com/actions/starter-workflows/blob/main/pages/jekyll.yml | ||
[actions/starter-workflows]: https://github.com/actions/starter-workflows/blob/main/LICENSE | ||
© [Year] SWAT Project Documentation. All rights reserved. |
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,35 +1,55 @@ | ||
--- | ||
title: Home | ||
layout: home | ||
layout: default | ||
title: Getting Started | ||
nav_order: 1 | ||
--- | ||
|
||
This is a *bare-minimum* template to create a Jekyll site that uses the [Just the Docs] theme. You can easily set the created site to be published on [GitHub Pages] – the [README] file explains how to do that, along with other details. | ||
# SWAT Project Documentation | ||
|
||
If [Jekyll] is installed on your computer, you can also build and preview the created site *locally*. This lets you test changes before committing them, and avoids waiting for GitHub Pages.[^1] And you will be able to deploy your local build to a different platform than GitHub Pages. | ||
Welcome to the SWAT Project Documentation! This guide is designed to help you get familiar with our project, understand its features, and learn how to use it effectively. | ||
|
||
More specifically, the created site: | ||
## What is the SWAT Project? | ||
|
||
- uses a gem-based approach, i.e. uses a `Gemfile` and loads the `just-the-docs` gem | ||
- uses the [GitHub Pages / Actions workflow] to build and publish the site on GitHub Pages | ||
"SWAT (Symbolic Web Application Testing platform)" is a cutting-edge, modular software testing platform designed for comprehensive web application testing. It stands out with its unique feature of using SMT-lib as an abstraction layer, allowing for compatibility with multiple solvers. Built using a diverse array of technologies like Python, Java, Docker, and more, SWAT is versatile and robust, catering to a wide range of testing scenarios. Its loosely coupled modules can be used either independently or collectively, offering unparalleled flexibility.. | ||
|
||
Other than that, you're free to customize sites that you create with this template, however you like. You can easily change the versions of `just-the-docs` and Jekyll it uses, as well as adding further plugins. | ||
## Getting Started | ||
|
||
[Browse our documentation][Just the Docs] to learn more about how to use this theme. | ||
--- | ||
|
||
## Navigation | ||
|
||
This documentation is structured to help you start from the basics and move towards more advanced topics: | ||
|
||
To get started with creating a site, simply: | ||
1. **Getting Started**: Learn how to set up and begin using the SWAT Project. | ||
2. **Features**: Dive into the features and capabilities of our project. | ||
3. **Advanced Topics**: Explore advanced use cases and customization options. | ||
4. **Internal Documentation**: Our Javadoc can be found [here](/javadoc/) | ||
4. **FAQs**: Find answers to commonly asked questions. | ||
|
||
1. click "[use this template]" to create a GitHub repository | ||
2. go to Settings > Pages > Build and deployment > Source, and select GitHub Actions | ||
## Contributing | ||
|
||
If you want to maintain your docs in the `docs` directory of an existing project repo, see [Hosting your docs from an existing project repo](https://github.com/just-the-docs/just-the-docs-template/blob/main/README.md#hosting-your-docs-from-an-existing-project-repo) in the template README. | ||
Contributions are always welcome! Please follow these steps: | ||
1. Fork the project repository. This creates a copy of the project on your account that you can modify without affecting the original project. | ||
2. Clone the forked repository to your local machine using a Git client like Git or GitHub Desktop. | ||
3. Create a new branch with a descriptive name (e.g., `new-feature-branch` or `bugfix-issue-123`). | ||
```sh | ||
git checkout -b new-feature-branch | ||
``` | ||
4. Make changes to the project's codebase. | ||
5. Commit your changes to your local branch with a clear commit message that explains the changes you've made. | ||
```sh | ||
git commit -m 'Implemented new feature.' | ||
``` | ||
6. Push your changes to your forked repository on GitHub using the following command | ||
```sh | ||
git push origin new-feature-branch | ||
``` | ||
7. Create a new pull request to the original project repository. In the pull request, describe the changes you've made and why they're necessary. | ||
The project maintainers will review your changes and provide feedback or merge them into the main branch. | ||
|
||
---- | ||
|
||
[^1]: [It can take up to 10 minutes for changes to your site to publish after you push the changes to GitHub](https://docs.github.com/en/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll#creating-your-site). | ||
We're excited to have you here and hope this documentation helps you effectively utilize the SWAT Project! | ||
|
||
--- | ||
|
||
[Just the Docs]: https://just-the-docs.github.io/just-the-docs/ | ||
[GitHub Pages]: https://docs.github.com/en/pages | ||
[README]: https://github.com/just-the-docs/just-the-docs-template/blob/main/README.md | ||
[Jekyll]: https://jekyllrb.com | ||
[GitHub Pages / Actions workflow]: https://github.blog/changelog/2022-07-27-github-pages-custom-github-actions-workflows-beta/ | ||
[use this template]: https://github.com/just-the-docs/just-the-docs-template/generate | ||
© 2024 SWAT Project. All rights reserved. |
Oops, something went wrong.