Update Academy First Page

[vr-varad]

Notes for Reviewers

This PR updates the first visible page of academy with important info.

Signed commits

• Yes, I signed my commits.

[leecalcote]

It's a fine line between convenience of info and duplication of info (more maintenance) - difficult to navigate.

[Vincamine]

should we hardcode the latest version?

[Vincamine]

It seems they are listed on one line in your screenshot?

[hortison]

Which is good. They shouldn't be on multiple lines here, though.... at least not in terms of cleanliness. They render on a the same line, which makes this acceptable.

[hortison]

This is incomplete.

Either the rest of the content types need to be represented or a note needs to be included to say that this is only part of what is supported and a hyperlink included to Layer5 Docs with the full list.

[Vincamine]

1. I’m wondering if we should include so much information on the landing page. We could explain things concisely and link to our documentation for details. Here, we can leave a simple workflow.
2. As a reminder, after modifying this landing page, we need to share it across all academy-related repositories.

[vr-varad]

1. I’m wondering if we should include so much information on the landing page. We could explain things concisely and link to our documentation for details. Here, we can leave a simple workflow.
2. As a reminder, after modifying this landing page, we need to share it across all academy-related repositories.

Ya, I agree with you @Vincamine
I kept only what might be helpful, like to content and file structure for academy and for rest i have added a link for docs.

[Vincamine]

Hi team, thanks for the effort on this！ For an effective Academy landing page, I have a few considerations:

On the content:

1. This is the landing page for academy-example. It should stay focused on showing what content developers can do. Details about it belong in the docs, not here.
2. Since users have already forked academy-example by the time they land here, this page should simply point them to the official Docs(with reminders) rather than listing too much info.
3. Adding “tutorial-level” instructions on the landing page risks going out of date and creates duplication. Detailed guidance should live in the Docs.
4. The current content fills the page and feels 'heavy' to read. The hierarchy examples are not very intuitive and can add confusion.
5. The landing page should just serve as an entry point with a short explanation and a clear CTA.

On the location:

1. This is a single-use block; a shortcode adds unnecessary indirection without any reuse benefit.
2. Page-scoped content keeps the impact limited.
3. Landing pages should remain concise and route users to the Docs, not duplicate them.

Thus, I’ll close this PR and submit a follow-up with a clear CTA to the Docs. If styling is needed, we can handle that via CSS or a page-specific partial instead of wrapping the content in a shortcode.