FCD Community Project #1: Vote for your favorite!
The Full Cycle Dev community has grown by over 250 discord members over the last day. To celebrate, we'll go full cycle on a community suggested SaaS product idea. And every one of you gets to vote!
Over the last day, we grew by a lot of members and suggestions for the first project were posted in the discord channel.
I took the liberty of curating the suggestions and to summarize them in this post. Some important and often-needed features will definitely be included in the first project, while we decided to hold a vote on the more specific topics.
Community project #1 will likely be done and streamed on Friday, Nov 10th, pending some availability checks. Make sure to follow on Twitter/X to be notified!
We will cover the following areas as a basis, in order:
Setting up the code base, with django, PostgreSQL, redis, celery and more. All in docker.
User registration, verification emails
Adding everything to version control, github in this case.
Launching locally and explaining the generated stack.
Renting a Virtual Private Server (VPS), and setting that up.
Configuring a domain to point to the server.
Deploying the web app to the VPS.
Setting up CI/CD to automatically re-deploy on pushes/merge on main branch.
Social logins with Google
… winners of the poll below in descending order
We will start with the poll winner.
Depending on time left, we will also cover the other options.
Option #1: Ticketing system
Support ticket system (suggested by turmiosieni)
allowing users to create a ticket
users and admins can reply and manage the ticket
Option #2: Billing/payment system
billing and payment processing (suggested by ace#2814 and magnusra)
integrating stripe, evaluating whether to use
the 1st party stripe SDK
a 3rd party SDK
stripe checkout with callbacks
adding a credit card as payment method
buying products and managing subscriptions
Option #3: Renting/order management system
User story without concrete requirements (suggested by BoredAIAnimal)
I’ll just post their words here as quote. The first step will be breaking this down into smaller requirements.
Lets considers one user journey, there is a company that hires out a few types of equipment, example: a temporary fencing charged by the meter by number of days on hire , a forklift by number of days, a few more types of solar lighting systems that are charged by a day/weekly rate, a customer sign's up with multiple documents to be approved by the company to be able to place an order , a admin gets notified of the new sign up looks at the documentation and approves the application , the client gets notified, they login into their user portal and pick any equipment they need and book it in for the number of days required and they will be sent a quote/invoice to be paid, once payment done the equipment is allotted to the client and ready for pickup/dropoff .
Option #4: Snowplowing P2P system
Connect customers and providers (suggested by turmiosieni)
providers can offer their services, and manage requests
clients can request these services
rating system
billing system from option #2