deploy: 45f9590

Author: nojaf

docs/end-users/Configuration.html

@@ -293,7 +293,7 @@ <h1><a name="Configuration" class="anchor" href="#Configuration">Configuration</
 commandline.<br />
 Your IDE should respect your settings, however the implementation of that is editor specific. Setting the configuration via
 UI might be available depending on the IDE.</p>
-<table class="pre"><tr><td><pre><code>version: 7.0.3+6dc12a1c2102c7b879506d86185d357adb8e658d</code></pre></td></tr></table>
+<table class="pre"><tr><td><pre><code>version: 7.0.3+45f9590b71e1460f9c50b95b8e6f74bf0bbabe83</code></pre></td></tr></table>
 <h2><a name="Usage" class="anchor" href="#Usage">Usage</a></h2>
 <p>Inside .editorconfig you can specify the file extension and code location to be use per config:</p>
 <pre class="fssnip highlighted"><code lang="fsharp"><span class="pn">[</span><span class="pn">*.</span><span class="id">fs</span><span class="pn">]</span>

docs/end-users/GeneratingCode.html

@@ -299,6 +299,11 @@ <h2><a name="Key-motivation" class="anchor" href="#Key-motivation">Key motivatio
 <li>It is easier to map your domain model to untyped syntax tree nodes and let Fantomas take care of the actual generation of code.</li>
 </ul>
 <p><strong>For mercy's sake don't use string concatenation when generating F# code, use Fantomas instead. It is battle tested and proven technology!</strong></p>
+<h2><a name="Consider-using-Fabulous-AST" class="anchor" href="#Consider-using-Fabulous-AST">Consider using Fabulous.AST</a></h2>
+<p>If you're looking to generate F# code programmatically, you might want to check out <a href="https://edgarfgp.github.io/Fabulous.AST/">Fabulous.AST</a> first.<br />
+Fabulous.AST provides a more user-friendly DSL built on top of Fantomas Oak AST, dramatically reducing the boilerplate code required to generate F# code.<br />
+It offers a concise and easier-to-use API compared to constructing Oak nodes directly, which can be quite verbose.</p>
+<p>The rest of this page documents how to work with Fantomas Oak AST directly, which is useful if you need more control or want to understand the underlying structure.</p>
 <h2><a name="Generating-source-code-from-scratch" class="anchor" href="#Generating-source-code-from-scratch">Generating source code from scratch</a></h2>
 <h3><a name="Example-syntax-tree" class="anchor" href="#Example-syntax-tree">Example syntax tree</a></h3>
 <p>To illustrate the API, lets generate a simple value binding: <code>let a = 0</code>.</p>
@@ -692,6 +697,11 @@ <h3><a name="Updates" class="anchor" href="#Updates">Updates</a></h3>
       Key motivation
     </a>
   </li>
+  <li class="level-2">
+    <a href="#Consider-using-Fabulous-AST">
+      Consider using Fabulous.AST
+    </a>
+  </li>
   <li class="level-2">
     <a href="#Generating-source-code-from-scratch">
       Generating source code from scratch

docs/end-users/StyleGuide.html

@@ -292,6 +292,9 @@ <h1><a name="Style-guide" class="anchor" href="#Style-guide">Style guide</a></h1
 - <a href="https://github.com/G-Research/fsharp-formatting-conventions">G-Research</a></p>
 <p>By default Fantomas  will format the code according to the Microsoft guide.<br />
 The benefit of these guides is that this allows us, as the F# community, to write code in the same manner.</p>
+<h2><a name="How-Fantomas-formats-code" class="anchor" href="#How-Fantomas-formats-code">How Fantomas formats code</a></h2>
+<p>Fantomas rewrites the entire source text after formatting. Think of it like a word document: Fantomas will re-type your entire text according to its rules in a new file.<br />
+It does not modify the original text. This approach ensures complete consistency and adherence to the formatting rules, but it means that all formatting decisions are made by Fantomas according to its opinionated style guide.</p>
 <h2><a name="Let-it-go" class="anchor" href="#Let-it-go">Let it go</a></h2>
 <p>If you are not used to having a code formatter, you might struggle a bit at first. A part of using a code formatter is about letting go how you wrote things and accept a common consistent style instead.<br />
 When embraced, this can truly be <strong>a liberation feeling</strong>. You can play <em>jazz</em> while typing the code, focus on the task at hand and have the same output as if anyone in your team would have written it.</p>
@@ -335,6 +338,11 @@ <h2><a name="Recommendations" class="anchor" href="#Recommendations">Recommendat
       Style guide
     </a>
   </li>
+  <li class="level-2">
+    <a href="#How-Fantomas-formats-code">
+      How Fantomas formats code
+    </a>
+  </li>
   <li class="level-2">
     <a href="#Let-it-go">
       Let it go