What's New

This is a list of new features and/or changes in a given version

2025

March MVP 2.0 CURRENT VERSION

  • Change Require Checkin at each repo front page before browsing any further content.
    • Checkin data is used by Analytics gathering and issues a cookie valid for 5 days across our workshop estate. Collecting:
      • e-mail address
      • SMART Ticket
      • Marketing Code
    • New De-coupled analytics check-in functionality from Lab provisioning shortcode.
      • Check-in is automatically included on every repo.
      • Lab provisioning shortcodes should be included on labs featuring Azure automated provisioning scripts, and REMOVED from workshops which don’t require Azure provisioning.
    • Added Author mode so analytics check-in NOT REQUIRED while locally authoring workshops.
      • TO DO: Generate_toml runs every time author mode runs (hugo server)
  • Change Introduced Go Utility to simplify workshop authoring from different systems
    • When this Utility and documentation is polished, it will eliminate the need for docker_build/_run scripts in each repo and the tax of maintaining/updating them.
  • New Created utility to upgrade older repos to latest feature set including automated conversion of config.toml to repoConfig.json/hugo.toml
  • Update Update gitHub action to use latest API versioned commands
  • New Added Quizdown shortcode. Check MD Page for usage instructions

2024

Oct MVP 1.2

  • Change Switched to new container base image from hugomods
    • continuous support for latest Hugo version releases
    • Upgraded ReLearn theme to 6.0.0
  • Change Created a simplified/scripted procedure to convert workshop repos using older containers to the latest:
  • Update Theme updates
  • NewAnalytics
    • Add analytics capabilities to track site activity across entire Cloud TEC workshop catalog.

2023

June MVP 1.1

  • reduce container size (using Alpine to get shell. BusyBox does not have shell)
  • autopublish action on GitHub (run our container as GitHub action to perform Hugo build w/ CentralRepo)
    • eliminates need to store Hugo static HTML (autopublish action directly publishes to GH pages)
  • Move Shortcodes from CentralRepo to UserRepo
  • Add CentralRepo/scripts/local_copy.sh to copy any local shortcodes or partials into container
  • Modify logo.html to read Params for logoBanner & logoBannerColor
  • Standardize themes and colors for Workshop, UseCase, Spotlight, Demo
  • Modify Banner Text and Subtext to match theme and be customizable
  • Add ability to run container run in “build”, “server”, or “shell” mode
  • Added Dev container env & workflow to stage and test changes before promoting to main/Prod

May MVP 1.0

  • Separated UserRepo and Central Repo to allow maximum re-usability & future-proofing for style/format changes
    • Standard Repo has Fortinet reLearn theme Variant & all necessary customizations
  • Swap in Hugo ReLearn theme (actively community supported) and eliminate Learn & Notice themes (inactive development)
  • Ubuntu container:
    • Maintain consistent Hugo version and eliminate need for local installs
    • allow continuous improvement to our process via container improvements without adding burden to CSE Team
  • Use Container for Hugo Build & GitHub action to publish/refresh GitHub Pages
  • Containerizing our development efforts allows for a lightweight development area while eliminating redundant componentry every time we create a new repo/workshop/demo, and allowing simple and automated updates to existing workshops when the parent template changes.
    • Ultimately we’d like to have scripting copy/revise parent templates periodically and/or whenever we create new Workshops
  • First TECWorkshop re-published with this new workflow: https://fortinetcloudcse.github.io/FortiCNF/

March MVP 0.2

  • created FortiCloudCSE GitHub Org
  • begin separation of UserRepo & Central Repo
  • begin investigation into container workflow

Jan MVP 0.1