Open Sophon96 opened 1 year ago
Latest commit: |
4620368
|
Status: | ✅ Deploy successful! |
Preview URL: | https://18a6553e.club-portal.pages.dev |
Branch Preview URL: | https://routes-skeleton.club-portal.pages.dev |
I don't think we need routes for club member lists and club member pages. A member list can be shown in the club page, and there's no need for a whole page on each member.
Those aren't pages, those are API endpoints for joining and leaving. Those
files don't have a default export of a function that returns a React
component (which would then render to HTML and be shown as a page), but
only export a loader
function (which handles data loading and GET
requests) or an action
function (which handles all other HTTP methods).
This commit introduces the starting layout proposed in #2. There is no functionality or "business logic" for any of the routes in this commit. These routes include unique pages for individual clubs as well as a collective overview on the admin side. Within these pages, there are functionalities for viewing and modifying specific aspects of each club, including the ability to approve or deny requests.