doc updates

docs/config.toml

@@ -26,10 +26,6 @@ enableRobotsTXT = true
   tag = "tags"
 
 [params]
-
-  # Include custom JS files
-  customJS = ["js/clarity.js"]
-
   # (Optional, default 6) Set how many table of contents levels to be showed on page.
   # Use false to hide ToC, note that 0 will default to 6 (https://gohugo.io/functions/default/)
   # You can also specify this parameter per page in front matter.

docs/content/contributing/website/_index.md

@@ -33,7 +33,7 @@ When in VS Code you should be able to open a terminal and run the below commands
 
 ```text
 cd docs
-hugo server -D
+hugo server -D // you can add "--poll 700ms", if file changes are not detected
 ```
 
 ### Software/Applications

docs/content/faq/_index.md

@@ -401,29 +401,7 @@ The high level steps are:
 
 ### How can I use Bicep modules through the Public Registry?
 
-Use the [Bicep Visual Studio Code extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-bicep) to author your Bicep template and explore modules published in the Bicep Public Registry. For more details, see the the below example steps.
-
-{{< hint type=note >}}
-The Bicep VSCode extension is reading metadata through [this JSON file](https://live-data.bicep.azure.com/module-index). All modules are added to this file, as part of the publication process.
-{{< /hint >}}
-
-1. When authoring a new Bicep file, use the [VS Code extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-bicep) to explore the modules published in the Bicep Public Registry.
-<img src="../img/faq/use-bicep-module-01.png" width=100% alt="Select br/public:">
-
-2. Expanding on this you can see the AVM modules that are published.
-<img src="../img/faq/use-bicep-module-02.png" width=100% alt="Select module from the Public Bicep Registry">
-
-3. Selecting the module expands on the current available versions.
-<img src="../img/faq/use-bicep-module-03.png" width=100% alt="Choose from the available versions">
-
-4. Setting required properties exposes what is required on the module.
-<img src="../img/faq/use-bicep-module-04.png" width=100% alt="Select required-properties">
-
-5. Hovering over the `myTestModule` name exposes the module's documentation URL.
-<img src="../img/faq/use-bicep-module-05.png" width=100% alt="Hover over the module name">
-
-6. Clicking on the link opens up the Bicep Registry Repo for the AVM module's source code, where you can find the documentation detailing all the module's functionality, input parameters and outputs, while providing various examples.
-<img src="../img/faq/use-bicep-module-06.png" width=100% alt="See the module's documentation online">
+Please see the Bicep Quickstart guide [here](/Azure-Verified-Modules/usage/quickstart/bicep/).
 
 ---
 

docs/content/usage/quickstart/_index.md

@@ -6,17 +6,16 @@ geekdocAnchor: true
 geekdocCollapseSection: true
 ---
 
-- this section describes the simplest way to get started with the project
-- a few sentences about why I should use AVM (and/or the kv module in this example)
-- am I "safe" to use the default values?
-- where can I find some examples? how can I find out all the features the kv module has to offer?
-- deploying a key vault the simplest way possible
-- prerequisites (VS code, packages, PS modules, etc.)
-- use story telling / screenshots from [FAQ](/Azure-Verified-Modules/faq/#how-can-i-use-bicep-modules-through-the-public-registry)
-  - how do I explore what modules are there?
-  - what are the built-in features of the key-vault module
-  - UDTs
-  - intellisense
-  - explore the source of the kv module without leaving VS code
-  - how can I see the readme of the kv module from vs code
-  - what if there's a missing feature? --> file a module issue
+This quickstart section describes the simplest way to get started with the project by providing step-by-step instructions and essential information, allowing you to leverage the benefits of AVM with minimal effort. It guides you through the initial setup, including the necessary tools and configurations, to help you quickly deploy and manage your Azure resources and solutions using Azure Verified Modules (AVM).
+
+## Why should I use Azure Verified Modules?
+
+Using AVM ensures that your infrastructure-as-code deployments adhere to Microsoft's best practices and guidelines, providing a consistent and reliable foundation for your cloud solutions. By leveraging AVM, you can accelerate your development process, reduce the risk of misconfigurations, and enhance the security and compliance of your applications. The AVM Key Vault resource module, used as an example through this chapter, simplifies the deployment and management of Azure Key Vaults, ensuring secure storage and access to your secrets, keys, and certificates.
+
+## Am I "safe" to use the default values?
+
+Using the default values provided by AVM is generally safe as they are configured to follow best practices and ensure a secure and reliable setup. However, it is important to review these values to ensure they meet your specific requirements and compliance needs. Customizing the default values may be necessary to align with your organization's policies and the specific needs of your project.
+
+## Where can I find some examples? How can I find out all the features a given module has to offer?
+
+You can find examples and detailed documentation for the each AVM module in their respective code repository's `README.MD` file that details all the features, input parameters, and outputs. The module's documentation also provides comprehensive usage examples, covering various scenarios and configurations. Additionally, you can explore the module's source code repository. This information will help you understand the full capabilities of the module and how to effectively integrate it into your projects.