Merge branch 'master' into master

Author: vr-varad

.github/ISSUE_TEMPLATE/bug_report.md

@@ -27,8 +27,10 @@ assignees: ''
 -->
 
 ---
+
 #### Contributor Guide and Resources
+
 - 📚 [Instructions for contributing to layer5-academy](https://github.com/layer5io/layer5-academy/blob/master/CONTRIBUTING.md)
-   - academy-template documentation [site](https://docs.layer5.io/cloud/academy/), [example](https://github.com/layer5io/academy-example/) and [theme](https://github.com/layer5io/academy-theme/)
+  - academy-template documentation [site](https://docs.layer5.io/cloud/academy/), [example](https://github.com/layer5io/academy-example/) and [theme](https://github.com/layer5io/academy-theme/)
 - 🎨 Wireframes and [designs for Layer5 site](https://www.figma.com/file/5ZwEkSJwUPitURD59YHMEN/Layer5-Designs) in Figma [(open invite)](https://www.figma.com/team_invite/redeem/qJy1c95qirjgWQODApilR9)
 - 🙋🏾🙋🏼 Questions: [Layer5 Discussion Forum](https://discuss.layer5.io) and [Layer5 Community Slack](http://slack.layer5.io)

.github/ISSUE_TEMPLATE/ci.md

@@ -18,8 +18,10 @@ assignees: ''
 <!-- Stipulations of functional behavior or non-functional items that must be in-place in order for the issue to be closed. -->
 
 ---
+
 #### Contributor Guide and Resources
+
 - 📚 [Instructions for contributing to layer5-academy](https://github.com/layer5io/layer5-academy/blob/master/CONTRIBUTING.md)
-   - academy-template documentation [site](https://docs.layer5.io/cloud/academy/), [example](https://github.com/layer5io/academy-example/) and [theme](https://github.com/layer5io/academy-theme/)
+  - academy-template documentation [site](https://docs.layer5.io/cloud/academy/), [example](https://github.com/layer5io/academy-example/) and [theme](https://github.com/layer5io/academy-theme/)
 - 🎨 Wireframes and [designs for Layer5 site](https://www.figma.com/file/5ZwEkSJwUPitURD59YHMEN/Layer5-Designs) in Figma [(open invite)](https://www.figma.com/team_invite/redeem/qJy1c95qirjgWQODApilR9)
-- 🙋🏾🙋🏼 Questions: [Layer5 Discussion Forum](https://discuss.layer5.io) and [Layer5 Community Slack](http://slack.layer5.io)
+- 🙋🏾🙋🏼 Questions: [Layer5 Discussion Forum](https://discuss.layer5.io) and [Layer5 Community Slack](http://slack.layer5.io)

.github/ISSUE_TEMPLATE/documentation.md

@@ -7,13 +7,13 @@ assignees: ''
 ---
 #### Current State
 
-
 #### Desired State
 
-
 ---
+
 #### Contributor Guide and Resources
+
 - 📚 [Instructions for contributing to layer5-academy](https://github.com/layer5io/layer5-academy/blob/master/CONTRIBUTING.md)
-   - academy-template documentation [site](https://docs.layer5.io/cloud/academy/), [example](https://github.com/layer5io/academy-example/) and [theme](https://github.com/layer5io/academy-theme/)
+  - academy-template documentation [site](https://docs.layer5.io/cloud/academy/), [example](https://github.com/layer5io/academy-example/) and [theme](https://github.com/layer5io/academy-theme/)
 - 🎨 Wireframes and [designs for Layer5 site](https://www.figma.com/file/5ZwEkSJwUPitURD59YHMEN/Layer5-Designs) in Figma [(open invite)](https://www.figma.com/team_invite/redeem/qJy1c95qirjgWQODApilR9)
 - 🙋🏾🙋🏼 Questions: [Layer5 Discussion Forum](https://discuss.layer5.io) and [Layer5 Community Slack](http://slack.layer5.io)

.github/ISSUE_TEMPLATE/feature_request.md

@@ -21,8 +21,10 @@ assignees: ''
 <!-- [Optional] Any visual diagrams of the desired user interface. -->
 
 ---
+
 #### Contributor Guide and Resources
+
 - 📚 [Instructions for contributing to layer5-academy](https://github.com/layer5io/layer5-academy/blob/master/CONTRIBUTING.md)
-   - academy-template documentation [site](https://docs.layer5.io/cloud/academy/), [example](https://github.com/layer5io/academy-example/) and [theme](https://github.com/layer5io/academy-theme/)
+  - academy-template documentation [site](https://docs.layer5.io/cloud/academy/), [example](https://github.com/layer5io/academy-example/) and [theme](https://github.com/layer5io/academy-theme/)
 - 🎨 Wireframes and [designs for Layer5 site](https://www.figma.com/file/5ZwEkSJwUPitURD59YHMEN/Layer5-Designs) in Figma [(open invite)](https://www.figma.com/team_invite/redeem/qJy1c95qirjgWQODApilR9)
-- 🙋🏾🙋🏼 Questions: [Layer5 Discussion Forum](https://discuss.layer5.io) and [Layer5 Community Slack](http://slack.layer5.io)
+- 🙋🏾🙋🏼 Questions: [Layer5 Discussion Forum](https://discuss.layer5.io) and [Layer5 Community Slack](http://slack.layer5.io)

.github/PULL_REQUEST_TEMPLATE.md

@@ -2,12 +2,9 @@
 
 This PR fixes #
 
-
-
-
 **[Signed commits](../blob/master/CONTRIBUTING.md#signing-off-on-commits-developer-certificate-of-origin)**
+
 - [ ] Yes, I signed my commits.
- 
 
 <!--
 Thank you for contributing to Meshery! 

CODE_OF_CONDUCT.md

@@ -2,4 +2,4 @@
 
 The Layer5 community follows the code of conduct outlined in the [Community Handbook]([https://layer5.io](https://layer5.io/community/handbook/code-of-conduct).
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting community@layer5.io.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting <community@layer5.io>.

CONTRIBUTING-gitflow.md

@@ -1,41 +1,53 @@
 # Working by Forking
+
 Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or just head straight to the command line:
 
 ## Clone your fork to your local machine
-```
+
+```shell
 git clone git@github.com:USERNAME/FORKED-PROJECT.git
 ```
+
 Keeping Your Fork Up to Date
 While this isn't an absolutely necessary step, if you plan on doing anything more than just a tiny quick fix, you'll want to make sure you keep your fork up to date by tracking the original "upstream" repo that you forked. To do this, you'll need to add a remote:
 
 ## Add 'upstream' repo to list of remotes
-```
+
+```shell
 git remote add upstream https://github.com/layer5io/meshery.git
-``` 
+```
+
 ("meshery" is used as the example repo. Be sure to reference the _actual_ repo you're contributing to e.g. "meshery-linkerd").
 
 ## Verify the new remote named 'upstream'
-```
+
+```shell
 git remote -v
 ```
+
 Whenever you want to update your fork with the latest upstream changes, you'll need to first fetch the upstream repo's branches and latest commits to bring them into your repository:
 
 ## Fetch from upstream remote
-```
+
+```shell
 git fetch upstream
 ```
 
 ## View all branches, including those from upstream
-```
+
+```shell
 git branch -va
 ```
+
 Now, checkout your own master branch and merge the upstream repo's master branch:
 
 ## Checkout your master branch and merge upstream
-```
+
+```shell
 git checkout master
 git merge upstream/master
 ```
+
 If there are no unique commits on the local master branch, git will simply perform a fast-forward. However, if you have been making changes on master (in the vast majority of cases you probably shouldn't be - see the next section, you may have to deal with conflicts. When doing so, be careful to respect the changes made upstream.
 
 Now, your local master branch is up-to-date with everything modified upstream.
@@ -46,50 +58,61 @@ Whenever you begin work on a new feature or bugfix, it's important that you crea
 To create a new branch and start working on it, peform the following flow.
 
 ## Checkout the master branch - you want your new branch to come from master
-```
+
+```shell
 git checkout master
 ```
 
 ## Create a new branch (give your branch its own simple informative name)
+
 For enhancements use `feature/your_username/issue#` or `feature/your_username/name_of_feature`
 
 For bugs use `bug/your_username/issue#` or `bug/your_username/name_of_bug`
 
-```
+```shell
 git branch feature/jdoe/567
 ```
 
 ## Switch to your new branch
-```
+
+```shell
 git checkout feature/jdoe/567
 ```
+
 Now, go to town hacking away and making whatever changes you want to.
 
 ## Submitting your changes (a Pull Request)
+
 Prior to submitting your pull request, you might want to do a few things to clean up your branch and make it as simple as possible for the original repo's maintainer to test, accept, and merge your work.
 
 In the time that you've been working on your changes, if any commits have been made to the upstream master branch, you will need to rebase your development branch so that merging it will be a simple fast-forward that won't require any conflict resolution work.
 
 ## Fetch upstream master and merge with your repo's master branch
-```
+
+```shell
 git fetch upstream
 git checkout master
 git merge upstream/master
 ```
 
 ## If there were any new commits, rebase your development branch
-```
+
+```shell
 git checkout feature/jdoe/567
 git rebase master
 ```
+
 Now, it may be desirable to squash some of your smaller commits down into a small number of larger more cohesive commits. You can do this with an interactive rebase:
 
 ## Rebase all commits on your development branch
-```
+
+```shell
 git checkout
 git rebase -i master
 ```
+
 This will open up a text editor where you can specify which commits to squash.
 
 ## Submitting
+
 Once you've committed and pushed all of your changes to GitHub, go to the page for your fork on GitHub, select your development branch, and click the pull request button. If you need to make any adjustments to your pull request, just push the updates to GitHub. Your pull request will automatically track the changes on your development branch and update.

CONTRIBUTING.md

@@ -1,11 +1,13 @@
 # <a name="contributing">Contributing Overview</a>
+
 Please do! Thanks for your help improving the project! :balloon:
 
 All contributors are welcome. Please see the [newcomers welcome guide](https://layer5.io/community/newcomers) for how, where and why to contribute. This project is community-built and welcomes collaboration. Contributors are expected to adhere to our [Code of Conduct](CODE_OF_CONDUCT.md).
 
 Not sure where to start? First, see the [newcomers welcome guide](https://layer5.io/community/newcomers). Grab an open issue with the [help-wanted label](../../labels/help%20wanted) and jump in. Join the [Slack account](http://slack.layer5.io) and engage in conversation. Create a [new issue](/../../issues/new/choose) if needed.  All [pull requests](/../../pulls) should reference an open [issue](/../../issues). Include keywords in your pull request descriptions, as well as commit messages, to [automatically close issues in GitHub](https://help.github.com/en/github/managing-your-work-on-github/closing-issues-using-keywords).
 
 **Sections**
+
 - <a name="contributing">General Contribution Flow</a>
   - <a href="#commit-signing">Developer Certificate of Origin</a>
 
@@ -15,8 +17,8 @@ Relevant coding style guidelines are the Go Code Review Comments and the Formatt
 
 This repository serves as the **official content repository** for Layer5's Academy learning platform, hosting all official learning paths, challenges, and certifications.
 
-
 ### Detailed Guide
+
 For a complete, step-by-step guide on how to create, structure, and publish a new learning path, please refer to our official documentation:
 
 ➡️ [Academy](https://docs.layer5.io/cloud/academy/)
@@ -43,24 +45,28 @@ Signed-off-by: Jane Smith <jane.smith@example.com>
 In most cases, you can add this signoff to your commit automatically with the
 `-s` or `--signoff` flag to `git commit`. You must use your real name and a reachable email
 address (sorry, no pseudonyms or anonymous contributions). An example of signing off on a commit:
+
 ```
-$ commit -s -m "my commit message w/signoff"
+commit -s -m "my commit message w/signoff"
 ```
 
 To ensure all your commits are signed, you may choose to add this alias to your global ```.gitconfig```:
 
 *~/.gitconfig*
+
 ```
 [alias]
   amend = commit -s --amend
   cm = commit -s -m
   commit = commit -s
 ```
+
 Or you may configure your IDE, for example, Visual Studio Code to automatically sign-off commits for you:
 
 <a href="https://user-images.githubusercontent.com/7570704/64490167-98906400-d25a-11e9-8b8a-5f465b854d49.png" ><img src="https://user-images.githubusercontent.com/7570704/64490167-98906400-d25a-11e9-8b8a-5f465b854d49.png" width="50%"><a>
 
 ## <a name="contributing-docs">Academy Content Contribution Flow</a>
+
 Please contribute! Layer5 Academy uses Hugo and GitHub Pages to host the learning platform. Learn more about [Layer5's Academy platform development](https://docs.layer5.io/cloud/academy/platform-development/). The process of contributing follows this flow:
 
 1. Create a fork, if you have not already, by following the steps described [here](./CONTRIBUTING-gitflow.md)
@@ -76,11 +82,12 @@ Please contribute! Layer5 Academy uses Hugo and GitHub Pages to host the learnin
 `git push origin <my-changes>`
 1. Open a pull request (in your web browser) against the repo.
 
-
 #### Tests
+
 Users can now test their local development setup using the provided Makefile commands.
 
 To test your local Academy setup, run the following commands:
+
 ```
 # Install dependencies
 make setup
@@ -90,7 +97,9 @@ make site
 ```
 
 #### Building the Site
+
 To build the Academy site for production, ensure you have `Hugo` and `Go` installed. Now, run the following command to build the site:
+
 ```sh
 make build
 ```
@@ -100,10 +109,12 @@ make build
 Layer5 Academy follows specific content and formatting guidelines for consistency across all learning materials.
 
 # <a name="maintaining"> Reviews</a>
+
 All contributors are invited to review pull requests. See this short video on [how to review a pull request](https://www.youtube.com/watch?v=isLfo7jfE6g&feature=youtu.be).
 
 # New to Git?
-Resources: https://lab.github.com and https://try.github.com/
+
+Resources: <https://lab.github.com> and <https://try.github.com/>
 
 ### License
 
@@ -115,4 +126,4 @@ This repository and site are available as open source under the terms of the [Ap
 <p>The <a href="https://layer5.io/community">Layer5 community</a> represents the largest collection of service mesh projects and their maintainers in the world.</p>
 
 **Open Source First**
-<p>At Layer5, we champion developer-defined infrastructure, giving engineers the power to reshape application delivery. We empower operators in reimagining how they manage modern infrastructure: collaboratively.</p>
+<p>At Layer5, we champion developer-defined infrastructure, giving engineers the power to reshape application delivery. We empower operators in reimagining how they manage modern infrastructure: collaboratively.</p>

Makefile

@@ -12,10 +12,9 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 
-#include .github/build/Makefile.show-help.mk
+include .github/build/Makefile.show-help.mk
 
-## Install academy-example dependencies on your local machine.
-## See https://gohugo.io/categories/installation
+## Install dependencies on your local machine.
 setup:
 	npm install
 
@@ -36,16 +35,25 @@ clean:
 	hugo --cleanDestinationDir
 	make site
 
+## Fix Markdown linting issues
+lint-fix:
+	@echo "Checking for markdownlint-cli2..."
+	@command -v markdownlint-cli2 > /dev/null || { \
+		echo "markdownlint-cli2 not found. Attempting to install globally..."; \
+		command -v npm > /dev/null || { echo "npm is not installed. Please install Node.js/npm and re-run 'make lint-fix'."; exit 1; }; \
+		npm install -g markdownlint-cli2; \
+	}
+	@echo "Running markdownlint-cli2 --fix..."
+	@markdownlint-cli2 --fix "**/*.md" "#node_modules" "#public" "#resources"
 
 check-go:
 	@echo "Checking if Go is installed..."
 	@command -v go > /dev/null || (echo "Go is not installed. Please install it before proceeding."; exit 1)
 	@echo "Go is installed."
 
-
 ## Update the academy-theme package to latest version
 theme-update:
 	echo "Updating to latest academy-theme..." && \
 	hugo mod get github.com/layer5io/academy-theme
 
-.PHONY: setup build site clean site-fast check-go academy-update
+.PHONY: setup build site clean check-go theme-update