SEO, Role Based Authentication, and React Query and more, basic configurations added to the boilerplate

[MeatBoyed]

Hi,

I have added a few more boilerplate features into the repo. These are things I've found myself having to constituently implement.

SEO

The main features I focus was to add more SEO configuration - such as the full MetaData object, JSONltd, Sitemap generation and a Robots.txt file, and Google Analytics Tag.

ShadCN basic components

I also added more basic ShadCN components that a basic web app/website would need - particularly the Form components.

React Query

This is a personal preference, as I know not everyone likes/would want to use this. But personally I've found React Query as the best way to do client-side mutation & data fetching in React while still keeping the code modular and maintainable.

Templated File Strucutre

I've also added empty folders to provide the outline for the file structure (this also a personal preference)

Primsa

I've added the very basic configuration for Prisma, this again is a personal preference which I leave to the maintainers to make the final decision to add.

Clerk Authentication

Clerk has been configured for the site (it uses the hosted clerk /login & /signup pages) and has Role Based Authentication implemented - also a personal preference.

Env

The env files have also been updated to support these additions, particularly for the Database URL

Change Log:

• React Query Setup
• Basic ShadCN comps added
• Sitemap object
• Updated .env
• Added Google Analytics
• Metadata & JSON-ltd
• Sitemap & Robots added

This is my first proper commit to a community project. So my apologies if it doesn't match the contribution standards yet.

Hope these additions provide some benefit and a starting ground for further contributions.

Thanks, have a good day further!

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
next-entree	❌ Failed (Inspect)			Dec 5, 2024 8:49am

[vercel]

@MeatBoyed is attempting to deploy a commit to the redpangilinan's projects Team on Vercel.

A member of the Team first needs to authorize it.

[redpangilinan]

Hey, thanks for the contribution! The changes are nice but it locks the boilerplate to use Prisma and Clerk for authentication which, while good, reduces the flexibility of picking different options.