chore(about): format and add link to project section

Author: chalin

docsy.dev/.prettierignore

@@ -1,6 +1,7 @@
 # cSpell:ignore lookandfeel
 
 /content/**/*.*
+!/content/en/about/**/*.*
 !/content/en/blog/**/*.*
 !/content/en/community/**/*.*
 !/content/en/docs/_index.md

docsy.dev/config/_default/params.yaml

@@ -7,7 +7,7 @@
 #   status: archived # Then fetch include
 
 version: &docsyVersion 0.14.3-dev
-tdBuildId: 015-over-main-e4c11620
+tdBuildId: 016-over-main-85549b3d
 versionLatest: &versionLatest v0.14.3
 version_menu: *docsyVersion
 version_menu_pagelinks: true

docsy.dev/content/en/about/index.md

@@ -4,7 +4,7 @@ linkTitle: About
 description: >-
   Docsy is a pre-configured Hugo theme that provides the core features and
   behaviors needed to create a technical documentation site
-menu: {main: {weight: 10}}
+menu: { main: { weight: 10 } }
 ---
 
 {{% blocks/cover
@@ -21,29 +21,56 @@ menu: {main: {weight: 10}}
 
 {{% blocks/section color="white" %}}
 
-Use Docsy to set up your documentation website, including an optional Blog section, and then spend your time focusing on authoring technical content. Depending on how you choose to configure Docsy and whether you use a hosting service that supports continuous builds, you can even just add your Markdown or HTML content file into a folder on your source repository, and then sit back while it automatically gets added to your site - complete with updated menus.
+Use Docsy to set up your documentation website, including an optional Blog
+section, and then spend your time focusing on authoring technical content.
+Depending on how you choose to configure Docsy and whether you use a hosting
+service that supports continuous builds, you can even just add your Markdown or
+HTML content file into a folder on your source repository, and then sit back
+while it automatically gets added to your site - complete with updated menus.
 
-Read on to find out more, or visit our [documentation](/docs/) to get started!
+To find out more, read on, or skip to the [documentation](/docs/). For project details, see the [project](/project/) page.
 
 ## So what’s a technical documentation site?
 
-A technical documentation site is a website that your users can visit to find the documentation for your technical project.  Your documentation set contains all the information you think your users might need to engage with your project, from overviews that help them understand what the project is for, to instructions for specific tasks. Depending on the size of the project, a documentation set can be a page or two or an entire “book” with different types of information.
-
-**Most users don’t want to have to spend much time looking at docs - they want to try your great project!** So how do you make sure your technical documentation set gives users what they need to easily understand your project and get things done? We think a good technical documentation set should be:
-
-*   **Reliable**: Is it true?
-*   **Comprehensive**: Does it have all the information your target users might need?
-*   **Well-organized and navigable**: Can the user find the information they need? Are similar types of information (all the information about a feature, all your reference information) grouped together?
-
-If you have users around the world, you might also want to provide your content in multiple languages, and if you have an open source project, you’ll probably want your users to be able to contribute to the docs.
-
-Once you have your content, you use a technical documentation site to publish your technical documentation set online for your users. In addition to your documentation, your site might also contain material like contact information, a blog, or information about how to contribute to the project.
+A technical documentation site is a website that your users can visit to find
+the documentation for your technical project. Your documentation set contains
+all the information you think your users might need to engage with your project,
+from overviews that help them understand what the project is for, to
+instructions for specific tasks. Depending on the size of the project, a
+documentation set can be a page or two or an entire “book” with different types
+of information.
+
+**Most users don’t want to have to spend much time looking at docs - they want
+to try your great project!** So how do you make sure your technical
+documentation set gives users what they need to easily understand your project
+and get things done? We think a good technical documentation set should be:
+
+- **Reliable**: Is it true?
+- **Comprehensive**: Does it have all the information your target users might
+  need?
+- **Well-organized and navigable**: Can the user find the information they need?
+  Are similar types of information (all the information about a feature, all
+  your reference information) grouped together?
+
+If you have users around the world, you might also want to provide your content
+in multiple languages, and if you have an open source project, you’ll probably
+want your users to be able to contribute to the docs.
+
+Once you have your content, you use a technical documentation site to publish
+your technical documentation set online for your users. In addition to your
+documentation, your site might also contain material like contact information, a
+blog, or information about how to contribute to the project.
 
 ## How does Docsy help?
 
-Particularly when working with open source projects, it can be difficult to figure out how to turn all your product knowledge into a website that helps and engages your users. **Enter Docsy!**
+Particularly when working with open source projects, it can be difficult to
+figure out how to turn all your product knowledge into a website that helps and
+engages your users. **Enter Docsy!**
 
-Docsy gives you a theme for the [Hugo](https://gohugo.io/) static site generator, an established open source tool that builds ready-to-serve websites from a set of theme and content files. The Docsy theme provides you with useful stuff for a technical documentation site that *isn’t* your own content:
+Docsy gives you a theme for the [Hugo](https://gohugo.io/) static site
+generator, an established open source tool that builds ready-to-serve websites
+from a set of theme and content files. The Docsy theme provides you with useful
+stuff for a technical documentation site that _isn’t_ your own content:
 
 <table>
   <tr>
@@ -92,51 +119,77 @@ Docsy gives you a theme for the [Hugo](https://gohugo.io/) static site generator
 
 ### Simple authoring and publishing
 
-Author your content in the Markdown or HTML and then immediately test it with Hugo's local server. Once you are ready to
-publish, add that content to your project and deploy it to your site using any of Hugo’s supported options.
+Author your content in the Markdown or HTML and then immediately test it with
+Hugo's local server. Once you are ready to publish, add that content to your
+project and deploy it to your site using any of Hugo’s supported options.
 [Learn more...](/docs/deployment/)
 
 ### Built-in integration with common tools
 
-The Docsy template currently includes built-in integration with the following tools:
-
-* [**GitHub**](https://github.com): Get in-page links directly to your GitHub repo and provide your users with a
-   convenient pathway to providing feedback, opening issues, and even suggesting changes through Pull Requests.
-* [**Google Analytics**](https://analytics.google.com/analytics/web/): Easily connect your Google Analytics account to your
-   site.
-* [**Google Custom Search**](https://cse.google.com/cse/): Use Google Custom Search for in-site search queries, or
-  configure your site to search the web.
-* [**Algolia DocSearch**](https://docsearch.algolia.com): Let your users search your site with Algolia DocSearch.
-* [**Lunr**](https://lunrjs.com/): Local indexing and search for your site without the need for external search services.
+The Docsy template currently includes built-in integration with the following
+tools:
+
+- [**GitHub**](https://github.com): Get in-page links directly to your GitHub
+  repo and provide your users with a convenient pathway to providing feedback,
+  opening issues, and even suggesting changes through Pull Requests.
+- [**Google Analytics**](https://analytics.google.com/analytics/web/): Easily
+  connect your Google Analytics account to your site.
+- [**Google Custom Search**](https://cse.google.com/cse/): Use Google Custom
+  Search for in-site search queries, or configure your site to search the web.
+- [**Algolia DocSearch**](https://docsearch.algolia.com): Let your users search
+  your site with Algolia DocSearch.
+- [**Lunr**](https://lunrjs.com/): Local indexing and search for your site
+  without the need for external search services.
 
 ### Make it your own
 
-You can configure the Docsy theme as much or as little as you like, anything from changing the colors and images to adding your own type of page layout. [Learn more...](/docs/content/lookandfeel/)
+You can configure the Docsy theme as much or as little as you like, anything
+from changing the colors and images to adding your own type of page layout.
+[Learn more...](/docs/content/lookandfeel/)
 
 ### Get organized
 
-We believe a well-organized documentation set can really help your users find the information they need, when they need it - whether it’s a “Hello World” tutorial when they’re starting out or a single core task they need to do to finish a complicated app. We also believe that having well-organized docs helps you create comprehensive docs, as it’s easier to see when you’re missing something important. [Learn more...](/docs/best-practices/organizing-content/)
+We believe a well-organized documentation set can really help your users find
+the information they need, when they need it - whether it’s a “Hello World”
+tutorial when they’re starting out or a single core task they need to do to
+finish a complicated app. We also believe that having well-organized docs helps
+you create comprehensive docs, as it’s easier to see when you’re missing
+something important. [Learn more...](/docs/best-practices/organizing-content/)
 
-Docsy also provides autogenerated site navigation based on how you organize your source files, so once you’ve organized your docs in folders in GitHub or other source control, you’ve got menus for your users to quickly reach the doc they need. [Learn more...](/docs/content/navigation/)
+Docsy also provides autogenerated site navigation based on how you organize your
+source files, so once you’ve organized your docs in folders in GitHub or other
+source control, you’ve got menus for your users to quickly reach the doc they
+need. [Learn more...](/docs/content/navigation/)
 
 ### Keep up to date
 
-Spend time setting up your technical documentation site once, and then focus on what you do best. We work closely with
-the Hugo team and have individuals actively maintaining the Docsy theme. You can easily get and
-apply Docsy updates to your site, as well as open feature requests to improve the
-template, or even add new behaviors. [Learn more...](/docs/updating/)
+Spend time setting up your technical documentation site once, and then focus on
+what you do best. We work closely with the Hugo team and have individuals
+actively maintaining the Docsy theme. You can easily get and apply Docsy updates
+to your site, as well as open feature requests to improve the template, or even
+add new behaviors. [Learn more...](/docs/updating/)
 
 ### Focus on great content
 
-Because Docsy helps you create and serve a well-organized, navigable technical documentation set, it frees you up to create and maintain great reliable, comprehensive content that your users can enjoy and trust.
+Because Docsy helps you create and serve a well-organized, navigable technical
+documentation set, it frees you up to create and maintain great reliable,
+comprehensive content that your users can enjoy and trust.
 
 ## What's next for Docsy?
 
-Docsy is an open source project and we love getting patches and contributions to make Docsy and its docs even better. We hope to continue to make improvements to the theme along with the Docsy community.
+Docsy is an open source project and we love getting patches and contributions to
+make Docsy and its docs even better. We hope to continue to make improvements to
+the theme along with the Docsy community.
+
+Visit our [Issues](https://github.com/google/docsy/issues) to see what we're
+currently working on. If there's something you'd like to see in Docsy, please
+create an issue yourself - or assign yourself an issue if you'd like to fix or
+add something! See our [contribution guidelines](/docs/contribution-guidelines/)
+for more information.
 
-Visit our [Issues](https://github.com/google/docsy/issues) to see what we're currently working on. If there's something you'd like to see in Docsy, please create an issue yourself - or assign yourself an issue if you'd like to fix or add something! See our [contribution guidelines](/docs/contribution-guidelines/) for more information.
+You can find out how to update your site to the latest version of Docsy in
+[Keeping the theme up to date](/docs/updating/).
 
-You can find out how to update your site to the latest version of Docsy in [Keeping the theme up to date](/docs/updating/).
 <!-- There must not be a blank line at the end of this file otherwise it creates an empty paragraph in the rendered page -->
 
 {{% /blocks/section %}}

package.json

@@ -1,6 +1,6 @@
 {
   "name": "docsy",
-  "version": "0.14.3-dev+015-over-main-e4c11620",
+  "version": "0.14.3-dev+016-over-main-85549b3d",
   "repository": "github:google/docsy",
   "homepage": "https://www.docsy.dev",
   "license": "Apache-2.0",