Article about Feliz and Fable React

docs/faq/faq-felizandfable.md

@@ -15,8 +15,8 @@ For example:
 
 ```fsharp
 h1 [ Style [ Color "Tomato" ] ] [
-    p [] [ text [ Value "Hello" ] [] ] // no props
-    p [] [ text [ Value "Another paragraph" ] [] ] // no props
+    p [] [ str "Hello" ] // no props
+    p [] [ str "Another paragraph" ] // no props
     h2 [ Style [ Color "Blue" ] ] [] // no child elements
 ]
 ```
@@ -32,7 +32,7 @@ Html.h1 [
     prop.style [ style.color "Tomato" ]
     prop.children [
         Html.p [ prop.text "Hello" ]
-        Html.p [ prop.text "Another paragraph" ]
+        Html.p "Another paragraph"
         Html.h2 [ prop.style [ style.backgroundColor "Blue" ] ]
     ]
 ]
@@ -54,12 +54,8 @@ Html.h1 [ // not fine - can't mix and match attributes and elements
     prop.style [ style.color "Tomato" ]
     Html.p [ prop.text "Hello" ]
 ]
-```
-
-In order to allow both attributes and elements in the same list, Feliz introduces the `children` node:
 
-```fsharp
-Html.h1 [ // this is now fine
+Html.h1 [ // fine, adding props, and adding children using prop.children
     prop.style [ style.color "Tomato" ]
     prop.children [ Html.p [ prop.text "Hello" ] ]
 ]
@@ -68,6 +64,7 @@ Html.h1 [ // this is now fine
 ## Guidance
 * Fable.React was created initially, whilst Feliz was developed some time later.
 * Feliz has better support for React interop and the majority of the community nowadays uses the Feliz DSL style for developing components.
-* As they are both wrappers around the same underlying technology (React) and Feliz uses some parts of Fable.React, you can actually mix and match the two in your applications as required.
+* Fable.React and Feliz can be mixed into your application if required (for progressive migration for example)
+
 
 * Also see [My journey with Feliz | A comparison between Fable.React and Feliz](https://github.com/Zaid-Ajaj/Feliz/issues/155).

mkdocs.yml

@@ -42,6 +42,13 @@ extra:
   analytics:
     provider: google
     property: G-WED2S9FLSL
+  consent:
+    title: Cookie consent
+    description:
+      We use cookies to recognise your repeated visits and preferences, as well
+      as to measure the effectiveness of our documentation and whether users
+      find what they're searching for. With your consent, you're helping us to
+      make our documentation better.
 
 nav:
   - Home: "index.md"