Built site for gh-pages

Author: chriscarrollsmith

.nojekyll

@@ -1 +1 @@
-1c863cf9
+cb967068

docs/architecture.html

@@ -132,7 +132,7 @@
     <h2 id="toc-title">On this page</h2>
 
   <ul>
-  <li><a href="#architecture" id="toc-architecture" class="nav-link active" data-scroll-target="#architecture">Architecture</a></li>
+  <li><a href="#data-flow" id="toc-data-flow" class="nav-link active" data-scroll-target="#data-flow">Data flow</a></li>
   </ul>
 </nav>
     </div>
@@ -158,13 +158,13 @@ <h1 class="title">Architecture</h1>
 </header>
 
 
-<section id="architecture" class="level2">
-<h2 class="anchored" data-anchor-id="architecture">Architecture</h2>
+<section id="data-flow" class="level2">
+<h2 class="anchored" data-anchor-id="data-flow">Data flow</h2>
 <p>This application uses a Post-Redirect-Get (PRG) pattern. The user submits a form, which sends a POST request to a FastAPI endpoint on the server. The database is updated, and the user is redirected to a GET endpoint, which fetches the updated data and re-renders the Jinja2 page template with the new data.</p>
 <div class="quarto-figure quarto-figure-center">
 <figure class="figure">
 <p><img src="static/webapp_flow.png" class="img-fluid figure-img"></p>
-<figcaption>Webapp Flow</figcaption>
+<figcaption>Data flow diagram</figcaption>
 </figure>
 </div>
 <p>The advantage of the PRG pattern is that it is very straightforward to implement and keeps most of the rendering logic on the server side. The disadvantage is that it requires an extra round trip to the database to fetch the updated data, and re-rendering the entire page template may be less efficient than a partial page update on the client side.</p>

docs/static/reset_flow.png

@@ -67,14 +67,14 @@
     "href": "docs/architecture.html",
     "title": "Architecture",
     "section": "",
-    "text": "This application uses a Post-Redirect-Get (PRG) pattern. The user submits a form, which sends a POST request to a FastAPI endpoint on the server. The database is updated, and the user is redirected to a GET endpoint, which fetches the updated data and re-renders the Jinja2 page template with the new data.\n\n\n\nWebapp Flow\n\n\nThe advantage of the PRG pattern is that it is very straightforward to implement and keeps most of the rendering logic on the server side. The disadvantage is that it requires an extra round trip to the database to fetch the updated data, and re-rendering the entire page template may be less efficient than a partial page update on the client side."
+    "text": "This application uses a Post-Redirect-Get (PRG) pattern. The user submits a form, which sends a POST request to a FastAPI endpoint on the server. The database is updated, and the user is redirected to a GET endpoint, which fetches the updated data and re-renders the Jinja2 page template with the new data.\n\n\n\nData flow diagram\n\n\nThe advantage of the PRG pattern is that it is very straightforward to implement and keeps most of the rendering logic on the server side. The disadvantage is that it requires an extra round trip to the database to fetch the updated data, and re-rendering the entire page template may be less efficient than a partial page update on the client side."
   },
   {
-    "objectID": "docs/architecture.html#architecture",
-    "href": "docs/architecture.html#architecture",
+    "objectID": "docs/architecture.html#data-flow",
+    "href": "docs/architecture.html#data-flow",
     "title": "Architecture",
     "section": "",
-    "text": "This application uses a Post-Redirect-Get (PRG) pattern. The user submits a form, which sends a POST request to a FastAPI endpoint on the server. The database is updated, and the user is redirected to a GET endpoint, which fetches the updated data and re-renders the Jinja2 page template with the new data.\n\n\n\nWebapp Flow\n\n\nThe advantage of the PRG pattern is that it is very straightforward to implement and keeps most of the rendering logic on the server side. The disadvantage is that it requires an extra round trip to the database to fetch the updated data, and re-rendering the entire page template may be less efficient than a partial page update on the client side."
+    "text": "This application uses a Post-Redirect-Get (PRG) pattern. The user submits a form, which sends a POST request to a FastAPI endpoint on the server. The database is updated, and the user is redirected to a GET endpoint, which fetches the updated data and re-renders the Jinja2 page template with the new data.\n\n\n\nData flow diagram\n\n\nThe advantage of the PRG pattern is that it is very straightforward to implement and keeps most of the rendering logic on the server side. The disadvantage is that it requires an extra round trip to the database to fetch the updated data, and re-rendering the entire page template may be less efficient than a partial page update on the client side."
   },
   {
     "objectID": "docs/authentication.html",

search.json

@@ -14,11 +14,11 @@
   </url>
   <url>
     <loc>https://Promptly-Technologies-LLC.github.io/fastapi-jinja2-postgres-webapp/docs/architecture.html</loc>
-    <lastmod>2024-11-19T20:26:21.009Z</lastmod>
+    <lastmod>2024-11-19T21:37:01.245Z</lastmod>
   </url>
   <url>
     <loc>https://Promptly-Technologies-LLC.github.io/fastapi-jinja2-postgres-webapp/docs/authentication.html</loc>
-    <lastmod>2024-11-19T16:55:55.525Z</lastmod>
+    <lastmod>2024-11-19T21:37:41.606Z</lastmod>
   </url>
   <url>
     <loc>https://Promptly-Technologies-LLC.github.io/fastapi-jinja2-postgres-webapp/docs/customization.html</loc>