Rename files to match the new naming convention

Author: Darius Neațu

docs/MISSION.md

@@ -40,8 +40,8 @@ These libraries were archived and no longer maintained. These libraries are not
 
 Transition examples:
 
-* They were [Production ready. Stable API.](./BEMAN_LIBRARY_MATURITY_MODEL.md#production-ready-stable-api) at some point, but are no longer developed or maintained, being superseded by native compiler implementations - `Mature retirement`.
+* They were [Production ready. Stable API.](./beman_library_maturity_model.md#production-ready-stable-api) at some point, but are no longer developed or maintained, being superseded by native compiler implementations - `Mature retirement`.
 
-* They were [Production ready. API may undergo changes.](./BEMAN_LIBRARY_MATURITY_MODEL.md#production-ready-api-may-undergo-changes) at some point, but are no longer developed or maintained, being rejected from the ISO C+ Standardization - `Early retirement`.
+* They were [Production ready. API may undergo changes.](./beman_library_maturity_model.md#production-ready-api-may-undergo-changes) at some point, but are no longer developed or maintained, being rejected from the ISO C+ Standardization - `Early retirement`.
 
-* They were [Under development and not yet ready for production use.](./BEMAN_LIBRARY_MATURITY_MODEL.md#under-development-and-not-yet-ready-for-production-use) at some point and were abandoned - `Early retirement`.
+* They were [Under development and not yet ready for production use.](./beman_library_maturity_model.md#under-development-and-not-yet-ready-for-production-use) at some point and were abandoned - `Early retirement`.

docs/BEMAN_LIBRARY_MATURITY_MODEL.md docs/beman_library_maturity_model.mddocs/BEMAN_LIBRARY_MATURITY_MODEL.md renamed to docs/beman_library_maturity_model.md

@@ -120,7 +120,7 @@ If you have questions, please feel free to ask on our communication channels, or
 
 ## Conduct team
 
-The conduct team will be the Beman Project Leads as outlined in our [Governance Documents](GOVERNANCE.md).
+The conduct team will be the Beman Project Leads as outlined in our [Governance Documents](governance.md).
 
 ### Reporting conduct
 
@@ -196,7 +196,7 @@ If that’s the case, the identities of anyone involved will remain confidential
 ### Appealing
 
 Only permanent resolutions, such as bans, or requests for public actions may be appealed. 
-To appeal a decision of the conduct team, contact the [Beman leads](GOVERNANCE.md) with your appeal and they will review the case.
+To appeal a decision of the conduct team, contact the [Beman leads](governance.md) with your appeal and they will review the case.
 
 In general, it is **not** appropriate to appeal a particular decision in public
 areas of GitHub or Discord. 

docs/BEMAN_STANDARD.md docs/beman_standard.mddocs/BEMAN_STANDARD.md renamed to docs/beman_standard.md

@@ -32,10 +32,7 @@ Libraries not falling in this category are out of scope.
 ## I have a personal/work project but I have no interest in it becoming a standard library. Does the Beman Project have anything for me?
 
 Yes!
-In our effort to create the highest-quality C++ libraries, we've established a set of templates, tools, and guidelines that are broadly applicable even for projects not destined to be standardized:
-
-* Our [Example Project](https://github.com/bemanproject/example) demonstrates a useful structure for organizing libraries
-* Our [CI Project](https://github.com/bemanproject/ci) utilizes Github Workflows to automate building, testing, and releasing libraries.
+In our effort to create the highest-quality C++ libraries, we've established a set of templates, tools, and guidelines that are broadly applicable even for projects not destined to be standardized. For example, our [Exemplar Project](https://github.com/bemanproject/exemplar) demonstrates a useful structure for organizing libraries
 
 ## Will libraries stay in Beman forever?
 

docs/CODE_OF_CONDUCT.md docs/code_of_conduct.mddocs/CODE_OF_CONDUCT.md renamed to docs/code_of_conduct.md

@@ -35,7 +35,7 @@ This includes strategic planning, setting goals, and ensuring the organization's
 This team should broadly understand both the Standardization process, the needs of library developers, and the concerns from Committee Members.
 The Beman Project Leads ultimately approve or change the process that we use for exposing Beman Libraries to the wider community.
 
-Beman Leads are currently: Jeff Garland, Inbal Levi, and David Sankel.
+Beman Leads are currently: Jeff Garland, Inbal Levi, and Eddie Nolan.
 
 ### 3.1.2 Adding and removing Beman Leads
 
@@ -71,7 +71,7 @@ Beman Project Leads ultimately decide the direction of the Project.
 
 # 5. Code of Conduct
 
-Please refer to our [Code of Conduct](CODE_OF_CONDUCT.md).
+Please refer to our [Code of Conduct](./code_of_conduct.md).
 
 # 5.1 Respectful Behavior:
 

docs/FAQ.md docs/faq.mddocs/FAQ.md renamed to docs/faq.md

@@ -0,0 +1,56 @@
+---
+sidebar_position: 4
+---
+
+<!--
+SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
+-->
+
+# Mission
+
+The Beman project's mission is to **support the efficient design and adoption of the highest quality C++ standard libraries** through implementation experience, user feedback, and technical expertise.
+
+The Beman project is named [in memory of Beman Dawes](https://bemanproject.org/blog/about-beman) - co-founder of [Boost](https://www.boost.org).
+
+---
+
+The Beman project was founded at C++Now in 2024, the project strives to aggregate libraries proposed for ISO standardization making a simple usage experience for the C++ Community to try out new libraries.
+
+---
+
+The Beman project's goals are broad, strategic propositions aligned with its mission and serve as guiding principles.
+An non-exhaustive list of those goals includes:
+
+## **[goals.support_for_authors]**
+
+**Support for Authors**. Assist library authors by providing appropriate tools and guidance.
+
+## **[goals.best_practices]**
+
+**Best Practices**. Promote adherence to industry standards and best practices.
+
+## **[goals.quality_assurance]**
+
+**Quality Assurance**. Evaluate and ensure the quality of libraries under the project.
+
+## **[goals.user_experience]**
+
+**User Experience**. Provide users with a seamless integration experience for consuming Beman libraries.
+
+## **[goals.feedback]**
+
+**Feedback Loops**. Facilitate effortless user feedback to help improve libraries.
+
+## **[goals.contributions]**
+
+**Inclusive Contribution**. Lower barriers to entry for new contributors and encourage broader participation.
+
+## **[goals.iso_integration]**
+
+**ISO Integration**. Deliver reference implementations for ISO proposals, including active paper development.
+
+## **[goals.public_presence]**
+
+**Public Presence**. Maintain a public website that communicates the project's purpose, offers user-friendly documentation, and helps authors structure their libraries.
+
+---