refine navigation and add resources section

[alee]

• promote working groups to top level navigation instead of nested under About/
• add /resources/awesome-modeling-practices page that is generated at build time, resolves https://github.com/openmodelingfoundation/planning/issues/15
• resolves https://github.com/openmodelingfoundation/planning/issues/16

[Copilot]

Pull request overview

This PR restructures site navigation to promote Working Groups to a top-level section, adds a new Resources section (including an auto-generated “Awesome Modeling Practices” page sourced from an upstream repo), and updates Hugo configuration/versioning to support these changes.

Changes:

• Promote /working-groups/ to top-level nav and preserve old /about/working-groups/... URLs via aliases.
• Add /resources/ section with publications/repositories pages and a build-time generated “Awesome Modeling Practices” page.
• Bump Hugo to v0.160.1 and modernize syntax highlighting configuration.

Reviewed changes

Copilot reviewed 25 out of 25 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
layouts/docs/awesome-list.html	New Hugo layout that fetches and renders the upstream awesome list at build time, with URL rewriting/sanitization.
hugo.yaml	Updates Hugo minimum version and moves highlighting config under markup.highlight; bumps site version.
content/en/working-groups/_index.md	Makes Working Groups a top-level nav item and adds alias from prior /about/... location.
content/en/working-groups/*.md and content/en/working-groups/early-career-scholars/*	Adds aliases so old /about/working-groups/... paths continue to resolve.
content/en/standards/_index.md	Adjusts menu weight to reflect new top-level nav ordering.
content/en/resources/_index.md	Introduces Resources landing page and adds it to the main menu.
content/en/resources/publications.md	Adds publications resource page.
content/en/resources/repositories.md	Adds repositories resource page and links to the awesome list page.
content/en/resources/awesome-modeling-practices/_index.md	Adds the awesome list landing page configured to use the new layout.
content/en/about/_index.md	Adjusts About menu weight for updated nav ordering.
content/en/contribute/_index.md	Adjusts Contribute menu weight for updated nav ordering.
content/en/about/history-events-and-activities.md	Updates Working Groups link to the new canonical path.
content/en/_index.html	Updates Working Groups link to new canonical path.
assets/scss/_styles_project.scss	Adds styling for the rendered awesome list page.
Dockerfile	Bumps Hugo container version to v0.160.1.
AGENTS.md	Updates documented Hugo version.
.env	Bumps Hugo version to v0.160.1.
.agent/working-memory/session.md	Notes the navigation/resources refactor plan is ready.
.agent/working-memory/plan-navigation-resources-refactor.md	Adds implementation plan for the navigation/resources refactor.
.agent/working-memory/plan-awesome-list.md	Updates target page path for the awesome list plan.

[Copilot]

The intro markup opened by <p class="awesome-list-intro"> is never closed (and the paragraph/content is only emitted when .Description is set). This results in invalid HTML and can cause the rest of the page to be nested inside the paragraph/card unexpectedly. Close the <p> (and consider moving the “generated from …” sentence outside the with .Description block if it should always appear).

Suggested change

	This page is generated from <a href="{{ $sourceRepo }}" target="_blank" rel="noopener">openmodelingfoundation/awesome-modeling-practices</a>
	This page is generated from <a href="{{ $sourceRepo }}" target="_blank" rel="noopener">openmodelingfoundation/awesome-modeling-practices</a>
	</p>

[CharlotteTill]

Looks great from what I can see Allen - tested the new layout and buttons etc using chrome and edge - all seems correct. Many thanks for the fast action on this.

[cmbarton]

I agree. Looks good. Thanks for the quick action in a busy week.

[cmbarton]

I'm not sure how best do to this. But the top level "standards" menu item leads to discussions from the planning workshops. Ultimately we want it to lead to OMF standards. Is there some way to put the current pages into a sub folder labeled something like 'planning workshop discussions'? As it is now, I fear it could lead to confusion as we begin to develop and promote 'real' standards.