From baa23f47d6c9ca9c38ae79a3f0e6ef05461a4dad Mon Sep 17 00:00:00 2001
From: zerinoid <leo.zerino@gmail.com>
Date: Thu, 6 Jul 2023 19:55:58 -0300
Subject: [PATCH] fix: remove about page

---
 src/pages/about.tsx | 45 ---------------------------------------------
 1 file changed, 45 deletions(-)
 delete mode 100644 src/pages/about.tsx

diff --git a/src/pages/about.tsx b/src/pages/about.tsx
deleted file mode 100644
index ee4c3f1..0000000
--- a/src/pages/about.tsx
+++ /dev/null
@@ -1,45 +0,0 @@
-import PrimaryLayout from '../components/layouts/primary/PrimaryLayout';
-import SidebarLayout from '../components/layouts/sidebar/SidebarLayout';
-import { NextPageWithLayout } from './_app';
-
-const About: NextPageWithLayout = () => {
-  return (
-    <section>
-      <h2>Layout Example (About)</h2>
-      <p>
-        This example adds a property <code>getLayout</code> to your page,
-        allowing you to return a React component for the layout. This allows you
-        to define the layout on a per-page basis. Since we&apos;re returning a
-        function, we can have complex nested layouts if desired.
-      </p>
-      <p>
-        When navigating between pages, we want to persist page state (input
-        values, scroll position, etc.) for a Single-Page Application (SPA)
-        experience.
-      </p>
-      <p>
-        This layout pattern will allow for state persistence because the React
-        component tree is persisted between page transitions. To preserve state,
-        we need to prevent the React component tree from being discarded between
-        page transitions.
-      </p>
-      <h3>Try It Out</h3>
-      <p>
-        To visualize this, try tying in the search input in the{' '}
-        <code>Sidebar</code> and then changing routes. You&apos;ll notice the
-        input state is persisted.
-      </p>
-    </section>
-  );
-};
-
-export default About;
-
-About.getLayout = page => {
-  return (
-    <PrimaryLayout>
-      <SidebarLayout />
-      {page}
-    </PrimaryLayout>
-  );
-};