Workshop words about modernizing your security testing. Do it all early and often!
REMOVE BELOW: This is lingering words about how to use Hugo for the AWS workshop
Hugo Framework and Markdown
Setting Up The Workshop: AWS Hosted Or Self-paced
By utilizing the Hugo language localization settings, directing the workshop towards a specific setup can be simplified. The Language setting in the config.toml file will allow you to distinguish between having one option or both. Commenting out one of the languages will hide all files that are related to that setup. By default, only the self-guided setup will be enabled. To enable switching, set disableLanguageSwitchingButton to false in the config.toml. If you want to have only the Event Engine setup, set the defaultContentLanguage at the top of the config.toml file to ee.
The Entry Point Of The Workshop And Naming Conventions
All modifications should be done to files in the content folder. _index.md serves as the main entry point to your workshop. Adding modules can be done utilizing the format of #_title as a folder within content. By adding a number value to the title, this helps to keep the files structured in parity with the content of the workshop. A good practice for file naming is to have the folder be the module number and the submodule numbers add to that number reflecting their order. For example, the first module is 1_ModuleOne and the submodules would be 11_SubmoduleOne, 12_SubmoduleTwo, and so forth.
To ensure the modules and submodules follow the correct structure order, adjust the “weight” value in the heading of the file to reflect the order you wish to use. Three module examples are included in this template with the second being split based upon the method of setup. The same rules apply for submodules. _index.md will be the entry point of that module. Submodules should be named with the format of {module number}{weight}_{title}.{language}.md. For example, 11_Foreword.md would be the first submodule of module one in the default language/setup. 31_PartnerSetup.ee.md would be the first submodule of module 3 in the EventEngine language/setup.
Working With Hugo Markdown and Shortcode
The following links will supply you with all the reference documentation about Hugo markdown. For more experienced developers, inline HTML is also an option to add more customization. For example <p style='text-align: left;'> inline will allow you to adjust your text placement.
Markdown and Shortcode Resources
The following links are your go-to resource for markdown and shortcode reference in building your workshop:
- Markdown cheat sheet https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet
- Learn theme markdown https://learn.netlify.app/en/cont/markdown/
- Menu extras and shortcuts https://learn.netlify.app/en/cont/menushortcuts/
- Using Font Awesome Emoji’s https://learn.netlify.app/en/cont/icons/ to help your page pop
Adding Images and Static Media
Any images and static media to be included in the workshop need to be placed in the static/images folder. The format to display an image is as follows: 
For example, the markdown for this dog is  and the image is in the static/images folder.
Creating Links
The format for creating links is [Link Display Text](http://example.com). For example, this link Hugo Framework was created using [Hugo Framework](https://gohugo.io/about/what-is-hugo/).
The “More” Menu Section
This section of the menu on the left is designed to add additional resources that are related to the workshop but not necessarily part of the workshop itself. To modify these links, edit the sections marked [[menu.shortcuts]] in the config.toml located in the root folder. The “name” portion will be what is displayed in the menu. The “url” should be the address of the link. The “weight” setting will adjust the display order, similar to the other “weight” settings utilized in indexes and modules mentioned previously.
Ensuring Pages Appear In Both Setup Versions
A shortcut to creating the workshop with different setup versions is utilizing the localization functionality of Hugo. By adding a secondary extension to the filename, this file will be included in the specific version of the workshop. Currently, the base utilizes the format *.ee.md to signify that the page is to be used in the AWS EventEngine setup. Much of the time, the files will be the same as the content only differs at specific points. It is necessary to add them, however, to make sure that the common content is duplicated across both versions. If you wish to change the secondary extension or default version, this can be done in the config.toml file in the heading and [Languages] sections.