Faq and Working Group update

[glikely]

This PR updates the FAQ and the Working Group page

The FAQ changes add some initial information about working group membership. More will come later.

The titles on the working group page are changed to hyperlinks so that visitors can find the associated Google Group

I've tested these changes by building and viewing the website locally.

[Copilot]

Pull request overview

Updates the CoreCollective website content to make working group participation clearer and to improve discoverability of each working group’s Google Group.

Changes:

• Add initial FAQ entries describing how to join working groups (including via email) and archive visibility.
• Update Working Groups page data to include Google Group identifiers and make group titles link to the corresponding Google Group.
• Add a “Technical Advisory Committee” entry to the Working Groups list.

Reviewed changes

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

File	Description
src/pages/working-groups/index.astro	Adds Google Group names to each working group and turns titles into links to Google Groups.
src/content/faq/faq.yaml	Replaces/extends FAQ content with working-group membership and archive information.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.

[Copilot]

The list renders a link for every item, but the final And more entry doesn’t define googlegroupname, so it will generate a URL ending in /undefined. Either add a valid group name for that item or render plain text / omit the link when googlegroupname is missing.

Suggested change

	<a href=`https://groups.google.com/u/0/a/corecollective.dev/g/${item.googlegroupname}`>
	{item.title}
	</a>
	{item.googlegroupname ? (
	<a href={`https://groups.google.com/u/0/a/corecollective.dev/g/${item.googlegroupname}`}>
	{item.title}
	</a>
	) : (
	item.title
	)}

[Copilot]

Property name googlegroupname is hard to read and inconsistent with the other camelCase identifiers in this file (e.g., backgroundImage, workingGroupsTitle). Consider renaming to googleGroupName (or similar) to improve readability and reduce typo risk.

Suggested change

	googlegroupname: 'linux-fundamentals',
	},
	{
	title: 'Confidential Compute',
	icon: iconConfidential,
	description:
	'Provision of a comprehensive set of software emulated hardware enabling execution of Confidential Compute on Arm',
	googlegroupname: 'confidential-compute',
	},
	{
	title: 'Windows on Arm',
	icon: iconWindows,
	description:
	'Targeting application layer support for Windows. From tooling to enablement and optimization of libraries on the Windows platform',
	googlegroupname: 'windows-on-arm',
	},
	{
	title: 'Android',
	icon: iconWindows,
	description:
	'Arm architecture feature adoption. Platform standardization & enablement',
	googlegroupname: 'android',
	},
	{
	title: 'Edge Compute',
	icon: iconEdge,
	description: 'Standards and Firmware for Arm edge platforms',
	googlegroupname: 'edge-compute',
	},
	{
	title: 'Virtualization',
	icon: iconData,
	description:
	'Enable collaboration on evolving Arm-architecture virtualization technologies for secure firmware, hypervisor, kernel and AI workloads',
	googlegroupname: 'virtualization',
	},
	{
	title: 'Data Center',
	icon: iconLink,
	description:
	'Focusing on technologies for cloud, on-prem and hybrid datacenter workloads as well as HPC.',
	googlegroupname: 'datacenter',
	},
	{
	title: 'Technical Advisory Committee',
	icon: iconLink,
	description:
	'Guidance committee for all CoreCollective activities',
	googlegroupname: 'tac',
	googleGroupName: 'linux-fundamentals',
	},
	{
	title: 'Confidential Compute',
	icon: iconConfidential,
	description:
	'Provision of a comprehensive set of software emulated hardware enabling execution of Confidential Compute on Arm',
	googleGroupName: 'confidential-compute',
	},
	{
	title: 'Windows on Arm',
	icon: iconWindows,
	description:
	'Targeting application layer support for Windows. From tooling to enablement and optimization of libraries on the Windows platform',
	googleGroupName: 'windows-on-arm',
	},
	{
	title: 'Android',
	icon: iconWindows,
	description:
	'Arm architecture feature adoption. Platform standardization & enablement',
	googleGroupName: 'android',
	},
	{
	title: 'Edge Compute',
	icon: iconEdge,
	description: 'Standards and Firmware for Arm edge platforms',
	googleGroupName: 'edge-compute',
	},
	{
	title: 'Virtualization',
	icon: iconData,
	description:
	'Enable collaboration on evolving Arm-architecture virtualization technologies for secure firmware, hypervisor, kernel and AI workloads',
	googleGroupName: 'virtualization',
	},
	{
	title: 'Data Center',
	icon: iconLink,
	description:
	'Focusing on technologies for cloud, on-prem and hybrid datacenter workloads as well as HPC.',
	googleGroupName: 'datacenter',
	},
	{
	title: 'Technical Advisory Committee',
	icon: iconLink,
	description:
	'Guidance committee for all CoreCollective activities',
	googleGroupName: 'tac',