Identify and list down possible web features that will be developed, either immediately or in the future.
e.g:

• Dashboard that shows summary of monthly bills' breakdown
• Users/Residents can edit their own info
• Viewing active monthly installments
• etc.

• Decide whether to use database driver (via Prisma etc) or to use Supabase's PostgREST
• After decision is made, plan the workflow for the application's middleware(s) on the data fetching modules
• Enable RLS on schema tables if necessary
• Ensure no credentials are exposed in the repository files
• Create token/db user if possible/necessary for the web app in supabase console

Create branch to separate work between main and development

The current features fit for MVP is listed on issue #7 and workable with the current database structure. The implementation of those features is dependent on UI design on issue #4 .

For future features especially those that require DB or other Supabase functionalities, it is suggested that:

1. A thorough plan on what the feature does is done
2. Implementation plan has to be planned e.g system modules, interaction with which Supabase features etc. Expected API request/response bodies MUST BE PLANNED AND AGREED UPON FIRST.
3. UI design for pages that are involved in the feature implementation be drafted first

Currently Vercel is planned and already tested for deployment of the actual web. The downside is that unlike Supabase, Vercel's team view is for paid users and thus not free. A possible solution is, if allowing team members to configure application builds and view build logs is necessary, is to create a joint email account and use it on Vercel so that all repository members can view them. Another solution is to find another free static site hosting service with team support, but this may take time, as most service providers only allow such feature for paid users only. Another solution is to simply use Github Pages, although this requires extra config (maybe little to no config at all, idk) as compared to Vercel which simply listen's to branch activities and begins build and deployment.

Identify the possible pages that will exist in the app. May refer to and must tally with the features listed in issue #7. Once identified, may start creating issues for each page before beginning development

Create js/ts app with preferred framework (react, next, etc)