make the Governance page readable straight through

_data/footer.yml

@@ -42,7 +42,7 @@
   class: scala
   links:
     - title: Governance
-      url: "/governance/index.html#governance"
+      url: "/governance/"
     - title: Blog
       url: "/blog/"
     - title: Code of Conduct

_layouts/inner-page-governance.html

@@ -2,8 +2,5 @@
 layout: inner-page-parent
 ---
 
-<!-- Masthead -->
-{% include masthead-governance.html %}
-
 <!-- Main content -->
 {% include inner-page-main-content.html %}

_posts/2024-10-16-announcing-governance.md

@@ -56,7 +56,7 @@ One big hurdle in the Scala 3 journey was the backlog of issues on the Scala rep
 
 ### Easier access to Scala maintainers
 
-You can now find a list of Scala maintainers and their roles on the updated Governance page, under [“Teams Behind Scala”](/governance/#gov-scala). We invite Scala users and contributors to tag maintainers on Scala related issues, according to their expertise and role, to further help responsiveness. Also, we encourage everyone to follow and engage with maintainers on official [GitHub discussions](https://github.com/scala/scala3/discussions), [Users](https://users.scala-lang.org/) and [Contributors](https://contributors.scala-lang.org/) forums, [Discord chat rooms](https://discord.com/invite/scala).
+You can now find lists of Scala maintainers and their roles on the new [Governance page](/governance). We invite Scala users and contributors to tag maintainers on Scala related issues, according to their expertise and role, to further help responsiveness. Also, we encourage everyone to follow and engage with maintainers on official [GitHub discussions](https://github.com/scala/scala3/discussions), [Users](https://users.scala-lang.org/) and [Contributors](https://contributors.scala-lang.org/) forums, [Discord chat rooms](https://discord.com/invite/scala).
 
 ### Conclusion
 

governance/index.md

@@ -10,26 +10,63 @@ includeTOC: true
 Scala was created by [Prof. Martin Odersky](https://lampwww.epfl.ch/~odersky/)
 at [EPFL](https://epfl.ch).
 
-The Scala language and associated websites are cooperative projects of the
-[Scala Center](https://scala.epfl.ch) at [EPFL](https://epfl.ch), the Scala 3
-team in Martin's research group, [LAMP](https://lamp.epfl.ch) (also at EPFL),
-the Scala teams at [Lightbend](https://www.lightbend.com) and
-[VirtusLab](https://virtuslab.com), and the Scala community more broadly, with
-participation from many companies, organizations, and individuals.
+The Scala language and associated websites are cooperative projects of the following
+four groups:
 
-Scala 2 maintenance is primarily handled by the Lightbend team. They also
-participate in Scala 3 development.
+* the [Scala Center](https://scala.epfl.ch) at [EPFL](https://epfl.ch)
+* the Scala 3 team in Martin's research group [LAMP](https://lamp.epfl.ch) (also at EPFL)
+* the Scala team at [Lightbend](https://www.lightbend.com)
+* the Scala team at [VirtusLab](https://virtuslab.com)
 
-VirtusLab focuses on infrastructure and tooling for Scala 3.
+and the Scala community more broadly, with participation from many
+companies, organizations, and individuals.
+
+## Who does what?
+
+The main decision body is the [Scala Core team](/scala-core/) which meets weekly
+to discuss issues within the language and its ecosystem.
 
 The Scala Center focuses on coordinating governance, education (especially
 online courses), documentation, open source community outreach, and tooling.
 Community participation in all of these efforts is strongly encouraged.
 
-The main decision body is the [Scala Core team](/scala-core/) which meets weekly
-to discuss issues within the language and its ecosystem.
+Scala 2 maintenance is primarily handled by the Lightbend team. They also
+participate in Scala 3 development.
+
+VirtusLab focuses on infrastructure and tooling for Scala 3.
 
 Scala 3 development is done by the compiler team currently listed at
 [Scala Compiler Team](/maintainers/) page and Scala 2 maintainers list is
 located in [the github README](https://github.com/scala/scala#get-in-touch) of
 the scala/scala repository.
+
+For Scala 3, see also the [Development guarantees](/development), which describes
+in detail how the timing and contents of Scala 3 releases are arrived at.
+
+## Scala Improvement Process
+
+The SIP is the primary mechanism for evolving the Scala language.
+
+This process aims to evolve Scala openly and collaboratively. Anyone from the community is welcome to submit a Scala Improvement Proposal (SIP), which is then reviewed and discussed by a Committee. Every month, the Committee votes on the proposals to accept in the language.
+
+For more information:
+
+* [SIP home page](https://docs.scala-lang.org/sips/index.html)
+* [SIP Committee Members](https://docs.scala-lang.org/sips/process-specification.html#the-sip-committee)
+* [SIP Process Specification](https://docs.scala-lang.org/sips/process-specification.html)
+
+## Scala Center
+
+This is the Scala language foundation coordinating Scala governance, community, education, and OSS library/tool development.
+
+The Scala Center contributes to the language core, open source Scala tooling and libraries, and
+delivers high-quality education materials. It fosters conversations in the community and coordinates with various parties to unblock and improve the Scala ecosystem.
+
+Joining the Center's Advisory Board is an effective way to participate in Scala governance, have your voice heard, as well as supporting the Center to achieve its goals.
+
+For more information:
+
+* [Home page](https://scala.epfl.ch/)
+* [Joining the Advisory Board](https://scala.epfl.ch/corporate-membership.html)
+* [5 Year Impact Report](https://scala.epfl.ch/records/first-five-years/)
+* [2024 Roadmap](https://www.scala-lang.org/blog/2024/02/06/scala-center-2024-roadmap.html)