diff --git a/.commitlintrc.json b/.commitlintrc.json
new file mode 100644
index 0000000..c30e5a9
--- /dev/null
+++ b/.commitlintrc.json
@@ -0,0 +1,3 @@
+{
+ "extends": ["@commitlint/config-conventional"]
+}
diff --git a/.env.example b/.env.example
new file mode 100644
index 0000000..815a601
--- /dev/null
+++ b/.env.example
@@ -0,0 +1,35 @@
+# -----------------------------------------------------------------------------
+# App
+# -----------------------------------------------------------------------------
+# NextAuth Secret (Generate using: `openssl rand -base64 32`)
+NEXT_PUBLIC_APP_URL=https://yourdomain.com/
+NEXTAUTH_URL=http://localhost:3000
+NEXTAUTH_SECRET=YOUR_NEXTAUTH_SECRET
+
+# -----------------------------------------------------------------------------
+# Google OAuth
+# -----------------------------------------------------------------------------
+GOOGLE_CLIENT_ID=YOUR_GOOGLE_CLIENT_ID
+GOOGLE_CLIENT_SECRET=YOUR_GOOGLE_CLIENT_SECRET
+
+# -----------------------------------------------------------------------------
+# Database (Neon - PostgreSQL)
+# -----------------------------------------------------------------------------
+DATABASE_URL="postgresql://username:password@host/database?sslmode=require"
+DATABASE_URL_UNPOOLED="postgresql://username:password@host/database?sslmode=require"
+
+# -----------------------------------------------------------------------------
+# Resend API
+# -----------------------------------------------------------------------------
+RESEND_API_KEY=YOUR_RESEND_API_KEY
+
+# -----------------------------------------------------------------------------
+# Stripe
+# -----------------------------------------------------------------------------
+STRIPE_API_KEY=YOUR_STRIPE_API_KEY
+STRIPE_WEBHOOK_SECRET=YOUR_STRIPE_WEBHOOK_SECRET
+NEXT_PUBLIC_STRIPE_PRO_MONTHLY_PLAN_ID=price_xxx
+NEXT_PUBLIC_STRIPE_PRO_YEARLY_PLAN_ID=price_xxx
+NEXT_PUBLIC_STRIPE_BUSINESS_MONTHLY_PLAN_ID=price_xxx
+NEXT_PUBLIC_STRIPE_BUSINESS_YEARLY_PLAN_ID=price_xxx
+
diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml
new file mode 100644
index 0000000..2f8edf5
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug_report.yml
@@ -0,0 +1,43 @@
+name: ๐ Bug report
+description: Create a bug report to help us improve ProjectX โจ
+title: "Bug: "
+labels: [๐ Exploration Pending, ๐ bug]
+body:
+ - type: markdown
+ attributes:
+ value: |
+ Thanks for taking the time to fill out this bug report!
+ - type: textarea
+ attributes:
+ label: Describe the bug
+ description: A clear and concise description of what the bug is.
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Steps to reproduce
+ description: Describe how to reproduce the behavior.
+ placeholder: |
+ 1. Go to '...'
+ 2. Click on '...'
+ 3. Scroll down to '...'
+ 4. See error
+ validations:
+ required: true
+ - type: dropdown
+ attributes:
+ multiple: true
+ label: Browsers
+ description: Select the browsers where the issue can be reproduced (that you know of).
+ options:
+ - "Chrome"
+ - "Firefox"
+ - "Safari"
+ - "Edge"
+ - "Opera"
+ - "Other (add additional context)"
+ - type: input
+ id: context
+ attributes:
+ label: Additional context (Is this in dev or production?)
+ description: Add any other context about the problem or helpful links here.
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
new file mode 100644
index 0000000..73226dd
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -0,0 +1,5 @@
+blank_issues_enabled: true
+contact_links:
+ - name: โ Ask a question
+ url: https://discord.gg/8BkX9hJRXs
+ about: Ask questions about ProjectX
diff --git a/.github/ISSUE_TEMPLATE/feature_request.yml b/.github/ISSUE_TEMPLATE/feature_request.yml
new file mode 100644
index 0000000..ad9b27b
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/feature_request.yml
@@ -0,0 +1,43 @@
+name: ๐ Feature request
+description: Suggest an idea for this project ๐ก
+title: "Feature: "
+labels: [๐ Exploration Pending, ๐ก feature]
+body:
+ - type: markdown
+ attributes:
+ value: |
+ Thanks for taking the time to fill out this feature request!
+ - type: dropdown
+ attributes:
+ multiple: false
+ label: Type of feature
+ description: Select the type of feature request, the lowercase should also be the PR prefix.
+ options:
+ - "๐ก Feature"
+ - "๐ Fix"
+ - "๐ Documentation"
+ - "๐จ Style"
+ - "๐งโ๐ป Refactor"
+ - "๐ฅ Performance"
+ - "โ Test"
+ - "๐ค Build"
+ - "๐ CI"
+ - "๐ฆ Chore"
+ - "โฉ Revert"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Current behavior
+ description: Is your feature request related to a problem? Please describe.
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Suggested solution
+ description: Describe the solution you'd like.
+ - type: input
+ id: context
+ attributes:
+ label: Additional context
+ description: Add any other context about the problem or helpful links here.
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
new file mode 100644
index 0000000..c429bbe
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,66 @@
+## Description
+
+
+
+## What type of PR is this? (check all applicable)
+
+- [ ] ๐ก Feature
+- [ ] ๐ Bug Fix
+- [ ] ๐ Documentation Update
+- [ ] ๐จ Style
+- [ ] ๐งโ๐ป Code Refactor
+- [ ] ๐ฅ Performance Improvements
+- [ ] โ Test
+- [ ] ๐ค Build
+- [ ] ๐ CI
+- [ ] ๐ฆ Chore (Release)
+- [ ] โฉ Revert
+
+## Related Tickets & Documents
+
+
+
+## Mobile & Desktop Screenshots/Recordings
+
+
+
+## Steps to QA
+
+
+
+## Added to documentation?
+
+- [ ] ๐ README.md
+- [ ] ๐ no documentation needed
+
+## [optional] Are there any post-deployment tasks we need to perform?
+
+## [optional] What gif best describes this PR or how it makes you feel?
+
+
+
+
diff --git a/.github/workflows/take-issue.yml b/.github/workflows/take-issue.yml
new file mode 100644
index 0000000..978d01b
--- /dev/null
+++ b/.github/workflows/take-issue.yml
@@ -0,0 +1,23 @@
+# .github/workflows/take.yml
+name: Assign issue to contributor
+on:
+ issue_comment:
+
+jobs:
+ assign:
+ name: Take an issue
+ runs-on: ubuntu-latest
+ permissions:
+ issues: write
+ steps:
+ - name: take the issue
+ uses: bdougie/take-action@main
+ with:
+ message:
+ Thanks for taking this issue! Let us know if you have any questions!
+ blockingLabels: in progress
+ blockingLabelsMessage:
+ This issue is already taken by someone else and is in progress. You
+ can find another one by surfing the issues page.
+ trigger: .take
+ token: ${{ secrets.GITHUB_TOKEN }}
diff --git a/.gitignore b/.gitignore
new file mode 100644
index 0000000..09ff7e3
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1,52 @@
+# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
+
+# dependencies
+node_modules
+.pnp
+.pnp.js
+
+# turbo
+.turbo/
+.turbo/
+
+# testing
+coverage
+
+# next.js
+.next/
+out/
+
+# build
+build
+dist
+
+# misc
+.DS_Store
+*.pem
+
+# debug
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+.pnpm-debug.log*
+
+# local env files
+.env*.local
+.env
+
+# vercel
+.vercel
+
+# typescript
+*.tsbuildinfo
+next-env.d.ts
+
+# email
+.react-email/
+
+.vscode
+.contentlayer
+
+#API
+.wrangler.toml
+wrangler.toml
diff --git a/.husky/commit-msg b/.husky/commit-msg
new file mode 100755
index 0000000..4974c35
--- /dev/null
+++ b/.husky/commit-msg
@@ -0,0 +1,4 @@
+#!/usr/bin/env sh
+. "$(dirname -- "$0")/_/husky.sh"
+
+npx commitlint --edit $1
diff --git a/.husky/pre-commit b/.husky/pre-commit
new file mode 100755
index 0000000..0da96d6
--- /dev/null
+++ b/.husky/pre-commit
@@ -0,0 +1,4 @@
+#!/usr/bin/env sh
+. "$(dirname -- "$0")/_/husky.sh"
+
+npx pretty-quick --staged
diff --git a/.npmrc b/.npmrc
new file mode 100644
index 0000000..3aba4f1
--- /dev/null
+++ b/.npmrc
@@ -0,0 +1,18 @@
+# Expo doesn't play nice with pnpm by default.
+# The symbolic links of pnpm break the rules of Expo monorepos.
+# @link https://docs.expo.dev/guides/monorepos/#common-issues
+node-linker=hoisted
+
+# In order to cache Prisma correctly
+public-hoist-pattern[]=*prisma*
+
+# FIXME: @prisma/client is required by the @acme/auth,
+# but we don't want it installed there since it's already
+# installed in the @acme/db package
+strict-peer-dependencies=false
+
+# Prevent pnpm from adding the "workspace:"" prefix to local
+# packages as it casues issues with manypkg
+# @link https://pnpm.io/npmrc#prefer-workspace-packages
+save-workspace-protocol=false
+prefer-workspace-packages=true
diff --git a/.nvmrc b/.nvmrc
new file mode 100644
index 0000000..790e110
--- /dev/null
+++ b/.nvmrc
@@ -0,0 +1 @@
+v20.10.0
diff --git a/.prettierignore b/.prettierignore
new file mode 100644
index 0000000..3aea320
--- /dev/null
+++ b/.prettierignore
@@ -0,0 +1,5 @@
+dist
+node_modules
+.next
+build
+.contentlayer
\ No newline at end of file
diff --git a/LICENSE.md b/LICENSE.md
new file mode 100644
index 0000000..162676c
--- /dev/null
+++ b/LICENSE.md
@@ -0,0 +1,661 @@
+ GNU AFFERO GENERAL PUBLIC LICENSE
+ Version 3, 19 November 2007
+
+Copyright (C) 2007 Free Software Foundation, Inc.
+Everyone is permitted to copy and distribute verbatim copies
+of this license document, but changing it is not allowed.
+
+ Preamble
+
+The GNU Affero General Public License is a free, copyleft license for
+software and other kinds of works, specifically designed to ensure
+cooperation with the community in the case of network server software.
+
+The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works. By contrast,
+our General Public Licenses are intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users.
+
+When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
+
+Developers that use our General Public Licenses protect your rights
+with two steps: (1) assert copyright on the software, and (2) offer
+you this License which gives you legal permission to copy, distribute
+and/or modify the software.
+
+A secondary benefit of defending all users' freedom is that
+improvements made in alternate versions of the program, if they
+receive widespread use, become available for other developers to
+incorporate. Many developers of free software are heartened and
+encouraged by the resulting cooperation. However, in the case of
+software used on network servers, this result may fail to come about.
+The GNU General Public License permits making a modified version and
+letting the public access it on a server without ever releasing its
+source code to the public.
+
+The GNU Affero General Public License is designed specifically to
+ensure that, in such cases, the modified source code becomes available
+to the community. It requires the operator of a network server to
+provide the source code of the modified version running there to the
+users of that server. Therefore, public use of a modified version, on
+a publicly accessible server, gives the public access to the source
+code of the modified version.
+
+An older license, called the Affero General Public License and
+published by Affero, was designed to accomplish similar goals. This is
+a different license, not a version of the Affero GPL, but Affero has
+released a new version of the Affero GPL which permits relicensing under
+this license.
+
+The precise terms and conditions for copying, distribution and
+modification follow.
+
+ TERMS AND CONDITIONS
+
+0. Definitions.
+
+"This License" refers to version 3 of the GNU Affero General Public License.
+
+"Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+"The Program" refers to any copyrightable work licensed under this
+License. Each licensee is addressed as "you". "Licensees" and
+"recipients" may be individuals or organizations.
+
+To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy. The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.
+
+A "covered work" means either the unmodified Program or a work based
+on the Program.
+
+To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy. Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+
+To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies. Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
+
+An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License. If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+
+1. Source Code.
+
+The "source code" for a work means the preferred form of the work
+for making modifications to it. "Object code" means any non-source
+form of a work.
+
+A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+
+The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form. A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+
+The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities. However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work. For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.
+
+The Corresponding Source for a work in source code form is that
+same work.
+
+2. Basic Permissions.
+
+All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met. This License explicitly affirms your unlimited
+permission to run the unmodified Program. The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work. This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+
+You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force. You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright. Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
+
+Conveying under any other circumstances is permitted solely under
+the conditions stated below. Sublicensing is not allowed; section 10
+makes it unnecessary.
+
+3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+4. Conveying Verbatim Copies.
+
+You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+5. Conveying Modified Source Versions.
+
+You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+ a) The work must carry prominent notices stating that you modified
+ it, and giving a relevant date.
+
+ b) The work must carry prominent notices stating that it is
+ released under this License and any conditions added under section
+ 7. This requirement modifies the requirement in section 4 to
+ "keep intact all notices".
+
+ c) You must license the entire work, as a whole, under this
+ License to anyone who comes into possession of a copy. This
+ License will therefore apply, along with any applicable section 7
+ additional terms, to the whole of the work, and all its parts,
+ regardless of how they are packaged. This License gives no
+ permission to license the work in any other way, but it does not
+ invalidate such permission if you have separately received it.
+
+ d) If the work has interactive user interfaces, each must display
+ Appropriate Legal Notices; however, if the Program has interactive
+ interfaces that do not display Appropriate Legal Notices, your
+ work need not make them do so.
+
+A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit. Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+6. Conveying Non-Source Forms.
+
+You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+ a) Convey the object code in, or embodied in, a physical product
+ (including a physical distribution medium), accompanied by the
+ Corresponding Source fixed on a durable physical medium
+ customarily used for software interchange.
+
+ b) Convey the object code in, or embodied in, a physical product
+ (including a physical distribution medium), accompanied by a
+ written offer, valid for at least three years and valid for as
+ long as you offer spare parts or customer support for that product
+ model, to give anyone who possesses the object code either (1) a
+ copy of the Corresponding Source for all the software in the
+ product that is covered by this License, on a durable physical
+ medium customarily used for software interchange, for a price no
+ more than your reasonable cost of physically performing this
+ conveying of source, or (2) access to copy the
+ Corresponding Source from a network server at no charge.
+
+ c) Convey individual copies of the object code with a copy of the
+ written offer to provide the Corresponding Source. This
+ alternative is allowed only occasionally and noncommercially, and
+ only if you received the object code with such an offer, in accord
+ with subsection 6b.
+
+ d) Convey the object code by offering access from a designated
+ place (gratis or for a charge), and offer equivalent access to the
+ Corresponding Source in the same way through the same place at no
+ further charge. You need not require recipients to copy the
+ Corresponding Source along with the object code. If the place to
+ copy the object code is a network server, the Corresponding Source
+ may be on a different server (operated by you or a third party)
+ that supports equivalent copying facilities, provided you maintain
+ clear directions next to the object code saying where to find the
+ Corresponding Source. Regardless of what server hosts the
+ Corresponding Source, you remain obligated to ensure that it is
+ available for as long as needed to satisfy these requirements.
+
+ e) Convey the object code using peer-to-peer transmission, provided
+ you inform other peers where the object code and Corresponding
+ Source of the work are being offered to the general public at no
+ charge under subsection 6d.
+
+A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling. In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage. For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product. A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+"Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source. The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information. But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed. Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+7. Additional Terms.
+
+"Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law. If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it. (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.) You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+ a) Disclaiming warranty or limiting liability differently from the
+ terms of sections 15 and 16 of this License; or
+
+ b) Requiring preservation of specified reasonable legal notices or
+ author attributions in that material or in the Appropriate Legal
+ Notices displayed by works containing it; or
+
+ c) Prohibiting misrepresentation of the origin of that material, or
+ requiring that modified versions of such material be marked in
+ reasonable ways as different from the original version; or
+
+ d) Limiting the use for publicity purposes of names of licensors or
+ authors of the material; or
+
+ e) Declining to grant rights under trademark law for use of some
+ trade names, trademarks, or service marks; or
+
+ f) Requiring indemnification of licensors and authors of that
+ material by anyone who conveys the material (or modified versions of
+ it) with contractual assumptions of liability to the recipient, for
+ any liability that these contractual assumptions directly impose on
+ those licensors and authors.
+
+All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10. If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term. If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+8. Termination.
+
+You may not propagate or modify a covered work except as expressly
+provided under this License. Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated (a)
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and (b) permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License. If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+9. Acceptance Not Required for Having Copies.
+
+You are not required to accept this License in order to receive or
+run a copy of the Program. Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance. However,
+nothing other than this License grants you permission to propagate or
+modify any covered work. These actions infringe copyright if you do
+not accept this License. Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+10. Automatic Licensing of Downstream Recipients.
+
+Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License. You are not responsible
+for enforcing compliance by third parties with this License.
+
+An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations. If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License. For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+11. Patents.
+
+A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based. The
+work thus licensed is called the contributor's "contributor version".
+
+A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version. For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement). To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients. "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License. You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+12. No Surrender of Others' Freedom.
+
+If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all. For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
+
+13. Remote Network Interaction; Use with the GNU General Public License.
+
+Notwithstanding any other provision of this License, if you modify the
+Program, your modified version must prominently offer all users
+interacting with it remotely through a computer network (if your version
+supports such interaction) an opportunity to receive the Corresponding
+Source of your version by providing access to the Corresponding Source
+from a network server at no charge, through some standard or customary
+means of facilitating copying of software. This Corresponding Source
+shall include the Corresponding Source for any work covered by version 3
+of the GNU General Public License that is incorporated pursuant to the
+following paragraph.
+
+Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU General Public License into a single
+combined work, and to convey the resulting work. The terms of this
+License will continue to apply to the part which is the covered work,
+but the work with which it is combined will remain governed by version
+3 of the GNU General Public License.
+
+14. Revised Versions of this License.
+
+The Free Software Foundation may publish revised and/or new versions of
+the GNU Affero General Public License from time to time. Such new versions
+will be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number. If the
+Program specifies that a certain numbered version of the GNU Affero General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation. If the Program does not specify a version number of the
+GNU Affero General Public License, you may choose any version ever published
+by the Free Software Foundation.
+
+If the Program specifies that a proxy can decide which future
+versions of the GNU Affero General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+Later license versions may give you additional or different
+permissions. However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+15. Disclaimer of Warranty.
+
+THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+16. Limitation of Liability.
+
+IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+17. Interpretation of Sections 15 and 16.
+
+If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+ END OF TERMS AND CONDITIONS
+
+ How to Apply These Terms to Your New Programs
+
+If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+To do so, attach the following notices to the program. It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+
+ Copyright (C)
+
+ This program is free software: you can redistribute it and/or modify
+ it under the terms of the GNU Affero General Public License as published
+ by the Free Software Foundation, either version 3 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU Affero General Public License for more details.
+
+ You should have received a copy of the GNU Affero General Public License
+ along with this program. If not, see .
+
+Also add information on how to contact you by electronic and paper mail.
+
+If your software can interact with users remotely through a computer
+network, you should also make sure that it provides a way for users to
+get its source. For example, if your program is a web application, its
+interface could display a "Source" link that leads users to an archive
+of the code. There are many ways you could offer source, and different
+solutions will be better for different programs; see section 13 for the
+specific requirements.
+
+You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary.
+For more information on this, and how to apply and follow the GNU AGPL, see
+.
diff --git a/README.md b/README.md
new file mode 100644
index 0000000..69cbb59
--- /dev/null
+++ b/README.md
@@ -0,0 +1,124 @@
+
+
+
+
+ );
+ } catch (error) {
+ return (
+
+
+
+ );
+ }
+}
diff --git a/apps/www/src/app/(dashboard)/dashboard/analytics/page.tsx b/apps/www/src/app/(dashboard)/dashboard/analytics/page.tsx
new file mode 100644
index 0000000..f3589ed
--- /dev/null
+++ b/apps/www/src/app/(dashboard)/dashboard/analytics/page.tsx
@@ -0,0 +1,60 @@
+import { redirect } from "next/navigation";
+import { getAnalyticsStats } from "@/actions/stats/get-analytics-stats";
+import { getUserStats } from "@/actions/stats/get-users-stats";
+
+import { authOptions } from "@/lib/auth";
+import { getCurrentUser } from "@/lib/session";
+import CardSection from "@/components/analytics/CardSection";
+import EventsTrendOverTimeChart from "@/components/dashboard/charts/EventsTrendOverTime";
+import UserGrowthTrend from "@/components/dashboard/charts/UserGrowthChart";
+import { DashboardHeader } from "@/components/dashboard/header";
+import { DashboardShell } from "@/components/dashboard/shell";
+import { EmptyPlaceholder } from "@/components/shared/empty-placeholder";
+
+export const metadata = {
+ title: "Dingify Analytics - Your Alerts Overview",
+ description:
+ "Monitor and analyze all your critical events in real-time. Access key metrics, track important journeys, and make data-driven decisions to optimize your business performance on the Dingify Dashboard.",
+};
+
+export default async function DashboardPage() {
+ const user = await getCurrentUser();
+
+ if (!user) {
+ redirect(authOptions.pages?.signIn || "/login");
+ }
+
+ //TODO Make these calls dynamic
+ // const { monthlyEvents, eventTypeBreakdown } = await getAnalyticsStats();
+ // const { totalUsers, usersToday, usersThisWeek, usersThisMonth } =
+ // await getUserStats();
+ // console.log(
+ // "monthlyEvents",
+ // totalUsers,
+ // usersToday,
+ // usersThisWeek,
+ // usersThisMonth,
+ // );
+
+ return (
+
+
+
+
+
+
+
+
+ );
+}
diff --git a/apps/www/src/app/(dashboard)/dashboard/billing/loading.tsx b/apps/www/src/app/(dashboard)/dashboard/billing/loading.tsx
new file mode 100644
index 0000000..fe447d4
--- /dev/null
+++ b/apps/www/src/app/(dashboard)/dashboard/billing/loading.tsx
@@ -0,0 +1,17 @@
+import { DashboardHeader } from "@/components/dashboard/header";
+import { DashboardShell } from "@/components/dashboard/shell";
+import { CardSkeleton } from "@/components/shared/card-skeleton";
+
+export default function DashboardBillingLoading() {
+ return (
+
+
+
+
+
+
+ );
+}
diff --git a/apps/www/src/app/(dashboard)/dashboard/billing/page.tsx b/apps/www/src/app/(dashboard)/dashboard/billing/page.tsx
new file mode 100644
index 0000000..852aa16
--- /dev/null
+++ b/apps/www/src/app/(dashboard)/dashboard/billing/page.tsx
@@ -0,0 +1,61 @@
+import { redirect } from "next/navigation";
+import { BillingInfo } from "@/components/billing-info";
+import { LanugageButton } from "@/components/buttons/LanguageButton";
+import { DashboardHeader } from "@/components/dashboard/header";
+import { DashboardShell } from "@/components/dashboard/shell";
+import { Icons } from "@/components/shared/icons";
+import { authOptions } from "@/lib/auth";
+import { getCurrentUser } from "@/lib/session";
+import { getUserSubscriptionPlan } from "@/lib/subscription";
+
+import {
+ Alert,
+ AlertDescription,
+ AlertTitle,
+} from "@dingify/ui/components/alert";
+
+export const metadata = {
+ title: "Dingity Billing - Subscription Management",
+ description:
+ "Access and manage your billing information, view subscription plans, and update payment methods on Dingity's Billing page.",
+};
+
+export default async function BillingPage() {
+ const user = await getCurrentUser();
+
+ if (!user) {
+ redirect(authOptions.pages?.signIn || "/login");
+ }
+
+ const subscriptionPlan = await getUserSubscriptionPlan(user.id);
+
+ return (
+
+
+
+ {/*
+
+ This is a demo app.
+
+ Propwrite app is a demo app using a Stripe test environment. You can
+ find a list of test card numbers on the{" "}
+
+ Stripe docs
+
+ .
+
+ */}
+
+
+ );
+}
diff --git a/apps/www/src/app/(dashboard)/dashboard/layout.tsx b/apps/www/src/app/(dashboard)/dashboard/layout.tsx
new file mode 100644
index 0000000..d9059ad
--- /dev/null
+++ b/apps/www/src/app/(dashboard)/dashboard/layout.tsx
@@ -0,0 +1,48 @@
+import { notFound } from "next/navigation";
+import { getUserChannels } from "@/actions/get-channels";
+
+import { dashboardConfig } from "@/config/dashboard";
+import { getCurrentUser } from "@/lib/session";
+import { DashboardNav } from "@/components/layout/nav";
+import { NavBar } from "@/components/layout/navbar";
+import { SiteFooter } from "@/components/layout/site-footer";
+
+interface DashboardLayoutProps {
+ children?: React.ReactNode;
+}
+
+export default async function DashboardLayout({
+ children,
+}: DashboardLayoutProps) {
+ const user = await getCurrentUser();
+
+ if (!user) {
+ return notFound();
+ }
+
+ const userChannels = await getUserChannels();
+
+ const sidebarNavItems = [
+ ...dashboardConfig.sidebarNav,
+ ...userChannels.map((channel) => ({
+ title: channel.name,
+ href: `/dashboard/channels/${channel.id}`, // Use ID instead of name
+ })),
+ ];
+
+ return (
+
+
+
+
+
+
+ {children}
+
+
+
+
+ );
+}
diff --git a/apps/www/src/app/(dashboard)/dashboard/loading.tsx b/apps/www/src/app/(dashboard)/dashboard/loading.tsx
new file mode 100644
index 0000000..ea4980b
--- /dev/null
+++ b/apps/www/src/app/(dashboard)/dashboard/loading.tsx
@@ -0,0 +1,21 @@
+import { Button } from "@dingify/ui/components/button";
+
+import { DashboardHeader } from "@/components/dashboard/header";
+import { DashboardShell } from "@/components/dashboard/shell";
+import { CardSkeleton } from "@/components/shared/card-skeleton";
+
+export default function DashboardLoading() {
+ return (
+
+
+
+
+
+
+
+
+
+
+
+ );
+}
diff --git a/apps/www/src/app/(dashboard)/dashboard/notifications/loading.tsx b/apps/www/src/app/(dashboard)/dashboard/notifications/loading.tsx
new file mode 100644
index 0000000..bbf8d7b
--- /dev/null
+++ b/apps/www/src/app/(dashboard)/dashboard/notifications/loading.tsx
@@ -0,0 +1,17 @@
+import { DashboardHeader } from "@/components/dashboard/header";
+import { DashboardShell } from "@/components/dashboard/shell";
+import { CardSkeleton } from "@/components/shared/card-skeleton";
+
+export default function DashboardSettingsLoading() {
+ return (
+
+
+
+
+
+
+ );
+}
diff --git a/apps/www/src/app/(dashboard)/dashboard/notifications/page.tsx b/apps/www/src/app/(dashboard)/dashboard/notifications/page.tsx
new file mode 100644
index 0000000..35032f7
--- /dev/null
+++ b/apps/www/src/app/(dashboard)/dashboard/notifications/page.tsx
@@ -0,0 +1,47 @@
+import { redirect } from "next/navigation";
+import { getMetricsForUser } from "@/actions/get-metrics-user";
+import { getNotificationSettings } from "@/actions/get-notification-settings";
+
+import {
+ Card,
+ CardContent,
+ CardDescription,
+ CardFooter,
+ CardHeader,
+ CardTitle,
+} from "@dingify/ui/components/card";
+
+import { authOptions } from "@/lib/auth";
+import { getCurrentUser } from "@/lib/session";
+import { DashboardHeader } from "@/components/dashboard/header";
+import { DashboardShell } from "@/components/dashboard/shell";
+import { LanguageForm2 } from "@/components/forms/language-form2";
+import { UserNameForm } from "@/components/forms/user-name-form";
+import { NotificationAlert } from "@/components/notifications/NotificationAlert";
+
+export const metadata = {
+ title: "Dingify Notifications - Customize Your Alerts",
+ description:
+ "Adjust your Dingify notification settings for a personalized real-time monitoring experience. Manage alert preferences, notification channels, and more.",
+};
+
+export default async function SettingsPage() {
+ const user = await getCurrentUser();
+
+ if (!user) {
+ redirect(authOptions.pages?.signIn || "/login");
+ }
+ // How to get the metrics for the user
+ const metrics = await getMetricsForUser();
+ const settings = await getNotificationSettings();
+
+ return (
+
+
+
+
+ );
+}
diff --git a/apps/www/src/app/(dashboard)/dashboard/page.tsx b/apps/www/src/app/(dashboard)/dashboard/page.tsx
new file mode 100644
index 0000000..6e4d558
--- /dev/null
+++ b/apps/www/src/app/(dashboard)/dashboard/page.tsx
@@ -0,0 +1,144 @@
+import { redirect } from "next/navigation";
+import { getUserCredits } from "@/actions/get-credits";
+import { getEventStats } from "@/actions/stats/get-events-stats";
+
+import { authOptions } from "@/lib/auth";
+import { prisma } from "@/lib/db";
+import { getCurrentUser } from "@/lib/session";
+import { AddApiKeyButton } from "@/components/buttons/AddApiKeyButton";
+import { AddChannelButton } from "@/components/buttons/AddChannelButton";
+import { AddProjectButton } from "@/components/buttons/AddProjectButton";
+import { AddPropertyButton } from "@/components/buttons/AddPropertyButton";
+import EventsDashboard from "@/components/dashboard/EventsDashboard";
+import { DashboardHeader } from "@/components/dashboard/header";
+import { DashboardShell } from "@/components/dashboard/shell";
+import { EmptyPlaceholder } from "@/components/shared/empty-placeholder";
+
+export const metadata = {
+ title: "Dingify Dashboard - Your Alerts Overview",
+ description:
+ "Monitor and analyze all your critical events in real-time. Access key metrics, track important journeys, and make data-driven decisions to optimize your business performance on the Dingify Dashboard.",
+};
+
+export default async function DashboardPage() {
+ const user = await getCurrentUser();
+ const userCredits = await getUserCredits();
+ const eventStats = await getEventStats();
+
+ if (!user) {
+ redirect(authOptions.pages?.signIn || "/login");
+ }
+
+ // Fetch projects associated with the user
+ const projects = await prisma.project.findMany({
+ where: {
+ userId: user.id,
+ },
+ select: {
+ id: true,
+ },
+ });
+
+ // Extract project IDs
+ const projectIds = projects.map((project) => project.id);
+
+ // Fetch customers associated with the user's projects
+ const customers = await prisma.customer.findMany({
+ where: {
+ projectId: {
+ in: projectIds,
+ },
+ },
+ });
+ console.log(customers);
+
+ // Fetch channels for the user's projects
+ const channels = await prisma.channel.findMany({
+ where: {
+ projectId: {
+ in: projectIds,
+ },
+ },
+ select: {
+ id: true,
+ name: true,
+ createdAt: true,
+ },
+ orderBy: {
+ createdAt: "desc",
+ },
+ });
+
+ // Extract channel IDs
+ const channelIds = channels.map((channel) => channel.id);
+
+ // Fetch events for the user's channels with project and channel names
+ const events = await prisma.event.findMany({
+ where: {
+ channelId: {
+ in: channelIds,
+ },
+ },
+ select: {
+ id: true,
+ name: true,
+ channelId: true,
+ userId: true,
+ icon: true,
+ tags: true,
+ notify: true,
+ createdAt: true,
+ customerId: true,
+ channel: {
+ select: {
+ name: true,
+ project: {
+ select: {
+ name: true,
+ },
+ },
+ },
+ },
+ },
+ orderBy: {
+ createdAt: "desc",
+ },
+ });
+
+ // Ensure userCredits.credits is defined, default to 0 if undefined
+ const availableCredits = userCredits.credits ?? 0;
+
+ return (
+
+
+ {userCredits.success && availableCredits > 0 ? (
+
+ ) : (
+ //
+ //
+
+ )}
+
+
+ {channels.length === 0 ? (
+ // Render EmptyPlaceholder if there are no channels
+
+
+
+ There are no channels
+
+
+ You need to generate an API key first
+
+
+
+ ) : (
+ // Render EventsTable if there are Events
+
+ )}
+
+
+ );
+}
diff --git a/apps/www/src/app/(dashboard)/dashboard/settings/loading.tsx b/apps/www/src/app/(dashboard)/dashboard/settings/loading.tsx
new file mode 100644
index 0000000..6f431b2
--- /dev/null
+++ b/apps/www/src/app/(dashboard)/dashboard/settings/loading.tsx
@@ -0,0 +1,17 @@
+import { DashboardHeader } from "@/components/dashboard/header";
+import { DashboardShell } from "@/components/dashboard/shell";
+import { CardSkeleton } from "@/components/shared/card-skeleton";
+
+export default function DashboardSettingsLoading() {
+ return (
+
+
+
+
+
+
+ );
+}
diff --git a/apps/www/src/app/(dashboard)/dashboard/settings/page.tsx b/apps/www/src/app/(dashboard)/dashboard/settings/page.tsx
new file mode 100644
index 0000000..2c7eb85
--- /dev/null
+++ b/apps/www/src/app/(dashboard)/dashboard/settings/page.tsx
@@ -0,0 +1,153 @@
+import { redirect } from "next/navigation";
+import { getMetricsForUser } from "@/actions/get-metrics-user";
+
+import {
+ Card,
+ CardContent,
+ CardDescription,
+ CardFooter,
+ CardHeader,
+ CardTitle,
+} from "@dingify/ui/components/card";
+
+import { authOptions } from "@/lib/auth";
+import { getCurrentUser } from "@/lib/session";
+import { DashboardHeader } from "@/components/dashboard/header";
+import { DashboardShell } from "@/components/dashboard/shell";
+import { LanguageForm2 } from "@/components/forms/language-form2";
+import { UserNameForm } from "@/components/forms/user-name-form";
+
+export const metadata = {
+ title: "Dingify Settings - Customize Your Experience",
+ description:
+ "Adjust your Dingify account settings for a personalized real-time monitoring experience. Manage language preferences, account details, and more.",
+};
+
+export default async function SettingsPage() {
+ const user = await getCurrentUser();
+
+ if (!user) {
+ redirect(authOptions.pages?.signIn || "/login");
+ }
+
+ const metrics = await getMetricsForUser();
+
+ const formatNumber = (number) => {
+ return new Intl.NumberFormat("en-US").format(number);
+ };
+
+ return (
+
+
+
+
+
+
+ Logs
+
+ {metrics
+ ? `${formatNumber(metrics.logsUsed)} / ${formatNumber(metrics.logsLimit)}`
+ : "N/A"}
+
+
+
+
+ Total logs for this month
+
+
+
+
+ Seats
+
+ {metrics ? `${formatNumber(metrics.seatsUsed)} / 1` : "N/A"}
+
+
+
+
+ Seats used in your plan
+
+
+
+
+ Projects
+
+ {metrics ? `${formatNumber(metrics.projectsUsed)} / โ` : "N/A"}
+
+
+
+
+ Total projects in your account
+
+
+
+ {subscriptionPlan.isCanceled
+ ? "Your plan will be canceled on "
+ : "Your plan renews on "}
+ {formatDate(subscriptionPlan.stripeCurrentPeriodEnd)}.
+
+ ) : null}
+
+
+ );
+}
diff --git a/apps/www/src/components/blog-posts.tsx b/apps/www/src/components/blog-posts.tsx
new file mode 100644
index 0000000..3e8246b
--- /dev/null
+++ b/apps/www/src/components/blog-posts.tsx
@@ -0,0 +1,78 @@
+import Image from "next/image";
+import Link from "next/link";
+import { formatDate } from "@/lib/utils";
+import Balancer from "react-wrap-balancer";
+
+export function BlogPosts({ posts }) {
+ return (
+
+ );
+}
diff --git a/apps/www/src/components/content/templete-blog/deploying-next-apps.mdx b/apps/www/src/components/content/templete-blog/deploying-next-apps.mdx
new file mode 100644
index 0000000..2599430
--- /dev/null
+++ b/apps/www/src/components/content/templete-blog/deploying-next-apps.mdx
@@ -0,0 +1,219 @@
+---
+title: Deploying Next.js Apps
+description: How to deploy your Next.js apps on Vercel.
+image: /images/blog/blog-post-3.jpg
+date: "2023-01-02"
+authors:
+ - shadcn
+---
+
+
+ The text below is from the [Tailwind
+ CSS](https://play.tailwindcss.com/uj1vGACRJA?layout=preview) docs. I copied it
+ here to test the markdown styles. **Tailwind is awesome. You should use it.**
+
+
+Until now, trying to style an article, document, or blog post with Tailwind has been a tedious task that required a keen eye for typography and a lot of complex custom CSS.
+
+By default, Tailwind removes all of the default browser styling from paragraphs, headings, lists and more. This ends up being really useful for building application UIs because you spend less time undoing user-agent styles, but when you _really are_ just trying to style some content that came from a rich-text editor in a CMS or a markdown file, it can be surprising and unintuitive.
+
+We get lots of complaints about it actually, with people regularly asking us things like:
+
+> Why is Tailwind removing the default styles on my `h1` elements? How do I disable this? What do you mean I lose all the other base styles too?
+> We hear you, but we're not convinced that simply disabling our base styles is what you really want. You don't want to have to remove annoying margins every time you use a `p` element in a piece of your dashboard UI. And I doubt you really want your blog posts to use the user-agent styles either โ you want them to look _awesome_, not awful.
+
+The `@tailwindcss/typography` plugin is our attempt to give you what you _actually_ want, without any of the downsides of doing something stupid like disabling our base styles.
+
+It adds a new `prose` class that you can slap on any block of vanilla HTML content and turn it into a beautiful, well-formatted document:
+
+```html
+
+
Garlic bread with cheese: What the science tells us
+
+ For years parents have espoused the health benefits of eating garlic bread
+ with cheese to their children, with the food earning such an iconic status
+ in our culture that kids will often dress up as warm, cheesy loaf for
+ Halloween.
+
+
+ But a recent study shows that the celebrated appetizer may be linked to a
+ series of rabies cases springing up around the country.
+
+
+```
+
+For more information about how to use the plugin and the features it includes, [read the documentation](https://github.com/tailwindcss/typography/blob/master/README.md).
+
+---
+
+## What to expect from here on out
+
+What follows from here is just a bunch of absolute nonsense I've written to dogfood the plugin itself. It includes every sensible typographic element I could think of, like **bold text**, unordered lists, ordered lists, code blocks, block quotes, _and even italics_.
+
+It's important to cover all of these use cases for a few reasons:
+
+1. We want everything to look good out of the box.
+2. Really just the first reason, that's the whole point of the plugin.
+3. Here's a third pretend reason though a list with three items looks more realistic than a list with two items.
+
+Now we're going to try out another header style.
+
+### Typography should be easy
+
+So that's a header for you โ with any luck if we've done our job correctly that will look pretty reasonable.
+
+Something a wise person once told me about typography is:
+
+> Typography is pretty important if you don't want your stuff to look like trash. Make it good then it won't be bad.
+
+It's probably important that images look okay here by default as well:
+
+
+
+Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots in a piece of classical Latin literature from 45 BC, making it over 2000 years old.
+
+Now I'm going to show you an example of an unordered list to make sure that looks good, too:
+
+- So here is the first item in this list.
+- In this example we're keeping the items short.
+- Later, we'll use longer, more complex list items.
+
+And that's the end of this section.
+
+## What if we stack headings?
+
+### We should make sure that looks good, too.
+
+Sometimes you have headings directly underneath each other. In those cases you often have to undo the top margin on the second heading because it usually looks better for the headings to be closer together than a paragraph followed by a heading should be.
+
+### When a heading comes after a paragraph โฆ
+
+When a heading comes after a paragraph, we need a bit more space, like I already mentioned above. Now let's see what a more complex list would look like.
+
+- **I often do this thing where list items have headings.**
+
+ For some reason I think this looks cool which is unfortunate because it's pretty annoying to get the styles right.
+
+ I often have two or three paragraphs in these list items, too, so the hard part is getting the spacing between the paragraphs, list item heading, and separate list items to all make sense. Pretty tough honestly, you could make a strong argument that you just shouldn't write this way.
+
+- **Since this is a list, I need at least two items.**
+
+ I explained what I'm doing already in the previous list item, but a list wouldn't be a list if it only had one item, and we really want this to look realistic. That's why I've added this second list item so I actually have something to look at when writing the styles.
+
+- **It's not a bad idea to add a third item either.**
+
+ I think it probably would've been fine to just use two items but three is definitely not worse, and since I seem to be having no trouble making up arbitrary things to type, I might as well include it.
+
+After this sort of list I usually have a closing statement or paragraph, because it kinda looks weird jumping right to a heading.
+
+## Code should look okay by default.
+
+I think most people are going to use [highlight.js](https://highlightjs.org/) or [Prism](https://prismjs.com/) or something if they want to style their code blocks but it wouldn't hurt to make them look _okay_ out of the box, even with no syntax highlighting.
+
+Here's what a default `tailwind.config.js` file looks like at the time of writing:
+
+```js
+module.exports = {
+ purge: [],
+ theme: {
+ extend: {},
+ },
+ variants: {},
+ plugins: [],
+};
+```
+
+Hopefully that looks good enough to you.
+
+### What about nested lists?
+
+Nested lists basically always look bad which is why editors like Medium don't even let you do it, but I guess since some of you goofballs are going to do it we have to carry the burden of at least making it work.
+
+1. **Nested lists are rarely a good idea.**
+ - You might feel like you are being really "organized" or something but you are just creating a gross shape on the screen that is hard to read.
+ - Nested navigation in UIs is a bad idea too, keep things as flat as possible.
+ - Nesting tons of folders in your source code is also not helpful.
+2. **Since we need to have more items, here's another one.**
+ - I'm not sure if we'll bother styling more than two levels deep.
+ - Two is already too much, three is guaranteed to be a bad idea.
+ - If you nest four levels deep you belong in prison.
+3. **Two items isn't really a list, three is good though.**
+ - Again please don't nest lists if you want people to actually read your content.
+ - Nobody wants to look at this.
+ - I'm upset that we even have to bother styling this.
+
+The most annoying thing about lists in Markdown is that `
` elements aren't given a child `
` tag unless there are multiple paragraphs in the list item. That means I have to worry about styling that annoying situation too.
+
+- **For example, here's another nested list.**
+
+ But this time with a second paragraph.
+
+ - These list items won't have `
` tags
+ - Because they are only one line each
+
+- **But in this second top-level list item, they will.**
+
+ This is especially annoying because of the spacing on this paragraph.
+
+ - As you can see here, because I've added a second line, this list item now has a `
` tag.
+
+ This is the second line I'm talking about by the way.
+
+ - Finally here's another list item so it's more like a list.
+
+- A closing list item, but with no nested list, because why not?
+
+And finally a sentence to close off this section.
+
+## There are other elements we need to style
+
+I almost forgot to mention links, like [this link to the Tailwind CSS website](https://tailwindcss.com). We almost made them blue but that's so yesterday, so we went with dark gray, feels edgier.
+
+We even included table styles, check it out:
+
+| Wrestler | Origin | Finisher |
+| ----------------------- | ------------ | ------------------ |
+| Bret "The Hitman" Hart | Calgary, AB | Sharpshooter |
+| Stone Cold Steve Austin | Austin, TX | Stone Cold Stunner |
+| Randy Savage | Sarasota, FL | Elbow Drop |
+| Vader | Boulder, CO | Vader Bomb |
+| Razor Ramon | Chuluota, FL | Razor's Edge |
+
+We also need to make sure inline code looks good, like if I wanted to talk about `` elements or tell you the good news about `@tailwindcss/typography`.
+
+### Sometimes I even use `code` in headings
+
+Even though it's probably a bad idea, and historically I've had a hard time making it look good. This _"wrap the code blocks in backticks"_ trick works pretty well though really.
+
+Another thing I've done in the past is put a `code` tag inside of a link, like if I wanted to tell you about the [`tailwindcss/docs`](https://github.com/tailwindcss/docs) repository. I don't love that there is an underline below the backticks but it is absolutely not worth the madness it would require to avoid it.
+
+#### We haven't used an `h4` yet
+
+But now we have. Please don't use `h5` or `h6` in your content, Medium only supports two heading levels for a reason, you animals. I honestly considered using a `before` pseudo-element to scream at you if you use an `h5` or `h6`.
+
+We don't style them at all out of the box because `h4` elements are already so small that they are the same size as the body copy. What are we supposed to do with an `h5`, make it _smaller_ than the body copy? No thanks.
+
+### We still need to think about stacked headings though.
+
+#### Let's make sure we don't screw that up with `h4` elements, either.
+
+Phew, with any luck we have styled the headings above this text and they look pretty good.
+
+Let's add a closing paragraph here so things end with a decently sized block of text. I can't explain why I want things to end that way but I have to assume it's because I think things will look weird or unbalanced if there is a heading too close to the end of the document.
+
+What I've written here is probably long enough, but adding this final sentence can't hurt.
+
+## GitHub Flavored Markdown
+
+I've also added support for GitHub Flavored Mardown using `remark-gfm`.
+
+With `remark-gfm`, we get a few extra features in our markdown. Example: autolink literals.
+
+A link like www.example.com or https://example.com would automatically be converted into an `a` tag.
+
+This works for email links too: contact@example.com.
diff --git a/apps/www/src/components/content/templete-blog/dynamic-routing-static-regeneration copy.mdx b/apps/www/src/components/content/templete-blog/dynamic-routing-static-regeneration copy.mdx
new file mode 100644
index 0000000..5a0ac70
--- /dev/null
+++ b/apps/www/src/components/content/templete-blog/dynamic-routing-static-regeneration copy.mdx
@@ -0,0 +1,219 @@
+---
+title: Dynamic Routing and Static Regeneration
+description: How to use incremental static regeneration using dynamic routes.
+image: /images/blog/blog-post-2.jpg
+date: "2023-03-04"
+authors:
+ - codehagen
+---
+
+
+ The text below is from the [Tailwind
+ CSS](https://play.tailwindcss.com/uj1vGACRJA?layout=preview) docs. I copied it
+ here to test the markdown styles. **Tailwind is awesome. You should use it.**
+
+
+Until now, trying to style an article, document, or blog post with Tailwind has been a tedious task that required a keen eye for typography and a lot of complex custom CSS.
+
+By default, Tailwind removes all of the default browser styling from paragraphs, headings, lists and more. This ends up being really useful for building application UIs because you spend less time undoing user-agent styles, but when you _really are_ just trying to style some content that came from a rich-text editor in a CMS or a markdown file, it can be surprising and unintuitive.
+
+We get lots of complaints about it actually, with people regularly asking us things like:
+
+> Why is Tailwind removing the default styles on my `h1` elements? How do I disable this? What do you mean I lose all the other base styles too?
+> We hear you, but we're not convinced that simply disabling our base styles is what you really want. You don't want to have to remove annoying margins every time you use a `p` element in a piece of your dashboard UI. And I doubt you really want your blog posts to use the user-agent styles either โ you want them to look _awesome_, not awful.
+
+The `@tailwindcss/typography` plugin is our attempt to give you what you _actually_ want, without any of the downsides of doing something stupid like disabling our base styles.
+
+It adds a new `prose` class that you can slap on any block of vanilla HTML content and turn it into a beautiful, well-formatted document:
+
+```html
+
+
Garlic bread with cheese: What the science tells us
+
+ For years parents have espoused the health benefits of eating garlic bread
+ with cheese to their children, with the food earning such an iconic status
+ in our culture that kids will often dress up as warm, cheesy loaf for
+ Halloween.
+
+
+ But a recent study shows that the celebrated appetizer may be linked to a
+ series of rabies cases springing up around the country.
+
+
+```
+
+For more information about how to use the plugin and the features it includes, [read the documentation](https://github.com/tailwindcss/typography/blob/master/README.md).
+
+---
+
+## What to expect from here on out
+
+What follows from here is just a bunch of absolute nonsense I've written to dogfood the plugin itself. It includes every sensible typographic element I could think of, like **bold text**, unordered lists, ordered lists, code blocks, block quotes, _and even italics_.
+
+It's important to cover all of these use cases for a few reasons:
+
+1. We want everything to look good out of the box.
+2. Really just the first reason, that's the whole point of the plugin.
+3. Here's a third pretend reason though a list with three items looks more realistic than a list with two items.
+
+Now we're going to try out another header style.
+
+### Typography should be easy
+
+So that's a header for you โ with any luck if we've done our job correctly that will look pretty reasonable.
+
+Something a wise person once told me about typography is:
+
+> Typography is pretty important if you don't want your stuff to look like trash. Make it good then it won't be bad.
+
+It's probably important that images look okay here by default as well:
+
+
+
+Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots in a piece of classical Latin literature from 45 BC, making it over 2000 years old.
+
+Now I'm going to show you an example of an unordered list to make sure that looks good, too:
+
+- So here is the first item in this list.
+- In this example we're keeping the items short.
+- Later, we'll use longer, more complex list items.
+
+And that's the end of this section.
+
+## What if we stack headings?
+
+### We should make sure that looks good, too.
+
+Sometimes you have headings directly underneath each other. In those cases you often have to undo the top margin on the second heading because it usually looks better for the headings to be closer together than a paragraph followed by a heading should be.
+
+### When a heading comes after a paragraph โฆ
+
+When a heading comes after a paragraph, we need a bit more space, like I already mentioned above. Now let's see what a more complex list would look like.
+
+- **I often do this thing where list items have headings.**
+
+ For some reason I think this looks cool which is unfortunate because it's pretty annoying to get the styles right.
+
+ I often have two or three paragraphs in these list items, too, so the hard part is getting the spacing between the paragraphs, list item heading, and separate list items to all make sense. Pretty tough honestly, you could make a strong argument that you just shouldn't write this way.
+
+- **Since this is a list, I need at least two items.**
+
+ I explained what I'm doing already in the previous list item, but a list wouldn't be a list if it only had one item, and we really want this to look realistic. That's why I've added this second list item so I actually have something to look at when writing the styles.
+
+- **It's not a bad idea to add a third item either.**
+
+ I think it probably would've been fine to just use two items but three is definitely not worse, and since I seem to be having no trouble making up arbitrary things to type, I might as well include it.
+
+After this sort of list I usually have a closing statement or paragraph, because it kinda looks weird jumping right to a heading.
+
+## Code should look okay by default.
+
+I think most people are going to use [highlight.js](https://highlightjs.org/) or [Prism](https://prismjs.com/) or something if they want to style their code blocks but it wouldn't hurt to make them look _okay_ out of the box, even with no syntax highlighting.
+
+Here's what a default `tailwind.config.js` file looks like at the time of writing:
+
+```js
+module.exports = {
+ purge: [],
+ theme: {
+ extend: {},
+ },
+ variants: {},
+ plugins: [],
+};
+```
+
+Hopefully that looks good enough to you.
+
+### What about nested lists?
+
+Nested lists basically always look bad which is why editors like Medium don't even let you do it, but I guess since some of you goofballs are going to do it we have to carry the burden of at least making it work.
+
+1. **Nested lists are rarely a good idea.**
+ - You might feel like you are being really "organized" or something but you are just creating a gross shape on the screen that is hard to read.
+ - Nested navigation in UIs is a bad idea too, keep things as flat as possible.
+ - Nesting tons of folders in your source code is also not helpful.
+2. **Since we need to have more items, here's another one.**
+ - I'm not sure if we'll bother styling more than two levels deep.
+ - Two is already too much, three is guaranteed to be a bad idea.
+ - If you nest four levels deep you belong in prison.
+3. **Two items isn't really a list, three is good though.**
+ - Again please don't nest lists if you want people to actually read your content.
+ - Nobody wants to look at this.
+ - I'm upset that we even have to bother styling this.
+
+The most annoying thing about lists in Markdown is that `
` elements aren't given a child `
` tag unless there are multiple paragraphs in the list item. That means I have to worry about styling that annoying situation too.
+
+- **For example, here's another nested list.**
+
+ But this time with a second paragraph.
+
+ - These list items won't have `
` tags
+ - Because they are only one line each
+
+- **But in this second top-level list item, they will.**
+
+ This is especially annoying because of the spacing on this paragraph.
+
+ - As you can see here, because I've added a second line, this list item now has a `
` tag.
+
+ This is the second line I'm talking about by the way.
+
+ - Finally here's another list item so it's more like a list.
+
+- A closing list item, but with no nested list, because why not?
+
+And finally a sentence to close off this section.
+
+## There are other elements we need to style
+
+I almost forgot to mention links, like [this link to the Tailwind CSS website](https://tailwindcss.com). We almost made them blue but that's so yesterday, so we went with dark gray, feels edgier.
+
+We even included table styles, check it out:
+
+| Wrestler | Origin | Finisher |
+| ----------------------- | ------------ | ------------------ |
+| Bret "The Hitman" Hart | Calgary, AB | Sharpshooter |
+| Stone Cold Steve Austin | Austin, TX | Stone Cold Stunner |
+| Randy Savage | Sarasota, FL | Elbow Drop |
+| Vader | Boulder, CO | Vader Bomb |
+| Razor Ramon | Chuluota, FL | Razor's Edge |
+
+We also need to make sure inline code looks good, like if I wanted to talk about `` elements or tell you the good news about `@tailwindcss/typography`.
+
+### Sometimes I even use `code` in headings
+
+Even though it's probably a bad idea, and historically I've had a hard time making it look good. This _"wrap the code blocks in backticks"_ trick works pretty well though really.
+
+Another thing I've done in the past is put a `code` tag inside of a link, like if I wanted to tell you about the [`tailwindcss/docs`](https://github.com/tailwindcss/docs) repository. I don't love that there is an underline below the backticks but it is absolutely not worth the madness it would require to avoid it.
+
+#### We haven't used an `h4` yet
+
+But now we have. Please don't use `h5` or `h6` in your content, Medium only supports two heading levels for a reason, you animals. I honestly considered using a `before` pseudo-element to scream at you if you use an `h5` or `h6`.
+
+We don't style them at all out of the box because `h4` elements are already so small that they are the same size as the body copy. What are we supposed to do with an `h5`, make it _smaller_ than the body copy? No thanks.
+
+### We still need to think about stacked headings though.
+
+#### Let's make sure we don't screw that up with `h4` elements, either.
+
+Phew, with any luck we have styled the headings above this text and they look pretty good.
+
+Let's add a closing paragraph here so things end with a decently sized block of text. I can't explain why I want things to end that way but I have to assume it's because I think things will look weird or unbalanced if there is a heading too close to the end of the document.
+
+What I've written here is probably long enough, but adding this final sentence can't hurt.
+
+## GitHub Flavored Markdown
+
+I've also added support for GitHub Flavored Mardown using `remark-gfm`.
+
+With `remark-gfm`, we get a few extra features in our markdown. Example: autolink literals.
+
+A link like www.example.com or https://example.com would automatically be converted into an `a` tag.
+
+This works for email links too: contact@example.com.
diff --git a/apps/www/src/components/content/templete-blog/preview-mode-headless-cms.mdx b/apps/www/src/components/content/templete-blog/preview-mode-headless-cms.mdx
new file mode 100644
index 0000000..e90e247
--- /dev/null
+++ b/apps/www/src/components/content/templete-blog/preview-mode-headless-cms.mdx
@@ -0,0 +1,219 @@
+---
+title: Preview Mode for Headless CMS
+description: How to implement preview mode in your headless CMS.
+date: "2023-04-09"
+image: /images/blog/blog-post-1.jpg
+authors:
+ - shadcn
+---
+
+
+ The text below is from the [Tailwind
+ CSS](https://play.tailwindcss.com/uj1vGACRJA?layout=preview) docs. I copied it
+ here to test the markdown styles. **Tailwind is awesome. You should use it.**
+
+
+Until now, trying to style an article, document, or blog post with Tailwind has been a tedious task that required a keen eye for typography and a lot of complex custom CSS.
+
+By default, Tailwind removes all of the default browser styling from paragraphs, headings, lists and more. This ends up being really useful for building application UIs because you spend less time undoing user-agent styles, but when you _really are_ just trying to style some content that came from a rich-text editor in a CMS or a markdown file, it can be surprising and unintuitive.
+
+We get lots of complaints about it actually, with people regularly asking us things like:
+
+> Why is Tailwind removing the default styles on my `h1` elements? How do I disable this? What do you mean I lose all the other base styles too?
+> We hear you, but we're not convinced that simply disabling our base styles is what you really want. You don't want to have to remove annoying margins every time you use a `p` element in a piece of your dashboard UI. And I doubt you really want your blog posts to use the user-agent styles either โ you want them to look _awesome_, not awful.
+
+The `@tailwindcss/typography` plugin is our attempt to give you what you _actually_ want, without any of the downsides of doing something stupid like disabling our base styles.
+
+It adds a new `prose` class that you can slap on any block of vanilla HTML content and turn it into a beautiful, well-formatted document:
+
+```html
+
+
Garlic bread with cheese: What the science tells us
+
+ For years parents have espoused the health benefits of eating garlic bread
+ with cheese to their children, with the food earning such an iconic status
+ in our culture that kids will often dress up as warm, cheesy loaf for
+ Halloween.
+
+
+ But a recent study shows that the celebrated appetizer may be linked to a
+ series of rabies cases springing up around the country.
+
+
+```
+
+For more information about how to use the plugin and the features it includes, [read the documentation](https://github.com/tailwindcss/typography/blob/master/README.md).
+
+---
+
+## What to expect from here on out
+
+What follows from here is just a bunch of absolute nonsense I've written to dogfood the plugin itself. It includes every sensible typographic element I could think of, like **bold text**, unordered lists, ordered lists, code blocks, block quotes, _and even italics_.
+
+It's important to cover all of these use cases for a few reasons:
+
+1. We want everything to look good out of the box.
+2. Really just the first reason, that's the whole point of the plugin.
+3. Here's a third pretend reason though a list with three items looks more realistic than a list with two items.
+
+Now we're going to try out another header style.
+
+### Typography should be easy
+
+So that's a header for you โ with any luck if we've done our job correctly that will look pretty reasonable.
+
+Something a wise person once told me about typography is:
+
+> Typography is pretty important if you don't want your stuff to look like trash. Make it good then it won't be bad.
+
+It's probably important that images look okay here by default as well:
+
+
+
+Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots in a piece of classical Latin literature from 45 BC, making it over 2000 years old.
+
+Now I'm going to show you an example of an unordered list to make sure that looks good, too:
+
+- So here is the first item in this list.
+- In this example we're keeping the items short.
+- Later, we'll use longer, more complex list items.
+
+And that's the end of this section.
+
+## What if we stack headings?
+
+### We should make sure that looks good, too.
+
+Sometimes you have headings directly underneath each other. In those cases you often have to undo the top margin on the second heading because it usually looks better for the headings to be closer together than a paragraph followed by a heading should be.
+
+### When a heading comes after a paragraph โฆ
+
+When a heading comes after a paragraph, we need a bit more space, like I already mentioned above. Now let's see what a more complex list would look like.
+
+- **I often do this thing where list items have headings.**
+
+ For some reason I think this looks cool which is unfortunate because it's pretty annoying to get the styles right.
+
+ I often have two or three paragraphs in these list items, too, so the hard part is getting the spacing between the paragraphs, list item heading, and separate list items to all make sense. Pretty tough honestly, you could make a strong argument that you just shouldn't write this way.
+
+- **Since this is a list, I need at least two items.**
+
+ I explained what I'm doing already in the previous list item, but a list wouldn't be a list if it only had one item, and we really want this to look realistic. That's why I've added this second list item so I actually have something to look at when writing the styles.
+
+- **It's not a bad idea to add a third item either.**
+
+ I think it probably would've been fine to just use two items but three is definitely not worse, and since I seem to be having no trouble making up arbitrary things to type, I might as well include it.
+
+After this sort of list I usually have a closing statement or paragraph, because it kinda looks weird jumping right to a heading.
+
+## Code should look okay by default.
+
+I think most people are going to use [highlight.js](https://highlightjs.org/) or [Prism](https://prismjs.com/) or something if they want to style their code blocks but it wouldn't hurt to make them look _okay_ out of the box, even with no syntax highlighting.
+
+Here's what a default `tailwind.config.js` file looks like at the time of writing:
+
+```js
+module.exports = {
+ purge: [],
+ theme: {
+ extend: {},
+ },
+ variants: {},
+ plugins: [],
+};
+```
+
+Hopefully that looks good enough to you.
+
+### What about nested lists?
+
+Nested lists basically always look bad which is why editors like Medium don't even let you do it, but I guess since some of you goofballs are going to do it we have to carry the burden of at least making it work.
+
+1. **Nested lists are rarely a good idea.**
+ - You might feel like you are being really "organized" or something but you are just creating a gross shape on the screen that is hard to read.
+ - Nested navigation in UIs is a bad idea too, keep things as flat as possible.
+ - Nesting tons of folders in your source code is also not helpful.
+2. **Since we need to have more items, here's another one.**
+ - I'm not sure if we'll bother styling more than two levels deep.
+ - Two is already too much, three is guaranteed to be a bad idea.
+ - If you nest four levels deep you belong in prison.
+3. **Two items isn't really a list, three is good though.**
+ - Again please don't nest lists if you want people to actually read your content.
+ - Nobody wants to look at this.
+ - I'm upset that we even have to bother styling this.
+
+The most annoying thing about lists in Markdown is that `
` elements aren't given a child `
` tag unless there are multiple paragraphs in the list item. That means I have to worry about styling that annoying situation too.
+
+- **For example, here's another nested list.**
+
+ But this time with a second paragraph.
+
+ - These list items won't have `
` tags
+ - Because they are only one line each
+
+- **But in this second top-level list item, they will.**
+
+ This is especially annoying because of the spacing on this paragraph.
+
+ - As you can see here, because I've added a second line, this list item now has a `
` tag.
+
+ This is the second line I'm talking about by the way.
+
+ - Finally here's another list item so it's more like a list.
+
+- A closing list item, but with no nested list, because why not?
+
+And finally a sentence to close off this section.
+
+## There are other elements we need to style
+
+I almost forgot to mention links, like [this link to the Tailwind CSS website](https://tailwindcss.com). We almost made them blue but that's so yesterday, so we went with dark gray, feels edgier.
+
+We even included table styles, check it out:
+
+| Wrestler | Origin | Finisher |
+| ----------------------- | ------------ | ------------------ |
+| Bret "The Hitman" Hart | Calgary, AB | Sharpshooter |
+| Stone Cold Steve Austin | Austin, TX | Stone Cold Stunner |
+| Randy Savage | Sarasota, FL | Elbow Drop |
+| Vader | Boulder, CO | Vader Bomb |
+| Razor Ramon | Chuluota, FL | Razor's Edge |
+
+We also need to make sure inline code looks good, like if I wanted to talk about `` elements or tell you the good news about `@tailwindcss/typography`.
+
+### Sometimes I even use `code` in headings
+
+Even though it's probably a bad idea, and historically I've had a hard time making it look good. This _"wrap the code blocks in backticks"_ trick works pretty well though really.
+
+Another thing I've done in the past is put a `code` tag inside of a link, like if I wanted to tell you about the [`tailwindcss/docs`](https://github.com/tailwindcss/docs) repository. I don't love that there is an underline below the backticks but it is absolutely not worth the madness it would require to avoid it.
+
+#### We haven't used an `h4` yet
+
+But now we have. Please don't use `h5` or `h6` in your content, Medium only supports two heading levels for a reason, you animals. I honestly considered using a `before` pseudo-element to scream at you if you use an `h5` or `h6`.
+
+We don't style them at all out of the box because `h4` elements are already so small that they are the same size as the body copy. What are we supposed to do with an `h5`, make it _smaller_ than the body copy? No thanks.
+
+### We still need to think about stacked headings though.
+
+#### Let's make sure we don't screw that up with `h4` elements, either.
+
+Phew, with any luck we have styled the headings above this text and they look pretty good.
+
+Let's add a closing paragraph here so things end with a decently sized block of text. I can't explain why I want things to end that way but I have to assume it's because I think things will look weird or unbalanced if there is a heading too close to the end of the document.
+
+What I've written here is probably long enough, but adding this final sentence can't hurt.
+
+## GitHub Flavored Markdown
+
+I've also added support for GitHub Flavored Mardown using `remark-gfm`.
+
+With `remark-gfm`, we get a few extra features in our markdown. Example: autolink literals.
+
+A link like www.example.com or https://example.com would automatically be converted into an `a` tag.
+
+This works for email links too: contact@example.com.
diff --git a/apps/www/src/components/content/templete-blog/server-client-components.mdx b/apps/www/src/components/content/templete-blog/server-client-components.mdx
new file mode 100644
index 0000000..f71d58c
--- /dev/null
+++ b/apps/www/src/components/content/templete-blog/server-client-components.mdx
@@ -0,0 +1,219 @@
+---
+title: Server and Client Components
+description: React Server Components allow developers to build applications that span the server and client.
+image: /images/blog/blog-post-4.jpg
+date: "2023-01-08"
+authors:
+ - shadcn
+---
+
+
+ The text below is from the [Tailwind
+ CSS](https://play.tailwindcss.com/uj1vGACRJA?layout=preview) docs. I copied it
+ here to test the markdown styles. **Tailwind is awesome. You should use it.**
+
+
+Until now, trying to style an article, document, or blog post with Tailwind has been a tedious task that required a keen eye for typography and a lot of complex custom CSS.
+
+By default, Tailwind removes all of the default browser styling from paragraphs, headings, lists and more. This ends up being really useful for building application UIs because you spend less time undoing user-agent styles, but when you _really are_ just trying to style some content that came from a rich-text editor in a CMS or a markdown file, it can be surprising and unintuitive.
+
+We get lots of complaints about it actually, with people regularly asking us things like:
+
+> Why is Tailwind removing the default styles on my `h1` elements? How do I disable this? What do you mean I lose all the other base styles too?
+> We hear you, but we're not convinced that simply disabling our base styles is what you really want. You don't want to have to remove annoying margins every time you use a `p` element in a piece of your dashboard UI. And I doubt you really want your blog posts to use the user-agent styles either โ you want them to look _awesome_, not awful.
+
+The `@tailwindcss/typography` plugin is our attempt to give you what you _actually_ want, without any of the downsides of doing something stupid like disabling our base styles.
+
+It adds a new `prose` class that you can slap on any block of vanilla HTML content and turn it into a beautiful, well-formatted document:
+
+```html
+
+
Garlic bread with cheese: What the science tells us
+
+ For years parents have espoused the health benefits of eating garlic bread
+ with cheese to their children, with the food earning such an iconic status
+ in our culture that kids will often dress up as warm, cheesy loaf for
+ Halloween.
+
+
+ But a recent study shows that the celebrated appetizer may be linked to a
+ series of rabies cases springing up around the country.
+
+
+```
+
+For more information about how to use the plugin and the features it includes, [read the documentation](https://github.com/tailwindcss/typography/blob/master/README.md).
+
+---
+
+## What to expect from here on out
+
+What follows from here is just a bunch of absolute nonsense I've written to dogfood the plugin itself. It includes every sensible typographic element I could think of, like **bold text**, unordered lists, ordered lists, code blocks, block quotes, _and even italics_.
+
+It's important to cover all of these use cases for a few reasons:
+
+1. We want everything to look good out of the box.
+2. Really just the first reason, that's the whole point of the plugin.
+3. Here's a third pretend reason though a list with three items looks more realistic than a list with two items.
+
+Now we're going to try out another header style.
+
+### Typography should be easy
+
+So that's a header for you โ with any luck if we've done our job correctly that will look pretty reasonable.
+
+Something a wise person once told me about typography is:
+
+> Typography is pretty important if you don't want your stuff to look like trash. Make it good then it won't be bad.
+
+It's probably important that images look okay here by default as well:
+
+
+
+Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots in a piece of classical Latin literature from 45 BC, making it over 2000 years old.
+
+Now I'm going to show you an example of an unordered list to make sure that looks good, too:
+
+- So here is the first item in this list.
+- In this example we're keeping the items short.
+- Later, we'll use longer, more complex list items.
+
+And that's the end of this section.
+
+## What if we stack headings?
+
+### We should make sure that looks good, too.
+
+Sometimes you have headings directly underneath each other. In those cases you often have to undo the top margin on the second heading because it usually looks better for the headings to be closer together than a paragraph followed by a heading should be.
+
+### When a heading comes after a paragraph โฆ
+
+When a heading comes after a paragraph, we need a bit more space, like I already mentioned above. Now let's see what a more complex list would look like.
+
+- **I often do this thing where list items have headings.**
+
+ For some reason I think this looks cool which is unfortunate because it's pretty annoying to get the styles right.
+
+ I often have two or three paragraphs in these list items, too, so the hard part is getting the spacing between the paragraphs, list item heading, and separate list items to all make sense. Pretty tough honestly, you could make a strong argument that you just shouldn't write this way.
+
+- **Since this is a list, I need at least two items.**
+
+ I explained what I'm doing already in the previous list item, but a list wouldn't be a list if it only had one item, and we really want this to look realistic. That's why I've added this second list item so I actually have something to look at when writing the styles.
+
+- **It's not a bad idea to add a third item either.**
+
+ I think it probably would've been fine to just use two items but three is definitely not worse, and since I seem to be having no trouble making up arbitrary things to type, I might as well include it.
+
+After this sort of list I usually have a closing statement or paragraph, because it kinda looks weird jumping right to a heading.
+
+## Code should look okay by default.
+
+I think most people are going to use [highlight.js](https://highlightjs.org/) or [Prism](https://prismjs.com/) or something if they want to style their code blocks but it wouldn't hurt to make them look _okay_ out of the box, even with no syntax highlighting.
+
+Here's what a default `tailwind.config.js` file looks like at the time of writing:
+
+```js
+module.exports = {
+ purge: [],
+ theme: {
+ extend: {},
+ },
+ variants: {},
+ plugins: [],
+};
+```
+
+Hopefully that looks good enough to you.
+
+### What about nested lists?
+
+Nested lists basically always look bad which is why editors like Medium don't even let you do it, but I guess since some of you goofballs are going to do it we have to carry the burden of at least making it work.
+
+1. **Nested lists are rarely a good idea.**
+ - You might feel like you are being really "organized" or something but you are just creating a gross shape on the screen that is hard to read.
+ - Nested navigation in UIs is a bad idea too, keep things as flat as possible.
+ - Nesting tons of folders in your source code is also not helpful.
+2. **Since we need to have more items, here's another one.**
+ - I'm not sure if we'll bother styling more than two levels deep.
+ - Two is already too much, three is guaranteed to be a bad idea.
+ - If you nest four levels deep you belong in prison.
+3. **Two items isn't really a list, three is good though.**
+ - Again please don't nest lists if you want people to actually read your content.
+ - Nobody wants to look at this.
+ - I'm upset that we even have to bother styling this.
+
+The most annoying thing about lists in Markdown is that `
` elements aren't given a child `
` tag unless there are multiple paragraphs in the list item. That means I have to worry about styling that annoying situation too.
+
+- **For example, here's another nested list.**
+
+ But this time with a second paragraph.
+
+ - These list items won't have `
` tags
+ - Because they are only one line each
+
+- **But in this second top-level list item, they will.**
+
+ This is especially annoying because of the spacing on this paragraph.
+
+ - As you can see here, because I've added a second line, this list item now has a `
` tag.
+
+ This is the second line I'm talking about by the way.
+
+ - Finally here's another list item so it's more like a list.
+
+- A closing list item, but with no nested list, because why not?
+
+And finally a sentence to close off this section.
+
+## There are other elements we need to style
+
+I almost forgot to mention links, like [this link to the Tailwind CSS website](https://tailwindcss.com). We almost made them blue but that's so yesterday, so we went with dark gray, feels edgier.
+
+We even included table styles, check it out:
+
+| Wrestler | Origin | Finisher |
+| ----------------------- | ------------ | ------------------ |
+| Bret "The Hitman" Hart | Calgary, AB | Sharpshooter |
+| Stone Cold Steve Austin | Austin, TX | Stone Cold Stunner |
+| Randy Savage | Sarasota, FL | Elbow Drop |
+| Vader | Boulder, CO | Vader Bomb |
+| Razor Ramon | Chuluota, FL | Razor's Edge |
+
+We also need to make sure inline code looks good, like if I wanted to talk about `` elements or tell you the good news about `@tailwindcss/typography`.
+
+### Sometimes I even use `code` in headings
+
+Even though it's probably a bad idea, and historically I've had a hard time making it look good. This _"wrap the code blocks in backticks"_ trick works pretty well though really.
+
+Another thing I've done in the past is put a `code` tag inside of a link, like if I wanted to tell you about the [`tailwindcss/docs`](https://github.com/tailwindcss/docs) repository. I don't love that there is an underline below the backticks but it is absolutely not worth the madness it would require to avoid it.
+
+#### We haven't used an `h4` yet
+
+But now we have. Please don't use `h5` or `h6` in your content, Medium only supports two heading levels for a reason, you animals. I honestly considered using a `before` pseudo-element to scream at you if you use an `h5` or `h6`.
+
+We don't style them at all out of the box because `h4` elements are already so small that they are the same size as the body copy. What are we supposed to do with an `h5`, make it _smaller_ than the body copy? No thanks.
+
+### We still need to think about stacked headings though.
+
+#### Let's make sure we don't screw that up with `h4` elements, either.
+
+Phew, with any luck we have styled the headings above this text and they look pretty good.
+
+Let's add a closing paragraph here so things end with a decently sized block of text. I can't explain why I want things to end that way but I have to assume it's because I think things will look weird or unbalanced if there is a heading too close to the end of the document.
+
+What I've written here is probably long enough, but adding this final sentence can't hurt.
+
+## GitHub Flavored Markdown
+
+I've also added support for GitHub Flavored Mardown using `remark-gfm`.
+
+With `remark-gfm`, we get a few extra features in our markdown. Example: autolink literals.
+
+A link like www.example.com or https://example.com would automatically be converted into an `a` tag.
+
+This works for email links too: contact@example.com.
diff --git a/apps/www/src/components/dashboard/EventsDashboard.tsx b/apps/www/src/components/dashboard/EventsDashboard.tsx
new file mode 100644
index 0000000..fec5c60
--- /dev/null
+++ b/apps/www/src/components/dashboard/EventsDashboard.tsx
@@ -0,0 +1,50 @@
+"use client";
+
+import { useState } from "react";
+
+import { AddApiKeyButton } from "@/components/buttons/AddApiKeyButton";
+import { EmptyPlaceholder } from "@/components/shared/empty-placeholder";
+
+import { DocsButton } from "../buttons/DocsButton";
+import { EventDashboardDetailsSheet } from "./EventsDashboardComponents/EventDashboardDetailsSheet";
+import EventsDashboardCards from "./EventsDashboardComponents/EventsDashboardCards";
+import EventsDashboardDetails from "./EventsDashboardComponents/EventsDashboardDetails";
+import EventsDashboardTable from "./EventsDashboardComponents/EventsDashboardTable";
+
+export default function EventsDashboard({ events, eventStats }) {
+ const [selectedEventId, setSelectedEventId] = useState(events[0]?.id);
+
+ const selectedEvent = events.find((event) => event.id === selectedEventId);
+
+ return (
+
+
+
+
+
+ {events.length > 0 ? (
+
+ ) : (
+
+
+ There are no events
+
+ You need to create an event first to see it here
+
+
+
+
+
+
+ )}
+
+
+
+
+
+ );
+}
diff --git a/apps/www/src/components/dashboard/EventsDashboardComponents/EventDashboardDetailsSheet.tsx b/apps/www/src/components/dashboard/EventsDashboardComponents/EventDashboardDetailsSheet.tsx
new file mode 100644
index 0000000..0949d63
--- /dev/null
+++ b/apps/www/src/components/dashboard/EventsDashboardComponents/EventDashboardDetailsSheet.tsx
@@ -0,0 +1,213 @@
+"use client";
+
+import Link from "next/link";
+import { createEvent } from "@/actions/create-event";
+import { zodResolver } from "@hookform/resolvers/zod";
+import { useForm } from "react-hook-form";
+import { z } from "zod";
+
+import { Button } from "@dingify/ui/components/button";
+import { Checkbox } from "@dingify/ui/components/checkbox";
+import {
+ Form,
+ FormControl,
+ FormDescription,
+ FormField,
+ FormItem,
+ FormLabel,
+ FormMessage,
+} from "@dingify/ui/components/form";
+import { Input } from "@dingify/ui/components/input";
+import {
+ Sheet,
+ SheetClose,
+ SheetContent,
+ SheetDescription,
+ SheetFooter,
+ SheetHeader,
+ SheetTitle,
+ SheetTrigger,
+} from "@dingify/ui/components/sheet";
+import { toast } from "sonner";
+
+// Define the validation schema
+const FormSchema = z.object({
+ channel: z.string().min(1, "Channel is required"),
+ name: z.string().min(1, "Name is required"),
+ event: z.string().min(1, "Event is required"),
+ user_id: z.string().min(1, "User ID is required"),
+ icon: z.string().min(1, "Icon is required"),
+ notify: z.boolean(),
+});
+
+export function EventDashboardDetailsSheet() {
+ const form = useForm({
+ resolver: zodResolver(FormSchema),
+ defaultValues: {
+ channel: "",
+ name: "",
+ event: "",
+ user_id: "",
+ icon: "",
+ notify: true,
+ },
+ });
+
+ const onSubmit = async (data) => {
+ console.log("Form data to submit:", data); // Log form dat
+ try {
+ const result = await createEvent(data);
+ if (result.success) {
+ toast.message(
+
+ Event Created.
+
+
+ {JSON.stringify(data, null, 2)}
+
+
+
);
+ console.log("Event created:", result.event); // Log the created event
+ // Optionally refresh the page or clear the form
+ form.reset();
+ }
+ } catch (error) {
+ toast.error("There was an error creating the event.");
+ console.error("Error creating event:", error); // Log any error
+ }
+ };
+
+ return (
+
+
+
+
+
+
+ Create Event
+
+ Fill in the details to create a new event.
+
+
+
+
+
+
+ );
+}
diff --git a/apps/www/src/components/dashboard/EventsDashboardComponents/EventsDashboardCards.tsx b/apps/www/src/components/dashboard/EventsDashboardComponents/EventsDashboardCards.tsx
new file mode 100644
index 0000000..802355c
--- /dev/null
+++ b/apps/www/src/components/dashboard/EventsDashboardComponents/EventsDashboardCards.tsx
@@ -0,0 +1,78 @@
+import { Button } from "@dingify/ui/components/button";
+import {
+ Card,
+ CardContent,
+ CardDescription,
+ CardFooter,
+ CardHeader,
+ CardTitle,
+} from "@dingify/ui/components/card";
+import { Progress } from "@dingify/ui/components/progress";
+
+import { CreateEventButton } from "@/components/buttons/CreatEventButton";
+
+import { EventDashboardDetailsSheet } from "./EventDashboardDetailsSheet";
+
+export default function EventsDashboardCards({ eventStats }) {
+ return (
+ <>
+
+
+ Your Events
+
+ Introducing Our Dynamic Orders Dashboard for Seamless Management and
+ Insightful Analysis.
+
+
+
+ {/* */}
+
+
+
+
+
+ This Week
+
+ {eventStats.currentWeekEvents}
+
+
+
+
+ {eventStats.weeklyChange >= 0
+ ? `+${eventStats.weeklyChange.toFixed(2)}%`
+ : `${eventStats.weeklyChange.toFixed(2)}%`}{" "}
+ from last week
+
+
+ Streamline your property listings and client interactions with the
+ precision of AI. Propwrite delivers a suite of tools that elevate your
+ efficiency and let you focus on closing deals โ not on paperwork.
+
+
+ );
+};
+
+export default FeatureSection1;
diff --git a/apps/www/src/components/dashboard/feautressection.tsx b/apps/www/src/components/dashboard/feautressection.tsx
new file mode 100644
index 0000000..f5fe5ee
--- /dev/null
+++ b/apps/www/src/components/dashboard/feautressection.tsx
@@ -0,0 +1,122 @@
+import {
+ ArrowPathIcon,
+ CloudArrowUpIcon,
+ Cog6ToothIcon,
+ FingerPrintIcon,
+ LockClosedIcon,
+ ServerIcon,
+} from "@heroicons/react/20/solid";
+import { Balancer } from "react-wrap-balancer";
+
+const features = [
+ {
+ name: "Revolutionizing Real Estate: AI-Powered Listings",
+ description:
+ "Instantly draft standout property listings with our advanced AI editor, designed to captivate and attract potential buyers through eloquent, detail-rich descriptions.",
+ icon: CloudArrowUpIcon,
+ },
+ {
+ name: "Elevate Your Realty Game with Propwrite",
+ description:
+ "Empower your real estate business with Propwrite's SSL encryption, ensuring that all client information and property data are secure and protected.",
+ icon: LockClosedIcon,
+ },
+ {
+ name: "Next-Gen Property Management: AI Meets Real Estate",
+ description:
+ "Our platform simplifies property management by automating follow-ups and updates, freeing you to focus on what you do best โ closing deals.",
+ icon: ArrowPathIcon,
+ },
+ {
+ name: "AI-Enhanced Listings for Smart Agents",
+ description:
+ "Stay ahead of security threats with real-time monitoring and automatic updates, safeguarding your listings with the latest in AI technology.",
+ icon: FingerPrintIcon,
+ },
+ {
+ name: "Maximize Sales with Intelligent Real Estate Solutions",
+ description:
+ "Integrate Propwrite's comprehensive API with your current tools for a seamless experience that enhances your workflow and maximizes efficiency.",
+ icon: Cog6ToothIcon,
+ },
+ {
+ name: "Unlock Real Estate Potential with AI Efficiency",
+ description:
+ "Ensure your listings are always current and never lost with our reliable backup solutions, providing peace of mind and data security.",
+ icon: ServerIcon,
+ },
+];
+
+export default function Featuressection() {
+ return (
+
+
+
+
+
+ Propwrite
+
+
+
+
+ Streamlined Real Estate Efficiency
+
+
+
+
+ Propwrite redefines property listing management with
+ state-of-the-art AI, delivering unparalleled efficiency and
+ precision. Experience the future of real estateโwhere technology
+ enhances every transaction, every client interaction, and every
+ sale
+
+
+
+ Email{" "}
+
+ support@propwrite.com
+ {" "}
+ for to contact our support team.
+
+
+ You can test the subscriptions and won't be charged.
+
+
+
+
+ );
+}
diff --git a/apps/www/src/components/pricing-faq.tsx b/apps/www/src/components/pricing-faq.tsx
new file mode 100644
index 0000000..962f795
--- /dev/null
+++ b/apps/www/src/components/pricing-faq.tsx
@@ -0,0 +1,74 @@
+import Balancer from "react-wrap-balancer";
+
+import {
+ Accordion,
+ AccordionContent,
+ AccordionItem,
+ AccordionTrigger,
+} from "@dingify/ui/components/accordion";
+
+const pricingFaqData = [
+ {
+ id: "item-1",
+ question: "How does Dingify help with real-time monitoring and analytics?",
+ answer:
+ "Dingify provides comprehensive real-time monitoring and analytics by capturing critical business events, tracking user journeys, and offering detailed KPIs and insights. Make data-driven decisions to optimize your business performance.",
+ },
+ {
+ id: "item-2",
+ question: "Can I integrate Dingify with my existing business tools?",
+ answer:
+ "Absolutely! Dingify is built with integration in mind. Our comprehensive API allows you to seamlessly connect with your existing business tools, ensuring a smooth addition to your current workflow.",
+ },
+ {
+ id: "item-3",
+ question: "What kind of support can I expect with Dingify?",
+ answer:
+ "We offer dedicated support for all our users. Whether you're on a free or paid plan, our team is ready to assist you with any questions or issues you may encounter. Premium support options are available for our Pro plan subscribers.",
+ },
+ {
+ id: "item-4",
+ question: "Is my data secure with Dingify?",
+ answer:
+ "Data security is our top priority. We employ SSL encryption and adhere to industry best practices to ensure that all your data, from event tracking to customer information, is securely stored and protected.",
+ },
+ {
+ id: "item-5",
+ question: "How does the free plan differ from the paid plans?",
+ answer:
+ "The free plan offers basic features that allow you to experience the advantages of Dingify's real-time monitoring. Our paid plans provide access to more advanced features, including detailed analytics, priority support, and increased event volume.",
+ },
+ {
+ id: "item-6",
+ question: "What additional features does the Pro plan include?",
+ answer:
+ "The Pro plan includes everything in the Basic plan plus advanced analytics, priority support, higher event volume, custom API integrations, and access to new features before they're publicly released.",
+ },
+];
+
+export function PricingFaq() {
+ return (
+
+
+
+ Frequently Asked Questions
+
+
+
+ Explore our comprehensive FAQ to find quick answers to common
+ inquiries. If you need further assistance, don't hesitate to
+ contact us for personalized help.
+
+
+
+
+ {pricingFaqData.map((faqItem) => (
+
+ {faqItem.question}
+ {faqItem.answer}
+
+ ))}
+
+
+ );
+}
diff --git a/apps/www/src/components/properties/NoPhotoPlaceholder copy.tsx b/apps/www/src/components/properties/NoPhotoPlaceholder copy.tsx
new file mode 100644
index 0000000..14e7ff7
--- /dev/null
+++ b/apps/www/src/components/properties/NoPhotoPlaceholder copy.tsx
@@ -0,0 +1,24 @@
+"use client";
+
+import { Button } from "@dingify/ui/components/button";
+
+import { EmptyPlaceholder } from "@/components/shared/empty-placeholder";
+
+import { DocsButton } from "../buttons/DocsButton";
+
+export default function NoPhotoPlaceholder() {
+ return (
+
+
+ Your events
+
+ Your events for this channel will appear here.
+
+
+
+
+
+
+
+ );
+}
diff --git a/apps/www/src/components/properties/NoSummaryPlaceholder.tsx b/apps/www/src/components/properties/NoSummaryPlaceholder.tsx
new file mode 100644
index 0000000..ab63311
--- /dev/null
+++ b/apps/www/src/components/properties/NoSummaryPlaceholder.tsx
@@ -0,0 +1,18 @@
+"use client";
+
+import { EmptyPlaceholder } from "@/components/shared/empty-placeholder";
+
+import { Button } from "@dingify/ui/components/button";
+
+export default function NoSummaryPlaceholder({ propertyId, slug }) {
+ return (
+
+
+ Upload pictures
+
+ Upload pictures to start and let us create the text
+
+
+
+ );
+}
diff --git a/apps/www/src/components/properties/NoTextPlaceholder.tsx b/apps/www/src/components/properties/NoTextPlaceholder.tsx
new file mode 100644
index 0000000..27cfc80
--- /dev/null
+++ b/apps/www/src/components/properties/NoTextPlaceholder.tsx
@@ -0,0 +1,22 @@
+"use client";
+
+import { EmptyPlaceholder } from "@/components/shared/empty-placeholder";
+
+import GenerateDescriptionButton2 from "../buttons/GenerateDescriptionButton2";
+
+export default function NoTextPlaceholder({ propertyId, setDescriptionData }) {
+ return (
+
+
+ Generate description
+
+ Let Propwrite make the summary and text for you.
+
+
+ {/* */}
+
+ );
+}
diff --git a/apps/www/src/components/properties/Propertiestable.tsx b/apps/www/src/components/properties/Propertiestable.tsx
new file mode 100644
index 0000000..387065e
--- /dev/null
+++ b/apps/www/src/components/properties/Propertiestable.tsx
@@ -0,0 +1,78 @@
+"use client";
+
+import { useState } from "react";
+import Link from "next/link";
+
+import {
+ Table,
+ TableBody,
+ TableCaption,
+ TableCell,
+ TableHead,
+ TableRow,
+} from "@dingify/ui/components/table";
+
+const PropertiesTable = ({ properties }) => {
+ const [sortKey, setSortKey] = useState("createdAt"); // default sort key
+ const [sortOrder, setSortOrder] = useState("desc"); // default sort order
+ const [filter, setFilter] = useState("");
+
+ // Sort and filter the properties
+ const sortedFilteredProperties = properties
+ .filter((property) =>
+ property.address.toLowerCase().includes(filter.toLowerCase())
+ )
+ .sort((a, b) => {
+ if (a[sortKey] < b[sortKey]) return sortOrder === "asc" ? -1 : 1;
+ if (a[sortKey] > b[sortKey]) return sortOrder === "asc" ? 1 : -1;
+ return 0;
+ });
+
+ const toggleSort = (key) => {
+ if (sortKey === key) {
+ setSortOrder(sortOrder === "asc" ? "desc" : "asc");
+ } else {
+ setSortKey(key);
+ setSortOrder("asc");
+ }
+ };
+
+ return (
+ <>
+ setFilter(e.target.value)}
+ className="mb-4 w-full rounded-md border-2 px-4 py-2"
+ />
+
+ A list of your properties.
+
+
+ toggleSort("address")}>Address
+ toggleSort("createdAt")}>
+ Date Added
+
+
+
+
+ {sortedFilteredProperties.map((property) => (
+
+
+
+ {property.address}
+
+
+
+ {new Date(property.createdAt).toLocaleDateString()}
+
+
+ ))}
+
+
+ );
+};
+
+export default PropertyImageWithOptions;
diff --git a/apps/www/src/components/properties/PropertyPicture.tsx b/apps/www/src/components/properties/PropertyPicture.tsx
new file mode 100644
index 0000000..e5795c4
--- /dev/null
+++ b/apps/www/src/components/properties/PropertyPicture.tsx
@@ -0,0 +1,25 @@
+import Image from "next/image";
+
+export default function PropertyPicture({ src, alt }) {
+ // If you want to have a default image, you can set it here
+ const defaultImage = "default_image_path.jpg";
+
+ return (
+
+
+
+ );
+}
+
+PropertyPicture.defaultProps = {
+ src: "https://images.finncdn.no/dynamic/1600w/2023/11/vertical-2/10/2/318/430/822_1071303782.jpg", // Default src as empty string or any default image path
+ alt: "Property Image", // Default alt text
+ width: 500, // Example default width
+ height: 300, // Example default height
+};
diff --git a/apps/www/src/components/providers.tsx b/apps/www/src/components/providers.tsx
new file mode 100644
index 0000000..f6763e7
--- /dev/null
+++ b/apps/www/src/components/providers.tsx
@@ -0,0 +1,20 @@
+"use client";
+
+import { SessionProvider } from "next-auth/react";
+import { ThemeProvider as NextThemesProvider } from "next-themes";
+import { ThemeProviderProps } from "next-themes/dist/types";
+import { Provider as BalancerProvider } from "react-wrap-balancer";
+
+import { TooltipProvider } from "@dingify/ui/components/tooltip";
+
+export function Providers({ children, ...props }: ThemeProviderProps) {
+ return (
+
+
+
+ {children}
+
+
+
+ );
+}
diff --git a/apps/www/src/components/shared/callout.tsx b/apps/www/src/components/shared/callout.tsx
new file mode 100644
index 0000000..6655e09
--- /dev/null
+++ b/apps/www/src/components/shared/callout.tsx
@@ -0,0 +1,32 @@
+import { cn } from "@/lib/utils";
+
+interface CalloutProps {
+ icon?: string;
+ children?: React.ReactNode;
+ type?: "default" | "warning" | "danger" | "info";
+}
+
+// โ ๐กโ ๏ธ๐ซ๐จ
+export function Callout({
+ children,
+ icon,
+ type = "default",
+ ...props
+}: CalloutProps) {
+ return (
+
+ {icon && {icon}}
+
{children}
+
+ );
+}
diff --git a/apps/www/src/components/shared/card-skeleton.tsx b/apps/www/src/components/shared/card-skeleton.tsx
new file mode 100644
index 0000000..c83ea38
--- /dev/null
+++ b/apps/www/src/components/shared/card-skeleton.tsx
@@ -0,0 +1,22 @@
+import {
+ Card,
+ CardContent,
+ CardFooter,
+ CardHeader,
+} from "@dingify/ui/components/card";
+import { Skeleton } from "@dingify/ui/components/skeleton";
+
+export function CardSkeleton() {
+ return (
+
+
+
+
+
+
+
+
+
+
+ );
+}
diff --git a/apps/www/src/components/shared/empty-placeholder.tsx b/apps/www/src/components/shared/empty-placeholder.tsx
new file mode 100644
index 0000000..a457a62
--- /dev/null
+++ b/apps/www/src/components/shared/empty-placeholder.tsx
@@ -0,0 +1,81 @@
+import * as React from "react";
+import { Icons } from "@/components/shared/icons";
+import { cn } from "@/lib/utils";
+
+type EmptyPlaceholderProps = React.HTMLAttributes;
+
+export function EmptyPlaceholder({
+ className,
+ children,
+ ...props
+}: EmptyPlaceholderProps) {
+ return (
+
+
+
+ );
+}
diff --git a/apps/www/src/config/dashboard.ts b/apps/www/src/config/dashboard.ts
new file mode 100644
index 0000000..87c73c8
--- /dev/null
+++ b/apps/www/src/config/dashboard.ts
@@ -0,0 +1,59 @@
+import { DashboardConfig } from "@/types";
+
+export const dashboardConfig: DashboardConfig = {
+ mainNav: [
+ {
+ title: "Docs",
+ href: "https://docs.dingify.io/",
+ },
+ {
+ title: "Support",
+ href: "/support",
+ disabled: true,
+ },
+ ],
+ sidebarNav: [
+ {
+ title: "Dashboard",
+ href: "/dashboard",
+ icon: "home",
+ },
+ {
+ title: "Analytics",
+ href: "/dashboard/analytics",
+ icon: "piechart",
+ },
+ {
+ title: "Users",
+ href: "/dashboard/users",
+ icon: "user",
+ },
+ {
+ title: "Notifications",
+ href: "/dashboard/notifications",
+ icon: "bell",
+ },
+ {
+ title: "Billing",
+ href: "/dashboard/billing",
+ icon: "billing",
+ },
+ {
+ title: "Settings",
+ href: "/dashboard/settings",
+ icon: "settings",
+ },
+ // {
+ // title: "Placeholder Names",
+ // href: "/dashboard/channels",
+ // },
+ // {
+ // title: "Marketing",
+ // href: "/dashboard/channels/marketing",
+ // },
+ // {
+ // title: "Sales",
+ // href: "/dashboard/channels/sales",
+ // },
+ ],
+};
diff --git a/apps/www/src/config/docs.ts b/apps/www/src/config/docs.ts
new file mode 100644
index 0000000..785b702
--- /dev/null
+++ b/apps/www/src/config/docs.ts
@@ -0,0 +1,106 @@
+import { DocsConfig } from "@/types";
+
+export const docsConfig: DocsConfig = {
+ mainNav: [
+ {
+ title: "Documentation",
+ href: "/docs",
+ },
+ {
+ title: "Guides",
+ href: "/guides",
+ },
+ ],
+ sidebarNav: [
+ {
+ title: "Getting Started",
+ items: [
+ {
+ title: "Introduction",
+ href: "/docs",
+ },
+ ],
+ },
+ {
+ title: "Documentation",
+ items: [
+ {
+ title: "Introduction",
+ href: "/docs/documentation",
+ },
+ {
+ title: "Contentlayer",
+ href: "/docs/in-progress",
+ disabled: true,
+ },
+ {
+ title: "Components",
+ href: "/docs/documentation/components",
+ },
+ {
+ title: "Code Blocks",
+ href: "/docs/documentation/code-blocks",
+ },
+ {
+ title: "Style Guide",
+ href: "/docs/documentation/style-guide",
+ },
+ ],
+ },
+ {
+ title: "Blog",
+ items: [
+ {
+ title: "Introduction",
+ href: "/docs/in-progress",
+ disabled: true,
+ },
+ {
+ title: "Build your own",
+ href: "/docs/in-progress",
+ disabled: true,
+ },
+ {
+ title: "Writing Posts",
+ href: "/docs/in-progress",
+ disabled: true,
+ },
+ ],
+ },
+ {
+ title: "Dashboard",
+ items: [
+ {
+ title: "Introduction",
+ href: "/docs/in-progress",
+ disabled: true,
+ },
+ {
+ title: "Layouts",
+ href: "/docs/in-progress",
+ disabled: true,
+ },
+ {
+ title: "Server Components",
+ href: "/docs/in-progress",
+ disabled: true,
+ },
+ {
+ title: "Authentication",
+ href: "/docs/in-progress",
+ disabled: true,
+ },
+ {
+ title: "Database with Prisma",
+ href: "/docs/in-progress",
+ disabled: true,
+ },
+ {
+ title: "API Routes",
+ href: "/docs/in-progress",
+ disabled: true,
+ },
+ ],
+ },
+ ],
+};
diff --git a/apps/www/src/config/marketing.ts b/apps/www/src/config/marketing.ts
new file mode 100644
index 0000000..8d02c9b
--- /dev/null
+++ b/apps/www/src/config/marketing.ts
@@ -0,0 +1,29 @@
+import type { MarketingConfig } from "@/types";
+
+export const marketingConfig: MarketingConfig = {
+ mainNav: [
+ {
+ title: "Docs",
+ href: "https://docs.dingify.io/",
+ },
+ {
+ title: "Open Startup",
+ href: "/open",
+ },
+ {
+ title: "Pricing",
+ href: "/pricing",
+ disabled: true,
+ },
+ {
+ title: "Blog",
+ href: "/blog",
+ disabled: true,
+ },
+ // {
+ // title: "Documentation",
+ // href: "/docs",
+ // disabled: true,
+ // },
+ ],
+};
diff --git a/apps/www/src/config/property.ts b/apps/www/src/config/property.ts
new file mode 100644
index 0000000..9bb6657
--- /dev/null
+++ b/apps/www/src/config/property.ts
@@ -0,0 +1,41 @@
+import { PropertyConfig } from "@/types";
+
+export const propertyConfig: PropertyConfig = {
+ mainNav: [
+ {
+ title: "Dashboard",
+ href: "/dashboard",
+ },
+ // {
+ // title: "Documentation",
+ // href: "/docs",
+ // },
+ {
+ title: "Support",
+ href: "/support",
+ disabled: true,
+ },
+ ],
+ sidebarNav: [
+ {
+ title: "Summary",
+ href: "/",
+ icon: "piechart",
+ },
+ {
+ title: "Pictures",
+ href: `/pictures`,
+ icon: "media",
+ },
+ {
+ title: "Appraisal Report",
+ href: "/report",
+ icon: "home",
+ },
+ // {
+ // title: "Settings",
+ // href: "/settings",
+ // icon: "settings",
+ // },
+ ],
+};
diff --git a/apps/www/src/config/site.ts b/apps/www/src/config/site.ts
new file mode 100644
index 0000000..81fb241
--- /dev/null
+++ b/apps/www/src/config/site.ts
@@ -0,0 +1,17 @@
+import type { SiteConfig } from "@/types";
+import { env } from "@/env";
+
+const site_url = env.NEXT_PUBLIC_APP_URL;
+
+export const siteConfig: SiteConfig = {
+ name: "Dingify",
+ description:
+ "Dingify revolutionizes alearts and notifications for developers and businesses",
+ url: site_url,
+ ogImage: `${site_url}/og.jpg`,
+ links: {
+ twitter: "https://twitter.com/codehagen",
+ github: "https://github.com/meglerhagen",
+ },
+ mailSupport: "christer@sailsdock.com",
+};
diff --git a/apps/www/src/config/subscriptions.ts b/apps/www/src/config/subscriptions.ts
new file mode 100644
index 0000000..6c7a3fe
--- /dev/null
+++ b/apps/www/src/config/subscriptions.ts
@@ -0,0 +1,71 @@
+import type { SubscriptionPlan } from "@/types";
+import { env } from "@/env";
+
+export const pricingData: SubscriptionPlan[] = [
+ {
+ title: "Starter",
+ description: "For Beginners",
+ benefits: [
+ "Up to 3 listings",
+ "Basic analytics and reporting",
+ "Access to standard templates",
+ ],
+ limitations: [
+ "No priority access to new features.",
+ "Limited customer support",
+ "No custom branding",
+ "Limited access to business resources.",
+ ],
+ prices: {
+ monthly: 0,
+ yearly: 0,
+ },
+ stripeIds: {
+ monthly: null,
+ yearly: null,
+ },
+ },
+ {
+ title: "Pro",
+ description: "Unlock Advanced Features",
+ benefits: [
+ "Up to 20 monthly listings",
+ "Advanced analytics and reporting",
+ "Access to business templates",
+ "Priority customer support",
+ "Exclusive webinars and training.",
+ ],
+ limitations: [
+ "No custom branding",
+ "Limited access to business resources.",
+ ],
+ prices: {
+ monthly: 40,
+ yearly: 384,
+ },
+ stripeIds: {
+ monthly: env.NEXT_PUBLIC_STRIPE_PRO_MONTHLY_PLAN_ID,
+ yearly: env.NEXT_PUBLIC_STRIPE_PRO_YEARLY_PLAN_ID,
+ },
+ },
+ {
+ title: "Business",
+ description: "For Power Users",
+ benefits: [
+ "Unlimited posts",
+ "Real-time analytics and reporting",
+ "Access to all templates, including custom branding",
+ "24/7 business customer support",
+ "Personalized onboarding and account management.",
+ ],
+ limitations: [],
+ prices: {
+ monthly: 60,
+ yearly: 576,
+ },
+ stripeIds: {
+ monthly: env.NEXT_PUBLIC_STRIPE_BUSINESS_MONTHLY_PLAN_ID,
+ yearly: env.NEXT_PUBLIC_STRIPE_BUSINESS_YEARLY_PLAN_ID,
+ },
+ },
+];
diff --git a/apps/www/src/content/authors/codehagen.mdx b/apps/www/src/content/authors/codehagen.mdx
new file mode 100644
index 0000000..28fca2d
--- /dev/null
+++ b/apps/www/src/content/authors/codehagen.mdx
@@ -0,0 +1,5 @@
+---
+title: Christer
+avatar: /images/avatars/shadcn.png
+twitter: codehagen
+---
diff --git a/apps/www/src/content/authors/shadcn.mdx b/apps/www/src/content/authors/shadcn.mdx
new file mode 100644
index 0000000..0883499
--- /dev/null
+++ b/apps/www/src/content/authors/shadcn.mdx
@@ -0,0 +1,5 @@
+---
+title: shadcn
+avatar: /images/avatars/shadcn.png
+twitter: shadcn
+---
diff --git a/apps/www/src/content/blog/how-propwrite-makes-listings-irresistible.mdx b/apps/www/src/content/blog/how-propwrite-makes-listings-irresistible.mdx
new file mode 100644
index 0000000..4444fbe
--- /dev/null
+++ b/apps/www/src/content/blog/how-propwrite-makes-listings-irresistible.mdx
@@ -0,0 +1,41 @@
+---
+title: "AI in Real Estate: How Propwrite Makes Listings Irresistible"
+description: Explore the transformative AI features of Propwrite that elevate real estate listings to new heights.
+image: /images/blog/blog-post-3.jpg
+date: "2023-11-23"
+authors:
+ - codehagen
+---
+
+
+ Discover the magic behind Propwrite's AI and how it turns ordinary listings
+ into captivating stories for potential buyers.
+
+
+## Unveiling the Power of AI in Real Estate
+
+Propwrite's AI technology is redefining real estate listings, making them more than just a collection of features and photos.
+
+### AI-Enhanced Property Descriptions
+
+Our AI analyzes and enhances property details, weaving them into engaging narratives that resonate with buyers.
+
+#### Crafting the Perfect Narrative
+
+- **Data-Driven Storytelling:** Our AI uses data points to create stories that highlight the unique aspects of each property.
+- **Tailored to Market Trends:** It dynamically adjusts to current market demands, ensuring your listing stands out.
+- **Buyer-Centric Approach:** The AI crafts descriptions that appeal to the right audience, maximizing interest and engagement.
+
+##### Propwrite's AI at Work
+
+Here's a glimpse of how our AI transforms various aspects of a listing:
+
+| Aspect | AI Enhancement |
+| ----------------- | ------------------------------------------------ |
+| Property Features | Converts basic details into compelling stories |
+| Market Insights | Adapts descriptions to current market trends |
+| Buyer Preferences | Personalizes listings to attract the ideal buyer |
+
+Join the revolution in real estate with Propwrite. Embrace the future where AI drives success in every listing.
+
+For more insights or to join our community, reach out at [support@propwrite.com](mailto:support@propwrite.com) or connect with us on Discord [here](https://discord.gg/wadg6fNX).
diff --git a/apps/www/src/content/blog/propwrite_aI_real_estate_blog_post.mdx b/apps/www/src/content/blog/propwrite_aI_real_estate_blog_post.mdx
new file mode 100644
index 0000000..e349109
--- /dev/null
+++ b/apps/www/src/content/blog/propwrite_aI_real_estate_blog_post.mdx
@@ -0,0 +1,37 @@
+---
+title: "Boost Your Real Estate Business with Propwrite: The AI Advantage"
+description: Discover how Propwrite leverages AI to revolutionize real estate, offering unparalleled efficiency and market insights.
+image: /images/blog/blog-post-4.jpg
+date: "2023-11-29"
+authors:
+ - codehagen
+---
+
+
+ Explore the transformative power of AI in real estate with Propwrite and see
+ how it can elevate your business to new heights.
+
+
+## The AI Revolution in Real Estate
+
+The real estate market is experiencing a seismic shift, thanks to advancements in AI technology. Propwrite is at the forefront of this revolution, offering cutting-edge solutions to modernize and enhance real estate operations.
+
+### Transforming Listings with AI
+
+With Propwrite, real estate listings are no longer just a set of images and descriptions. They are transformed into engaging narratives, each crafted to highlight the unique appeal of a property, thanks to our advanced AI algorithms.
+
+#### Leveraging AI for Market Insights
+
+- **Advanced Data Analysis:** Propwrite's AI dives deep into market data, providing valuable insights that can inform your strategy and help you stay ahead of the curve.
+- **Trend Forecasting:** Our AI tools are designed to identify and adapt to emerging market trends, ensuring your listings are always relevant and appealing.
+- **Efficient Operations:** AI streamlines various aspects of real estate operations, from client communications to scheduling, increasing overall efficiency.
+
+##### Propwrite: A Game-Changer for Real Estate Professionals
+
+Propwrite's AI-driven platform is more than just a tool; it's a game-changer for real estate professionals. By automating mundane tasks and offering deep market insights, Propwrite enables agents to focus on what they do best โ selling properties.
+
+###### Connect with Propwrite Today
+
+Embrace the future of real estate with Propwrite. Join a growing community of professionals who are leveraging AI to transform their businesses.
+
+For more information or to join our community, contact us at [support@propwrite.com](mailto:support@propwrite.com) or connect on our Discord [here](https://discord.gg/wadg6fNX).
diff --git a/apps/www/src/content/blog/welcome-to-propwrite.mdx b/apps/www/src/content/blog/welcome-to-propwrite.mdx
new file mode 100644
index 0000000..775720a
--- /dev/null
+++ b/apps/www/src/content/blog/welcome-to-propwrite.mdx
@@ -0,0 +1,81 @@
+---
+title: Welcome to Propwrite
+description: Explore how Propwrite's AI is transforming real estate by enhancing listings and operations.
+image: /images/blog/blog-post-2.jpg
+date: "2023-11-22"
+authors:
+ - codehagen
+---
+
+
+ Christer is a real estate agent with a passion for coding. That's why he
+ created Propwrite - to make every real estate agent's job easier by letting AI
+ handle the heavy lifting of property listings.
+
+
+Welcome to Propwrite, where AI meets real estate in an innovative blend thatโs transforming the industry.
+
+## Why AI in Real Estate?
+
+AI is reshaping real estate by bringing a new level of efficiency and insight. Itโs not just about automation; itโs about elevating the entire buying and selling experience.
+
+- AI doesnโt just process data; it uncovers opportunities.
+- Think of it as a market whisperer, always staying ahead of trends.
+- In short: Listings that not only list but also glisten.
+
+### Making Listings Stand Out with Propwrite
+
+Propwrite's AI-driven platform is more than just a tool; it's your partner in crafting listings that catch eyes and capture interest. With our AI, each property description becomes a compelling narrative, drawing potential buyers in from the first word.
+
+> "Our AI is like a real estate poet, creating listings that are not just informative but also inspiring," says Christer, the brain behind Propwrite.
+
+#### Streamlining Operations
+
+Propwrite goes beyond listings. Itโs about orchestrating the entire real estate operation seamlessly. From scheduling showings to managing client relationships, our AI is your all-in-one solution for a more organized, efficient, and effective real estate business.
+
+##### Connect with Us and Join the Community
+
+The future of real estate is here with Propwrite. We're not just building a product; we're cultivating a community. Join us on this exciting journey to reshape the world of real estate.
+
+Interested in more insights and networking with like-minded professionals? Join our Discord community [here](---
+title: Welcome to Propwrite
+description: Explore how Propwrite's AI is transforming real estate by enhancing listings and operations.
+image: /images/blog/blog-post-2.jpg
+date: "2023-11-11"
+authors:
+
+- codehagen
+
+---
+
+
+ Christer is a real estate agent with a passion for coding. That's why he
+ created Propwrite - to make every real estate agent's job easier by letting AI
+ handle the heavy lifting of property listings.
+
+
+Welcome to Propwrite, where AI meets real estate in an innovative blend thatโs transforming the industry.
+
+## Why AI in Real Estate?
+
+AI is reshaping real estate by bringing a new level of efficiency and insight. Itโs not just about automation; itโs about elevating the entire buying and selling experience.
+
+- AI doesnโt just process data; it uncovers opportunities.
+- Think of it as a market whisperer, always staying ahead of trends.
+- In short: Listings that not only list but also glisten.
+
+### Making Listings Stand Out with Propwrite
+
+Propwrite's AI-driven platform is more than just a tool; it's your partner in crafting listings that catch eyes and capture interest. With our AI, each property description becomes a compelling narrative, drawing potential buyers in from the first word.
+
+> "Our AI is like a real estate poet, creating listings that are not just informative but also inspiring," says Christer, the brain behind Propwrite.
+
+#### Streamlining Operations
+
+PPropwrite isn't just revolutionizing listings; it's redefining the entire workflow of real estate operations. Our platform transforms the cumbersome tasks of managing a real estate business into a streamlined, intuitive process.
+
+##### Connect with Us and Join the Community
+
+The future of real estate is here with Propwrite. We're not just building a product; we're cultivating a community. Join us on this exciting journey to reshape the world of real estate.
+
+Interested in more insights and networking with like-minded professionals? Join our Discord community [here](https://discord.gg/wadg6fNX) and be a part of the real estate revolution.
diff --git a/apps/www/src/content/docs/documentation/code-blocks.mdx b/apps/www/src/content/docs/documentation/code-blocks.mdx
new file mode 100644
index 0000000..1bbe5a8
--- /dev/null
+++ b/apps/www/src/content/docs/documentation/code-blocks.mdx
@@ -0,0 +1,73 @@
+---
+title: Code Blocks
+description: Advanced code blocks with highlighting, file names and more.
+---
+
+The code blocks on the documentation site and the blog are powered by [rehype-pretty-code](https://github.com/atomiks/rehype-pretty-code). The syntax highlighting is done using [shiki](https://github.com/shikijs/shiki).
+
+It has the following features:
+
+1. Beautiful code blocks with syntax highlighting.
+2. Support for VS Code themes.
+3. Works with hundreds of languages.
+4. Line and word highlighting.
+5. Support for line numbers.
+6. Show code block titles using meta strings.
+
+
+
+Thanks to Shiki, highlighting is done at build time. No JavaScript is sent to the client for runtime highlighting.
+
+
+
+## Example
+
+```ts showLineNumbers title="next.config.js" {3} /appDir: true/
+import { withContentlayer } from "next-contentlayer";
+
+/** @type {import('next').NextConfig} */
+const nextConfig = {
+ reactStrictMode: true,
+ images: {
+ domains: ["avatars.githubusercontent.com"],
+ },
+ experimental: {
+ appDir: true,
+ serverComponentsExternalPackages: ["@prisma/client"],
+ },
+};
+
+export default withContentlayer(nextConfig);
+```
+
+## Title
+
+````mdx
+```ts title="path/to/file.ts"
+// Code here
+```
+````
+
+## Line Highlight
+
+````mdx
+```ts {1,3-6}
+// Highlight line 1 and line 3 to 6
+```
+````
+
+## Word Highlight
+
+````mdx
+```ts /shadcn/
+// Highlight the word shadcn.
+```
+````
+
+## Line Numbers
+
+````mdx
+```ts showLineNumbers
+// This will show line numbers.
+```
+````
diff --git a/apps/www/src/content/docs/documentation/components.mdx b/apps/www/src/content/docs/documentation/components.mdx
new file mode 100644
index 0000000..f56dbed
--- /dev/null
+++ b/apps/www/src/content/docs/documentation/components.mdx
@@ -0,0 +1,157 @@
+---
+title: Components
+description: Use React components in Markdown using MDX.
+---
+
+The following components are available out of the box for use in Markdown.
+
+If you'd like to build and add your own custom components, see the [Custom Components](#custom-components) section below.
+
+## Built-in Components
+
+### 1. Callout
+
+```mdx
+
+
+This is a default callout. You can embed **Markdown** inside a `callout`.
+
+
+```
+
+
+
+This is a default callout. You can embed **Markdown** inside a `callout`.
+
+
+
+
+
+This is a warning callout. It uses the props `type="warning"`.
+
+
+
+
+
+This is a danger callout. It uses the props `type="danger"`.
+
+
+
+### 2. Card
+
+```mdx
+
+
+#### Heading
+
+You can use **markdown** inside cards.
+
+
+```
+
+
+
+#### Heading
+
+You can use **markdown** inside cards.
+
+
+
+You can also use HTML to embed cards in a grid.
+
+```mdx
+
+
+ #### Card One
+ You can use **markdown** inside cards.
+
+
+
+ #### Card Two
+ You can also use `inline code` and code blocks.
+
+
+```
+
+
+
+ #### Card One
+ You can use **markdown** inside cards.
+
+
+
+ #### Card Two
+ You can also use `inline code` and code blocks.
+
+
+
+---
+
+## Custom Components
+
+You can add your own custom components using the `components` props from `useMDXComponent`.
+
+```ts title="components/mdx.tsx" {2,6}
+import { Callout } from "@/components/callout"
+import { CustomComponent } from "@/components/custom"
+
+const components = {
+ Callout,
+ CustomComponent,
+}
+
+export function Mdx({ code }) {
+ const Component = useMDXComponent(code)
+
+ return (
+
+
+
+ )
+}
+```
+
+Once you've added your custom component, you can use it in MDX as follows:
+
+```js
+
+```
+
+---
+
+## HTML Elements
+
+You can overwrite HTML elements using the same technique above.
+
+```ts {4}
+const components = {
+ Callout,
+ CustomComponent,
+ hr: ({ ...props }) => ,
+}
+```
+
+This will overwrite the `` tag or `---` in Mardown with the HTML output above.
+
+---
+
+## Styling
+
+Tailwind CSS classes can be used inside MDX for styling.
+
+```mdx
+
This text will be red.
+```
+
+Make sure you have configured the path to your content in your `tailwind.config.js` file:
+
+```js title="tailwind.config.js" {6}
+/** @type {import('tailwindcss').Config} */
+module.exports = {
+ content: [
+ "./app/**/*.{ts,tsx}",
+ "./components/**/*.{ts,tsx}",
+ "./content/**/*.{md,mdx}",
+ ],
+};
+```
diff --git a/apps/www/src/content/docs/documentation/index.mdx b/apps/www/src/content/docs/documentation/index.mdx
new file mode 100644
index 0000000..c3e6b1d
--- /dev/null
+++ b/apps/www/src/content/docs/documentation/index.mdx
@@ -0,0 +1,60 @@
+---
+title: Documentation
+description: Build your documentation site using Contentlayer and MDX.
+---
+
+Taxonomy includes a documentation site built using [Contentlayer](https://contentlayer.dev) and [MDX](http://mdxjs.com).
+
+## Features
+
+It comes with the following features out of the box:
+
+1. Write content using MDX.
+2. Transform and validate content using Contentlayer.
+3. MDX components such as `` and ``.
+4. Support for table of contents.
+5. Custom navigation with prev and next pager.
+6. Beautiful code blocks using `rehype-pretty-code`.
+7. Syntax highlighting using `shiki`.
+8. Built-in search (_in progress_).
+9. Dark mode (_in progress_).
+
+## How is it built
+
+Click on a section below to learn how the documentation site built.
+
+
+
+
+
+### Contentlayer
+
+Learn how to use MDX with Contentlayer.
+
+
+
+
+
+### Components
+
+Using React components in Mardown.
+
+
+
+
+
+### Code Blocks
+
+Beautiful code blocks with syntax highlighting.
+
+
+
+
+
+### Style Guide
+
+View a sample page with all the styles.
+
+
+
+
diff --git a/apps/www/src/content/docs/documentation/style-guide.mdx b/apps/www/src/content/docs/documentation/style-guide.mdx
new file mode 100644
index 0000000..830af07
--- /dev/null
+++ b/apps/www/src/content/docs/documentation/style-guide.mdx
@@ -0,0 +1,216 @@
+---
+title: Style Guide
+description: Testing the MDX style guide with Tailwind Typography
+---
+
+
+
+- The text below is from the [Tailwind CSS](https://play.tailwindcss.com/uj1vGACRJA?layout=preview) docs. I copied it here to test the markdown styles. **Tailwind is awesome. You should use it.**
+- The CSS is from MDX sites I've built through the years. I copied this from [Nextra](https://github.com/shuding/nextra) and tweaked it a bit to fit the styles of this site.
+
+
+
+Until now, trying to style an article, document, or blog post with Tailwind has been a tedious task that required a keen eye for typography and a lot of complex custom CSS.
+
+By default, Tailwind removes all of the default browser styling from paragraphs, headings, lists and more. This ends up being really useful for building application UIs because you spend less time undoing user-agent styles, but when you _really are_ just trying to style some content that came from a rich-text editor in a CMS or a markdown file, it can be surprising and unintuitive.
+
+We get lots of complaints about it actually, with people regularly asking us things like:
+
+> Why is Tailwind removing the default styles on my `h1` elements? How do I disable this? What do you mean I lose all the other base styles too?
+> We hear you, but we're not convinced that simply disabling our base styles is what you really want. You don't want to have to remove annoying margins every time you use a `p` element in a piece of your dashboard UI. And I doubt you really want your blog posts to use the user-agent styles either โ you want them to look _awesome_, not awful.
+
+The `@tailwindcss/typography` plugin is our attempt to give you what you _actually_ want, without any of the downsides of doing something stupid like disabling our base styles.
+
+It adds a new `prose` class that you can slap on any block of vanilla HTML content and turn it into a beautiful, well-formatted document:
+
+```html
+
+
Garlic bread with cheese: What the science tells us
+
+ For years parents have espoused the health benefits of eating garlic bread
+ with cheese to their children, with the food earning such an iconic status
+ in our culture that kids will often dress up as warm, cheesy loaf for
+ Halloween.
+
+
+ But a recent study shows that the celebrated appetizer may be linked to a
+ series of rabies cases springing up around the country.
+
+
+```
+
+For more information about how to use the plugin and the features it includes, [read the documentation](https://github.com/tailwindcss/typography/blob/master/README.md).
+
+---
+
+## What to expect from here on out
+
+What follows from here is just a bunch of absolute nonsense I've written to dogfood the plugin itself. It includes every sensible typographic element I could think of, like **bold text**, unordered lists, ordered lists, code blocks, block quotes, _and even italics_.
+
+It's important to cover all of these use cases for a few reasons:
+
+1. We want everything to look good out of the box.
+2. Really just the first reason, that's the whole point of the plugin.
+3. Here's a third pretend reason though a list with three items looks more realistic than a list with two items.
+
+Now we're going to try out another header style.
+
+### Typography should be easy
+
+So that's a header for you โ with any luck if we've done our job correctly that will look pretty reasonable.
+
+Something a wise person once told me about typography is:
+
+> Typography is pretty important if you don't want your stuff to look like trash. Make it good then it won't be bad.
+
+It's probably important that images look okay here by default as well:
+
+
+
+Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots in a piece of classical Latin literature from 45 BC, making it over 2000 years old.
+
+Now I'm going to show you an example of an unordered list to make sure that looks good, too:
+
+- So here is the first item in this list.
+- In this example we're keeping the items short.
+- Later, we'll use longer, more complex list items.
+
+And that's the end of this section.
+
+## What if we stack headings?
+
+### We should make sure that looks good, too.
+
+Sometimes you have headings directly underneath each other. In those cases you often have to undo the top margin on the second heading because it usually looks better for the headings to be closer together than a paragraph followed by a heading should be.
+
+### When a heading comes after a paragraph โฆ
+
+When a heading comes after a paragraph, we need a bit more space, like I already mentioned above. Now let's see what a more complex list would look like.
+
+- **I often do this thing where list items have headings.**
+
+ For some reason I think this looks cool which is unfortunate because it's pretty annoying to get the styles right.
+
+ I often have two or three paragraphs in these list items, too, so the hard part is getting the spacing between the paragraphs, list item heading, and separate list items to all make sense. Pretty tough honestly, you could make a strong argument that you just shouldn't write this way.
+
+- **Since this is a list, I need at least two items.**
+
+ I explained what I'm doing already in the previous list item, but a list wouldn't be a list if it only had one item, and we really want this to look realistic. That's why I've added this second list item so I actually have something to look at when writing the styles.
+
+- **It's not a bad idea to add a third item either.**
+
+ I think it probably would've been fine to just use two items but three is definitely not worse, and since I seem to be having no trouble making up arbitrary things to type, I might as well include it.
+
+After this sort of list I usually have a closing statement or paragraph, because it kinda looks weird jumping right to a heading.
+
+## Code should look okay by default.
+
+I think most people are going to use [highlight.js](https://highlightjs.org/) or [Prism](https://prismjs.com/) or something if they want to style their code blocks but it wouldn't hurt to make them look _okay_ out of the box, even with no syntax highlighting.
+
+Here's what a default `tailwind.config.js` file looks like at the time of writing:
+
+```js
+module.exports = {
+ purge: [],
+ theme: {
+ extend: {},
+ },
+ variants: {},
+ plugins: [],
+};
+```
+
+Hopefully that looks good enough to you.
+
+### What about nested lists?
+
+Nested lists basically always look bad which is why editors like Medium don't even let you do it, but I guess since some of you goofballs are going to do it we have to carry the burden of at least making it work.
+
+1. **Nested lists are rarely a good idea.**
+ - You might feel like you are being really "organized" or something but you are just creating a gross shape on the screen that is hard to read.
+ - Nested navigation in UIs is a bad idea too, keep things as flat as possible.
+ - Nesting tons of folders in your source code is also not helpful.
+2. **Since we need to have more items, here's another one.**
+ - I'm not sure if we'll bother styling more than two levels deep.
+ - Two is already too much, three is guaranteed to be a bad idea.
+ - If you nest four levels deep you belong in prison.
+3. **Two items isn't really a list, three is good though.**
+ - Again please don't nest lists if you want people to actually read your content.
+ - Nobody wants to look at this.
+ - I'm upset that we even have to bother styling this.
+
+The most annoying thing about lists in Markdown is that `
` elements aren't given a child `
` tag unless there are multiple paragraphs in the list item. That means I have to worry about styling that annoying situation too.
+
+- **For example, here's another nested list.**
+
+ But this time with a second paragraph.
+
+ - These list items won't have `
` tags
+ - Because they are only one line each
+
+- **But in this second top-level list item, they will.**
+
+ This is especially annoying because of the spacing on this paragraph.
+
+ - As you can see here, because I've added a second line, this list item now has a `
` tag.
+
+ This is the second line I'm talking about by the way.
+
+ - Finally here's another list item so it's more like a list.
+
+- A closing list item, but with no nested list, because why not?
+
+And finally a sentence to close off this section.
+
+## There are other elements we need to style
+
+I almost forgot to mention links, like [this link to the Tailwind CSS website](https://tailwindcss.com). We almost made them blue but that's so yesterday, so we went with dark gray, feels edgier.
+
+We even included table styles, check it out:
+
+| Wrestler | Origin | Finisher |
+| ----------------------- | ------------ | ------------------ |
+| Bret "The Hitman" Hart | Calgary, AB | Sharpshooter |
+| Stone Cold Steve Austin | Austin, TX | Stone Cold Stunner |
+| Randy Savage | Sarasota, FL | Elbow Drop |
+| Vader | Boulder, CO | Vader Bomb |
+| Razor Ramon | Chuluota, FL | Razor's Edge |
+
+We also need to make sure inline code looks good, like if I wanted to talk about `` elements or tell you the good news about `@tailwindcss/typography`.
+
+### Sometimes I even use `code` in headings
+
+Even though it's probably a bad idea, and historically I've had a hard time making it look good. This _"wrap the code blocks in backticks"_ trick works pretty well though really.
+
+Another thing I've done in the past is put a `code` tag inside of a link, like if I wanted to tell you about the [`tailwindcss/docs`](https://github.com/tailwindcss/docs) repository. I don't love that there is an underline below the backticks but it is absolutely not worth the madness it would require to avoid it.
+
+#### We haven't used an `h4` yet
+
+But now we have. Please don't use `h5` or `h6` in your content, Medium only supports two heading levels for a reason, you animals. I honestly considered using a `before` pseudo-element to scream at you if you use an `h5` or `h6`.
+
+We don't style them at all out of the box because `h4` elements are already so small that they are the same size as the body copy. What are we supposed to do with an `h5`, make it _smaller_ than the body copy? No thanks.
+
+### We still need to think about stacked headings though.
+
+#### Let's make sure we don't screw that up with `h4` elements, either.
+
+Phew, with any luck we have styled the headings above this text and they look pretty good.
+
+Let's add a closing paragraph here so things end with a decently sized block of text. I can't explain why I want things to end that way but I have to assume it's because I think things will look weird or unbalanced if there is a heading too close to the end of the document.
+
+What I've written here is probably long enough, but adding this final sentence can't hurt.
+
+## GitHub Flavored Markdown
+
+I've also added support for GitHub Flavored Mardown using `remark-gfm`.
+
+With `remark-gfm`, we get a few extra features in our markdown. Example: autolink literals.
+
+A link like www.example.com or https://example.com would automatically be converted into an `a` tag.
+
+This works for email links too: contact@example.com.
diff --git a/apps/www/src/content/docs/in-progress.mdx b/apps/www/src/content/docs/in-progress.mdx
new file mode 100644
index 0000000..c48c938
--- /dev/null
+++ b/apps/www/src/content/docs/in-progress.mdx
@@ -0,0 +1,10 @@
+---
+title: Not Implemented
+description: This page is in progress.
+---
+
+
+
+This site is a work in progress. If you see dummy text on a page, it means I'm still working on it. You can follow updates on Twitter [@shadcn](https://twitter.com/shadcn).
+
+
diff --git a/apps/www/src/content/docs/index.mdx b/apps/www/src/content/docs/index.mdx
new file mode 100644
index 0000000..8f12d68
--- /dev/null
+++ b/apps/www/src/content/docs/index.mdx
@@ -0,0 +1,54 @@
+---
+title: Documentation
+description: Welcome to the Taxonomy documentation.
+---
+
+This is the documentation for the Taxonomy site.
+
+This is an example of a doc site built using [ContentLayer](/docs/documentation/contentlayer) and MDX.
+
+
+
+This site is a work in progress. If you see dummy text on a page, it means I'm still working on it. You can follow updates on Twitter [@shadcn](https://twitter.com/shadcn).
+
+
+
+## Features
+
+Select a feature below to learn more about it.
+
+
+
+
+
+### Documentation
+
+This documentation site built using Contentlayer.
+
+
+
+
+
+### Marketing
+
+The marketing site with landing pages.
+
+
+
+
+
+### App
+
+The dashboard with auth and subscriptions.
+
+
+
+
+
+### Blog
+
+The blog built using Contentlayer and MDX.
+
+
+
+
diff --git a/apps/www/src/content/guides/build-blog-using-contentlayer-mdx.mdx b/apps/www/src/content/guides/build-blog-using-contentlayer-mdx.mdx
new file mode 100644
index 0000000..d9c0bc5
--- /dev/null
+++ b/apps/www/src/content/guides/build-blog-using-contentlayer-mdx.mdx
@@ -0,0 +1,222 @@
+---
+title: Build a blog using ContentLayer and MDX.
+description: Learn how to use ContentLayer to build a blog with Next.js
+date: 2022-11-18
+---
+
+
+
+This site is a work in progress. If you see dummy text on a page, it means I'm still working on it. You can follow updates on Twitter [@shadcn](https://twitter.com/shadcn).
+
+
+
+
+ The text below is from the [Tailwind
+ CSS](https://play.tailwindcss.com/uj1vGACRJA?layout=preview) docs. I copied it
+ here to test the markdown styles. **Tailwind is awesome. You should use it.**
+
+
+Until now, trying to style an article, document, or blog post with Tailwind has been a tedious task that required a keen eye for typography and a lot of complex custom CSS.
+
+By default, Tailwind removes all of the default browser styling from paragraphs, headings, lists and more. This ends up being really useful for building application UIs because you spend less time undoing user-agent styles, but when you _really are_ just trying to style some content that came from a rich-text editor in a CMS or a markdown file, it can be surprising and unintuitive.
+
+We get lots of complaints about it actually, with people regularly asking us things like:
+
+> Why is Tailwind removing the default styles on my `h1` elements? How do I disable this? What do you mean I lose all the other base styles too?
+> We hear you, but we're not convinced that simply disabling our base styles is what you really want. You don't want to have to remove annoying margins every time you use a `p` element in a piece of your dashboard UI. And I doubt you really want your blog posts to use the user-agent styles either โ you want them to look _awesome_, not awful.
+
+The `@tailwindcss/typography` plugin is our attempt to give you what you _actually_ want, without any of the downsides of doing something stupid like disabling our base styles.
+
+It adds a new `prose` class that you can slap on any block of vanilla HTML content and turn it into a beautiful, well-formatted document:
+
+```html
+
+
Garlic bread with cheese: What the science tells us
+
+ For years parents have espoused the health benefits of eating garlic bread
+ with cheese to their children, with the food earning such an iconic status
+ in our culture that kids will often dress up as warm, cheesy loaf for
+ Halloween.
+
+
+ But a recent study shows that the celebrated appetizer may be linked to a
+ series of rabies cases springing up around the country.
+
+
+```
+
+For more information about how to use the plugin and the features it includes, [read the documentation](https://github.com/tailwindcss/typography/blob/master/README.md).
+
+---
+
+## What to expect from here on out
+
+What follows from here is just a bunch of absolute nonsense I've written to dogfood the plugin itself. It includes every sensible typographic element I could think of, like **bold text**, unordered lists, ordered lists, code blocks, block quotes, _and even italics_.
+
+It's important to cover all of these use cases for a few reasons:
+
+1. We want everything to look good out of the box.
+2. Really just the first reason, that's the whole point of the plugin.
+3. Here's a third pretend reason though a list with three items looks more realistic than a list with two items.
+
+Now we're going to try out another header style.
+
+### Typography should be easy
+
+So that's a header for you โ with any luck if we've done our job correctly that will look pretty reasonable.
+
+Something a wise person once told me about typography is:
+
+> Typography is pretty important if you don't want your stuff to look like trash. Make it good then it won't be bad.
+
+It's probably important that images look okay here by default as well:
+
+
+
+Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots in a piece of classical Latin literature from 45 BC, making it over 2000 years old.
+
+Now I'm going to show you an example of an unordered list to make sure that looks good, too:
+
+- So here is the first item in this list.
+- In this example we're keeping the items short.
+- Later, we'll use longer, more complex list items.
+
+And that's the end of this section.
+
+## What if we stack headings?
+
+### We should make sure that looks good, too.
+
+Sometimes you have headings directly underneath each other. In those cases you often have to undo the top margin on the second heading because it usually looks better for the headings to be closer together than a paragraph followed by a heading should be.
+
+### When a heading comes after a paragraph โฆ
+
+When a heading comes after a paragraph, we need a bit more space, like I already mentioned above. Now let's see what a more complex list would look like.
+
+- **I often do this thing where list items have headings.**
+
+ For some reason I think this looks cool which is unfortunate because it's pretty annoying to get the styles right.
+
+ I often have two or three paragraphs in these list items, too, so the hard part is getting the spacing between the paragraphs, list item heading, and separate list items to all make sense. Pretty tough honestly, you could make a strong argument that you just shouldn't write this way.
+
+- **Since this is a list, I need at least two items.**
+
+ I explained what I'm doing already in the previous list item, but a list wouldn't be a list if it only had one item, and we really want this to look realistic. That's why I've added this second list item so I actually have something to look at when writing the styles.
+
+- **It's not a bad idea to add a third item either.**
+
+ I think it probably would've been fine to just use two items but three is definitely not worse, and since I seem to be having no trouble making up arbitrary things to type, I might as well include it.
+
+After this sort of list I usually have a closing statement or paragraph, because it kinda looks weird jumping right to a heading.
+
+## Code should look okay by default.
+
+I think most people are going to use [highlight.js](https://highlightjs.org/) or [Prism](https://prismjs.com/) or something if they want to style their code blocks but it wouldn't hurt to make them look _okay_ out of the box, even with no syntax highlighting.
+
+Here's what a default `tailwind.config.js` file looks like at the time of writing:
+
+```js
+module.exports = {
+ purge: [],
+ theme: {
+ extend: {},
+ },
+ variants: {},
+ plugins: [],
+};
+```
+
+Hopefully that looks good enough to you.
+
+### What about nested lists?
+
+Nested lists basically always look bad which is why editors like Medium don't even let you do it, but I guess since some of you goofballs are going to do it we have to carry the burden of at least making it work.
+
+1. **Nested lists are rarely a good idea.**
+ - You might feel like you are being really "organized" or something but you are just creating a gross shape on the screen that is hard to read.
+ - Nested navigation in UIs is a bad idea too, keep things as flat as possible.
+ - Nesting tons of folders in your source code is also not helpful.
+2. **Since we need to have more items, here's another one.**
+ - I'm not sure if we'll bother styling more than two levels deep.
+ - Two is already too much, three is guaranteed to be a bad idea.
+ - If you nest four levels deep you belong in prison.
+3. **Two items isn't really a list, three is good though.**
+ - Again please don't nest lists if you want people to actually read your content.
+ - Nobody wants to look at this.
+ - I'm upset that we even have to bother styling this.
+
+The most annoying thing about lists in Markdown is that `
` elements aren't given a child `
` tag unless there are multiple paragraphs in the list item. That means I have to worry about styling that annoying situation too.
+
+- **For example, here's another nested list.**
+
+ But this time with a second paragraph.
+
+ - These list items won't have `
` tags
+ - Because they are only one line each
+
+- **But in this second top-level list item, they will.**
+
+ This is especially annoying because of the spacing on this paragraph.
+
+ - As you can see here, because I've added a second line, this list item now has a `
` tag.
+
+ This is the second line I'm talking about by the way.
+
+ - Finally here's another list item so it's more like a list.
+
+- A closing list item, but with no nested list, because why not?
+
+And finally a sentence to close off this section.
+
+## There are other elements we need to style
+
+I almost forgot to mention links, like [this link to the Tailwind CSS website](https://tailwindcss.com). We almost made them blue but that's so yesterday, so we went with dark gray, feels edgier.
+
+We even included table styles, check it out:
+
+| Wrestler | Origin | Finisher |
+| ----------------------- | ------------ | ------------------ |
+| Bret "The Hitman" Hart | Calgary, AB | Sharpshooter |
+| Stone Cold Steve Austin | Austin, TX | Stone Cold Stunner |
+| Randy Savage | Sarasota, FL | Elbow Drop |
+| Vader | Boulder, CO | Vader Bomb |
+| Razor Ramon | Chuluota, FL | Razor's Edge |
+
+We also need to make sure inline code looks good, like if I wanted to talk about `` elements or tell you the good news about `@tailwindcss/typography`.
+
+### Sometimes I even use `code` in headings
+
+Even though it's probably a bad idea, and historically I've had a hard time making it look good. This _"wrap the code blocks in backticks"_ trick works pretty well though really.
+
+Another thing I've done in the past is put a `code` tag inside of a link, like if I wanted to tell you about the [`tailwindcss/docs`](https://github.com/tailwindcss/docs) repository. I don't love that there is an underline below the backticks but it is absolutely not worth the madness it would require to avoid it.
+
+#### We haven't used an `h4` yet
+
+But now we have. Please don't use `h5` or `h6` in your content, Medium only supports two heading levels for a reason, you animals. I honestly considered using a `before` pseudo-element to scream at you if you use an `h5` or `h6`.
+
+We don't style them at all out of the box because `h4` elements are already so small that they are the same size as the body copy. What are we supposed to do with an `h5`, make it _smaller_ than the body copy? No thanks.
+
+### We still need to think about stacked headings though.
+
+#### Let's make sure we don't screw that up with `h4` elements, either.
+
+Phew, with any luck we have styled the headings above this text and they look pretty good.
+
+Let's add a closing paragraph here so things end with a decently sized block of text. I can't explain why I want things to end that way but I have to assume it's because I think things will look weird or unbalanced if there is a heading too close to the end of the document.
+
+What I've written here is probably long enough, but adding this final sentence can't hurt.
+
+## GitHub Flavored Markdown
+
+I've also added support for GitHub Flavored Mardown using `remark-gfm`.
+
+With `remark-gfm`, we get a few extra features in our markdown. Example: autolink literals.
+
+A link like www.example.com or https://example.com would automatically be converted into an `a` tag.
+
+This works for email links too: contact@example.com.
diff --git a/apps/www/src/content/guides/using-next-auth-next-13.mdx b/apps/www/src/content/guides/using-next-auth-next-13.mdx
new file mode 100644
index 0000000..956776d
--- /dev/null
+++ b/apps/www/src/content/guides/using-next-auth-next-13.mdx
@@ -0,0 +1,222 @@
+---
+title: Using NextAuth.js with Next.13
+description: How to use NextAuth.js in server components.
+date: 2022-11-23
+---
+
+
+
+This site is a work in progress. If you see dummy text on a page, it means I'm still working on it. You can follow updates on Twitter [@shadcn](https://twitter.com/shadcn).
+
+
+
+
+ The text below is from the [Tailwind
+ CSS](https://play.tailwindcss.com/uj1vGACRJA?layout=preview) docs. I copied it
+ here to test the markdown styles. **Tailwind is awesome. You should use it.**
+
+
+Until now, trying to style an article, document, or blog post with Tailwind has been a tedious task that required a keen eye for typography and a lot of complex custom CSS.
+
+By default, Tailwind removes all of the default browser styling from paragraphs, headings, lists and more. This ends up being really useful for building application UIs because you spend less time undoing user-agent styles, but when you _really are_ just trying to style some content that came from a rich-text editor in a CMS or a markdown file, it can be surprising and unintuitive.
+
+We get lots of complaints about it actually, with people regularly asking us things like:
+
+> Why is Tailwind removing the default styles on my `h1` elements? How do I disable this? What do you mean I lose all the other base styles too?
+> We hear you, but we're not convinced that simply disabling our base styles is what you really want. You don't want to have to remove annoying margins every time you use a `p` element in a piece of your dashboard UI. And I doubt you really want your blog posts to use the user-agent styles either โ you want them to look _awesome_, not awful.
+
+The `@tailwindcss/typography` plugin is our attempt to give you what you _actually_ want, without any of the downsides of doing something stupid like disabling our base styles.
+
+It adds a new `prose` class that you can slap on any block of vanilla HTML content and turn it into a beautiful, well-formatted document:
+
+```html
+
+
Garlic bread with cheese: What the science tells us
+
+ For years parents have espoused the health benefits of eating garlic bread
+ with cheese to their children, with the food earning such an iconic status
+ in our culture that kids will often dress up as warm, cheesy loaf for
+ Halloween.
+
+
+ But a recent study shows that the celebrated appetizer may be linked to a
+ series of rabies cases springing up around the country.
+
+
+```
+
+For more information about how to use the plugin and the features it includes, [read the documentation](https://github.com/tailwindcss/typography/blob/master/README.md).
+
+---
+
+## What to expect from here on out
+
+What follows from here is just a bunch of absolute nonsense I've written to dogfood the plugin itself. It includes every sensible typographic element I could think of, like **bold text**, unordered lists, ordered lists, code blocks, block quotes, _and even italics_.
+
+It's important to cover all of these use cases for a few reasons:
+
+1. We want everything to look good out of the box.
+2. Really just the first reason, that's the whole point of the plugin.
+3. Here's a third pretend reason though a list with three items looks more realistic than a list with two items.
+
+Now we're going to try out another header style.
+
+### Typography should be easy
+
+So that's a header for you โ with any luck if we've done our job correctly that will look pretty reasonable.
+
+Something a wise person once told me about typography is:
+
+> Typography is pretty important if you don't want your stuff to look like trash. Make it good then it won't be bad.
+
+It's probably important that images look okay here by default as well:
+
+
+
+Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots in a piece of classical Latin literature from 45 BC, making it over 2000 years old.
+
+Now I'm going to show you an example of an unordered list to make sure that looks good, too:
+
+- So here is the first item in this list.
+- In this example we're keeping the items short.
+- Later, we'll use longer, more complex list items.
+
+And that's the end of this section.
+
+## What if we stack headings?
+
+### We should make sure that looks good, too.
+
+Sometimes you have headings directly underneath each other. In those cases you often have to undo the top margin on the second heading because it usually looks better for the headings to be closer together than a paragraph followed by a heading should be.
+
+### When a heading comes after a paragraph โฆ
+
+When a heading comes after a paragraph, we need a bit more space, like I already mentioned above. Now let's see what a more complex list would look like.
+
+- **I often do this thing where list items have headings.**
+
+ For some reason I think this looks cool which is unfortunate because it's pretty annoying to get the styles right.
+
+ I often have two or three paragraphs in these list items, too, so the hard part is getting the spacing between the paragraphs, list item heading, and separate list items to all make sense. Pretty tough honestly, you could make a strong argument that you just shouldn't write this way.
+
+- **Since this is a list, I need at least two items.**
+
+ I explained what I'm doing already in the previous list item, but a list wouldn't be a list if it only had one item, and we really want this to look realistic. That's why I've added this second list item so I actually have something to look at when writing the styles.
+
+- **It's not a bad idea to add a third item either.**
+
+ I think it probably would've been fine to just use two items but three is definitely not worse, and since I seem to be having no trouble making up arbitrary things to type, I might as well include it.
+
+After this sort of list I usually have a closing statement or paragraph, because it kinda looks weird jumping right to a heading.
+
+## Code should look okay by default.
+
+I think most people are going to use [highlight.js](https://highlightjs.org/) or [Prism](https://prismjs.com/) or something if they want to style their code blocks but it wouldn't hurt to make them look _okay_ out of the box, even with no syntax highlighting.
+
+Here's what a default `tailwind.config.js` file looks like at the time of writing:
+
+```js
+module.exports = {
+ purge: [],
+ theme: {
+ extend: {},
+ },
+ variants: {},
+ plugins: [],
+};
+```
+
+Hopefully that looks good enough to you.
+
+### What about nested lists?
+
+Nested lists basically always look bad which is why editors like Medium don't even let you do it, but I guess since some of you goofballs are going to do it we have to carry the burden of at least making it work.
+
+1. **Nested lists are rarely a good idea.**
+ - You might feel like you are being really "organized" or something but you are just creating a gross shape on the screen that is hard to read.
+ - Nested navigation in UIs is a bad idea too, keep things as flat as possible.
+ - Nesting tons of folders in your source code is also not helpful.
+2. **Since we need to have more items, here's another one.**
+ - I'm not sure if we'll bother styling more than two levels deep.
+ - Two is already too much, three is guaranteed to be a bad idea.
+ - If you nest four levels deep you belong in prison.
+3. **Two items isn't really a list, three is good though.**
+ - Again please don't nest lists if you want people to actually read your content.
+ - Nobody wants to look at this.
+ - I'm upset that we even have to bother styling this.
+
+The most annoying thing about lists in Markdown is that `
` elements aren't given a child `
` tag unless there are multiple paragraphs in the list item. That means I have to worry about styling that annoying situation too.
+
+- **For example, here's another nested list.**
+
+ But this time with a second paragraph.
+
+ - These list items won't have `
` tags
+ - Because they are only one line each
+
+- **But in this second top-level list item, they will.**
+
+ This is especially annoying because of the spacing on this paragraph.
+
+ - As you can see here, because I've added a second line, this list item now has a `
` tag.
+
+ This is the second line I'm talking about by the way.
+
+ - Finally here's another list item so it's more like a list.
+
+- A closing list item, but with no nested list, because why not?
+
+And finally a sentence to close off this section.
+
+## There are other elements we need to style
+
+I almost forgot to mention links, like [this link to the Tailwind CSS website](https://tailwindcss.com). We almost made them blue but that's so yesterday, so we went with dark gray, feels edgier.
+
+We even included table styles, check it out:
+
+| Wrestler | Origin | Finisher |
+| ----------------------- | ------------ | ------------------ |
+| Bret "The Hitman" Hart | Calgary, AB | Sharpshooter |
+| Stone Cold Steve Austin | Austin, TX | Stone Cold Stunner |
+| Randy Savage | Sarasota, FL | Elbow Drop |
+| Vader | Boulder, CO | Vader Bomb |
+| Razor Ramon | Chuluota, FL | Razor's Edge |
+
+We also need to make sure inline code looks good, like if I wanted to talk about `` elements or tell you the good news about `@tailwindcss/typography`.
+
+### Sometimes I even use `code` in headings
+
+Even though it's probably a bad idea, and historically I've had a hard time making it look good. This _"wrap the code blocks in backticks"_ trick works pretty well though really.
+
+Another thing I've done in the past is put a `code` tag inside of a link, like if I wanted to tell you about the [`tailwindcss/docs`](https://github.com/tailwindcss/docs) repository. I don't love that there is an underline below the backticks but it is absolutely not worth the madness it would require to avoid it.
+
+#### We haven't used an `h4` yet
+
+But now we have. Please don't use `h5` or `h6` in your content, Medium only supports two heading levels for a reason, you animals. I honestly considered using a `before` pseudo-element to scream at you if you use an `h5` or `h6`.
+
+We don't style them at all out of the box because `h4` elements are already so small that they are the same size as the body copy. What are we supposed to do with an `h5`, make it _smaller_ than the body copy? No thanks.
+
+### We still need to think about stacked headings though.
+
+#### Let's make sure we don't screw that up with `h4` elements, either.
+
+Phew, with any luck we have styled the headings above this text and they look pretty good.
+
+Let's add a closing paragraph here so things end with a decently sized block of text. I can't explain why I want things to end that way but I have to assume it's because I think things will look weird or unbalanced if there is a heading too close to the end of the document.
+
+What I've written here is probably long enough, but adding this final sentence can't hurt.
+
+## GitHub Flavored Markdown
+
+I've also added support for GitHub Flavored Mardown using `remark-gfm`.
+
+With `remark-gfm`, we get a few extra features in our markdown. Example: autolink literals.
+
+A link like www.example.com or https://example.com would automatically be converted into an `a` tag.
+
+This works for email links too: contact@example.com.
diff --git a/apps/www/src/content/pages/privacy.mdx b/apps/www/src/content/pages/privacy.mdx
new file mode 100644
index 0000000..6390468
--- /dev/null
+++ b/apps/www/src/content/pages/privacy.mdx
@@ -0,0 +1,45 @@
+---
+title: Privacy
+description: The Privacy Policy for Propwrite
+---
+
+# Privacy Policy
+
+At Propwrite, we are committed to protecting your privacy and ensuring that your personal information is handled in a safe and responsible manner. This Privacy Policy outlines how we collect, use, store, and protect the information you provide us when using our services.
+
+## Consent
+
+By using our website and services, you agree to the collection and use of information in accordance with this policy. If you do not agree with our policies and practices, please do not use our website.
+
+## Information We Collect
+
+We collect several types of information from and about users of our website, including:
+
+- **Personal Data**: This may include, but is not limited to, your name, email address, postal address, phone number, and other identifiers by which you may be contacted online or offline.
+- **Usage Data**: We may also collect information on how the website is accessed and used. This data may include your computer's Internet Protocol address (IP address), browser type, browser version, the pages you visit, the time and date of your visit, the time spent on those pages, and other diagnostic data.
+
+## How We Use Your Information
+
+We use the information we collect about you or that you provide to us, including any personal data, for various purposes, including to:
+
+- Provide and maintain our website.
+- Notify you about changes to our website or any products or services we offer or provide through it.
+- Allow you to participate in interactive features on our website.
+- Provide customer support.
+- Gather analysis or valuable information so that we can improve our website.
+- Monitor the usage of our website.
+- Detect, prevent and address technical issues.
+
+## Data Security
+
+We have implemented measures designed to secure your personal information from accidental loss and from unauthorized access, use, alteration, and disclosure. However, the transmission of information via the internet is not completely secure. Although we do our best to protect your personal information, we cannot guarantee the security of your personal information transmitted to our website.
+
+## Changes to Our Privacy Policy
+
+We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page. We will let you know via email and/or a prominent notice on our website, prior to the change becoming effective.
+
+## Contact Information
+
+To ask questions or comment about this Privacy Policy and our privacy practices, contact us at: [your contact information or email].
+
+Last updated: 28.11.2023
diff --git a/apps/www/src/content/pages/terms.mdx b/apps/www/src/content/pages/terms.mdx
new file mode 100644
index 0000000..e53263c
--- /dev/null
+++ b/apps/www/src/content/pages/terms.mdx
@@ -0,0 +1,30 @@
+---
+title: Terms & Conditions
+description: Read our terms and conditions.
+---
+
+Lorem ipsumMagna fermentum iaculis eu non diam. Vitae purus faucibus ornare suspendisse sed nisi lacus sed. In nibh mauris cursus mattis molestie a iaculis at. Enim sit amet venenatis urna. Eget sit amet tellus cras adipiscing.
+
+## Legal Notices
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Volutpat sed cras ornare arcu. Nibh ipsum consequat nisl vel pretium lectus quam id leo. A arcu cursus vitae congue. Amet justo donec enim diam. Vel pharetra vel turpis nunc eget lorem. Gravida quis blandit turpis cursus in. Semper auctor neque vitae tempus. Elementum facilisis leo vel fringilla est ullamcorper eget nulla. Imperdiet nulla malesuada pellentesque elit eget.
+
+Felis donec et odio pellentesque diam volutpat commodo sed.
+
+Tortor consequat id porta nibh. Fames ac turpis egestas maecenas pharetra convallis posuere morbi leo. Scelerisque fermentum dui faucibus in. Tortor posuere ac ut consequat semper viverra.
+
+## Warranty Disclaimer
+
+Tellus in hac habitasse platea dictumst vestibulum. Faucibus in ornare quam viverra. Viverra aliquet eget sit amet tellus cras adipiscing. Erat nam at lectus urna duis convallis convallis tellus. Bibendum est ultricies integer quis auctor elit sed vulputate.
+
+Nisl condimentum id venenatis a condimentum vitae. Ac auctor augue mauris augue neque gravida in fermentum. Arcu felis bibendum ut tristique. Tempor commodo ullamcorper a lacus vestibulum sed arcu non.
+
+## General
+
+Magna fermentum iaculis eu non diam. Vitae purus faucibus ornare suspendisse sed nisi lacus sed. In nibh mauris cursus mattis molestie a iaculis at. Enim sit amet venenatis urna. Eget sit amet tellus cras adipiscing.
+
+Sed lectus vestibulum mattis ullamcorper velit. Id diam vel quam elementum pulvinar. In iaculis nunc sed augue lacus viverra. In hendrerit gravida rutrum quisque non tellus. Nisl purus in mollis nunc.
+
+## Disclaimer
+
+Amet justo donec enim diam. In hendrerit gravida rutrum quisque non. Hac habitasse platea dictumst quisque sagittis purus sit. Faucibus ornare suspendisse sed nisi lacus. Nulla porttitor massa id neque aliquam vestibulum. Ante in nibh mauris cursus mattis molestie a. Mi tempus imperdiet nulla malesuada.
diff --git a/apps/www/src/emails/components/footer.tsx b/apps/www/src/emails/components/footer.tsx
new file mode 100644
index 0000000..cd0f0b2
--- /dev/null
+++ b/apps/www/src/emails/components/footer.tsx
@@ -0,0 +1,35 @@
+/* eslint-disable react/no-unescaped-entities */
+import { Hr, Tailwind, Text } from "@react-email/components";
+
+export default function Footer({
+ email,
+ marketing,
+}: {
+ email: string;
+ marketing?: boolean;
+}) {
+ return (
+
+
+ {marketing ? (
+
+ This email was intended for{" "}
+ {email}. If you were not expecting
+ this email, you can ignore this email. If you don't want to receive
+ emails like this in the future, you can{" "}
+
+ unsubscribe here
+
+ .
+
+ ) : (
+
+ This email was intended for{" "}
+ {email}. If you were not expecting
+ this email, you can ignore this email. If you are concerned about your
+ account's safety, please reply to this email to get in touch with us.
+
+ )}
+
+ );
+}
diff --git a/apps/www/src/emails/magic-link-email.tsx b/apps/www/src/emails/magic-link-email.tsx
new file mode 100644
index 0000000..94fe41e
--- /dev/null
+++ b/apps/www/src/emails/magic-link-email.tsx
@@ -0,0 +1,70 @@
+import {
+ Body,
+ Button,
+ Container,
+ Head,
+ Hr,
+ Html,
+ Preview,
+ Section,
+ Tailwind,
+ Text,
+} from "@react-email/components";
+
+import { Icons } from "../components/shared/icons";
+
+type MagicLinkEmailProps = {
+ actionUrl: string;
+ firstName: string;
+ mailType: "login" | "register";
+ siteName: string;
+};
+
+export const MagicLinkEmail = ({
+ firstName = "",
+ actionUrl,
+ mailType,
+ siteName,
+}: MagicLinkEmailProps) => (
+
+
+
+ The sales intelligence platform that helps you uncover qualified leads.
+
+
+
+
+
+ Hi {firstName},
+
+ Welcome to {siteName} ! Click the link below to{" "}
+ {mailType === "login" ? "sign in to" : "activate"} your account.
+
+
+
+
+
+ This link expires in 24 hours and can only be used once.
+
+ {mailType === "login" ? (
+
+ If you did not try to log into your account, you can safely ignore
+ it.
+
+ ) : null}
+
+
+ 123 Code Street, Suite 404, Devtown, CA 98765
+
+
+
+
+
+);
+
+export default MagicLinkEmail;
diff --git a/apps/www/src/emails/welcome-email.tsx b/apps/www/src/emails/welcome-email.tsx
new file mode 100644
index 0000000..019eaf1
--- /dev/null
+++ b/apps/www/src/emails/welcome-email.tsx
@@ -0,0 +1,89 @@
+/* eslint-disable react/no-unescaped-entities */
+import {
+ Body,
+ Container,
+ Head,
+ Heading,
+ Hr,
+ Html,
+ Img,
+ Link,
+ Preview,
+ Section,
+ Tailwind,
+ Text,
+} from "@react-email/components";
+
+import Footer from "./components/footer";
+
+export default function WelcomeEmail({
+ name = "John Doe",
+ email = "welcome@propwrite.com",
+}: {
+ name: string | null;
+ email: string;
+}) {
+ return (
+
+
+ 
+ 
+ 
+