Refactor documentation by using github pages with jekyll

.github/workflows/jekyll-gh-pages.yml

@@ -5,6 +5,7 @@ on:
  # Runs on pushes targeting the default branch
  push:
  branches: ["master"]
+ paths: ["docs/**"]
 
  # Allows you to run this workflow manually from the Actions tab
  workflow_dispatch:
@@ -25,18 +26,30 @@ jobs:
  # Build job
  build:
  runs-on: ubuntu-latest
+ defaults:
+ run:
+ working-directory: docs
  steps:
  - name: Checkout
  uses: actions/checkout@v3
+ - name: Setup Ruby
+ uses: ruby/setup-ruby@v1
+ with:
+ ruby-version: '3.1' # Not needed with a .ruby-version file
+ bundler-cache: true # runs 'bundle install' and caches installed gems automatically
+ cache-version: 0 # Increment this number if you need to re-download cached gems
+ working-directory: '${{ github.workspace }}/docs'
  - name: Setup Pages
  uses: actions/configure-pages@v3
  - name: Build with Jekyll
- uses: actions/jekyll-build-pages@v1
- with:
-  source: ./docs/
- destination: ./_site
+ # Outputs to the './_site' directory by default
+ run: bundle exec jekyll build --baseurl "SyliusActiveCampaignPlugin"
+ env:
+  JEKYLL_ENV: production
  - name: Upload artifact
  uses: actions/upload-pages-artifact@v2
+ with:
+ path: "docs/_site/"
 
  # Deployment job
  deploy:

README.md

@@ -22,7 +22,7 @@ _ActiveCampaign_ and want to integrate it with _Sylius_.
 
 ## How can I install the plugin on my Sylius store?
 
-Please, check the documentation at the [Installation](docs/02-Installation.md) step.
+Please, check the documentation at the [Installation](https://webgriffe.github.io/SyliusActiveCampaignPlugin/installation.html) step.
 
 ## Is this plugin conformed to privacy?
 
@@ -35,6 +35,6 @@ designed with these issues in mind and is therefore easily customizable.
 
 ## Where do I start?
 
-First, we recommend that you read the entire documentation available at this [link](docs/README.md). Then you could start to
+First, we recommend that you read the entire documentation available at this [link](https://webgriffe.github.io/SyliusActiveCampaignPlugin/). Then you could start to
 install the plugin and use the basic features it gives such as the abandoned cart. You could also think to suggest some
 new features that this integration could add. So, let's start! 🚀

docs/.gitignore

@@ -0,0 +1,2 @@
+.jekyll-cache
+_site/*

docs/Gemfile

@@ -0,0 +1,7 @@
+source 'https://rubygems.org'
+
+gem "jekyll", "~> 4.3.2" # installed by `gem jekyll`
+# gem "webrick" # required when using Ruby >= 3 and Jekyll <= 4.2.2
+
+# gem "just-the-docs", "0.6.0" # pinned to the current release
+gem "just-the-docs" # always download the latest release

docs/Gemfile.lock

@@ -0,0 +1,84 @@
+GEM
+ remote: https://rubygems.org/
+ specs:
+ addressable (2.8.5)
+ public_suffix (>= 2.0.2, < 6.0)
+ colorator (1.1.0)
+ concurrent-ruby (1.2.2)
+ em-websocket (0.5.3)
+ eventmachine (>= 0.12.9)
+ http_parser.rb (~> 0)
+ eventmachine (1.2.7)
+ ffi (1.15.5)
+ forwardable-extended (2.6.0)
+ google-protobuf (3.23.4-x86_64-darwin)
+ google-protobuf (3.23.4-x86_64-linux)
+ http_parser.rb (0.8.0)
+ i18n (1.14.1)
+ concurrent-ruby (~> 1.0)
+ jekyll (4.3.2)
+ addressable (~> 2.4)
+ colorator (~> 1.0)
+ em-websocket (~> 0.5)
+ i18n (~> 1.0)
+ jekyll-sass-converter (>= 2.0, < 4.0)
+ jekyll-watch (~> 2.0)
+ kramdown (~> 2.3, >= 2.3.1)
+ kramdown-parser-gfm (~> 1.0)
+ liquid (~> 4.0)
+ mercenary (>= 0.3.6, < 0.5)
+ pathutil (~> 0.9)
+ rouge (>= 3.0, < 5.0)
+ safe_yaml (~> 1.0)
+ terminal-table (>= 1.8, < 4.0)
+ webrick (~> 1.7)
+ jekyll-include-cache (0.2.1)
+ jekyll (>= 3.7, < 5.0)
+ jekyll-sass-converter (3.0.0)
+ sass-embedded (~> 1.54)
+ jekyll-seo-tag (2.8.0)
+ jekyll (>= 3.8, < 5.0)
+ jekyll-watch (2.2.1)
+ listen (~> 3.0)
+ just-the-docs (0.6.1)
+ jekyll (>= 3.8.5)
+ jekyll-include-cache
+ jekyll-seo-tag (>= 2.0)
+ rake (>= 12.3.1)
+ kramdown (2.4.0)
+ rexml
+ kramdown-parser-gfm (1.1.0)
+ kramdown (~> 2.0)
+ liquid (4.0.4)
+ listen (3.8.0)
+ rb-fsevent (~> 0.10, >= 0.10.3)
+ rb-inotify (~> 0.9, >= 0.9.10)
+ mercenary (0.4.0)
+ pathutil (0.16.2)
+ forwardable-extended (~> 2.6)
+ public_suffix (5.0.3)
+ rake (13.0.6)
+ rb-fsevent (0.11.2)
+ rb-inotify (0.10.1)
+ ffi (~> 1.0)
+ rexml (3.2.6)
+ rouge (3.30.0)
+ safe_yaml (1.0.5)
+ sass-embedded (1.58.3)
+ google-protobuf (~> 3.21)
+ rake (>= 10.0.0)
+ terminal-table (3.0.2)
+ unicode-display_width (>= 1.1.1, < 3)
+ unicode-display_width (2.4.2)
+ webrick (1.8.1)
+
+PLATFORMS
+ x86_64-darwin-22
+ x86_64-linux
+
+DEPENDENCIES
+ jekyll (~> 4.3.2)
+ just-the-docs
+
+BUNDLED WITH
+ 2.4.19

docs/README.md

@@ -1,11 +1,174 @@
-# Docs Summary
-
-- [Requirements](01-Requirements.md)
-- [Installation](02-Installation.md)
-- [Usage](03-Usage.md)
- - [First setup](03_A-First_setup.md)
- - [Events](03_B-Events.md)
- - [Automation example](03_C-Automation_example.md)
-- [Contributing](04-Contributing.md)
- - [Running plugin tests](04_A-Tests.md)
- - [Opening Sylius with plugin](04_B-Opening_Sylius.md)
+# just-the-docs-template
+
+This is a *bare-minimum* template to create a [Jekyll] site that:
+
+- 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.
+
+More specifically, the created site:
+
+- 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.
+
+To get started with creating a site, simply:
+
+1. click "[use this template]" to create a GitHub repository
+2. go to Settings > Pages > Build and deployment > Source, and select GitHub Actions
+
+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).
+
+After completing the creation of your new site on GitHub, update it as needed:
+
+## Replace the content of the template pages
+
+Update the following files to your own content:
+
+- `index.md` (your new home page)
+- `README.md` (information for those who access your site repo on GitHub)
+
+## Changing the version of the theme and/or Jekyll
+
+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

docs/_config.yml

@@ -0,0 +1,30 @@
+title: Webgriffe Sylius ActiveCampaign plugin documentation
+description: A complete guide to install and use the Sylius ActiveCampaign plugin
+theme: just-the-docs
+logo: "/images/sylius-logo.png"
+favicon_ico: "/images/sylius-logo.png"
+enable_copy_code_button: true
+
+url: https://webgriffe.github.io
+
+aux_links:
+ Template Repository: https://github.com/webgriffe/SyliusActiveCampaignPlugin
+
+footer_content: "Copyright © 2023 Webgriffe."
+
+# Footer last edited timestamp
+last_edit_timestamp: true # show or hide edit time - page must have `last_modified_date` defined in the frontmatter
+last_edit_time_format: "%b %e %Y at %I:%M %p" # uses ruby's time format: https://ruby-doc.org/stdlib-2.7.0/libdoc/time/rdoc/Time.html
+
+# Footer "Edit this page on GitHub" link text
+gh_edit_link: true # show or hide edit this page link
+gh_edit_link_text: "Edit this page on GitHub."
+gh_edit_repository: "https://github.com/webgriffe/SyliusActiveCampaignPlugin" # the github URL for your repo
+gh_edit_branch: "master" # the branch that your docs is served from
+gh_edit_source: docs # the source that your files originate from
+gh_edit_view_mode: "tree" # "tree" or "edit" if you want the user to jump into the editor immediately
+
+# Google Analytics Tracking (optional)
+# Supports a CSV of tracking ID strings (eg. "UA-1234567-89,G-1AB234CDE5")
+ga_tracking:
+ga_tracking_anonymize_ip: true # Use GDPR compliant Google Analytics settings (true/nil by default)

docs/04-Contributing.md → docs/contributing/index.md

@@ -1,6 +1,11 @@
-# Contributing
+---
+title: Contributing
+layout: page
+nav_order: 4
+has_children: true
+---
 
-[Return to Summary main page](README.md)
+# Contributing
 
 In order to contribute to this plugin you have to clone this repository, create a branch for your feature or bugfix, do
 your changes and then make sure al tests are passing.
@@ -16,6 +21,3 @@ your changes and then make sure al tests are passing.
 
 To be able to set up a plugin's database, remember to configure you database credentials in `tests/Application/.env`
 and `tests/Application/.env.test`.
-
-- [Run tests](04_A-Tests.md)
-- [Opening Sylius in the plugin](04_B-Opening_Sylius.md)