initial commit

readme.md

@@ -0,0 +1,98 @@
+# SAAS Builder
+
+A simple framework or boilerplate that will provide everything you need in order to build a SAAS application.
+
+Everything must be procedurally generated based on configuration.
+
+Items required for a SAAS application:
+
+* Web application
+* Mobile application
+* Marketing Website
+* Sign-up and payment
+* Authentication
+* backend business logic
+  * CRUD
+  * Specialized views and queries
+  * Actions a user can take
+  * Regularly scheduled tasks
+  * Rule based events - trigger an action on a preset state (could supersede the scheduled tasks)
+* Data storage
+  * Access rules
+* File/Object storage
+  * Upload/Download
+  * Access rules
+* Integration with external application specific tools and services for ingestion (e.g. Domo Workbench, Weave Sync App, Parentlink Data app, etc)
+* Notifications - send to frontend
+* Send messages via email, SMS, Slack, or other chat applications
+* Event streams - for internal and external consumption
+* Audit logging - for user actions
+* System logging and monitoring
+* System monitoring for uptime and maintenance
+* User feedback system
+* Support systems - chat, phone, email, ticketing
+* Sales - lead gen, demoing, closing, onboarding
+
+Can everything be based on a single 'Entity' object that gets augmented with features when the config calls for it?
+
+Let's run through some examples.
+
+Some examples of entities are:
+* users
+* pages
+* blog articles
+* tasks
+* Notifications
+* Photos
+* Permissions
+* Customers
+* Addresses
+* Passwords
+* SMS Messages
+* SMS Threads
+* Databases
+* DB Tables
+* Charts
+* Preferences
+* Forms
+* Form Fields
+* User Actions
+* System Actions
+* Micro Services
+* Support Tickets
+* Templates
+
+I'm trying to think through how I'd go about building a page with dynamic content on it. Let's keep it simple first. And build a basic blog.
+* Create an entity and set its name to be a 'page'.
+* Properties for the page will include a name
+* Features would include a template that renders blog articles with pagination
+* Child entities would include blog articles
+
+I asked ChatGPT to come up with some example page types that I would need to implement and here is what it came up with:
+
+* Login/Authentication Views: For user login, registration, password recovery, and multi-factor authentication.
+* Profile/User Account Views: For user settings, profiles, and account management.
+* Admin/Settings Views: For configuring application settings, roles, and permissions.
+* Settings/Preferences Views: For user preferences and application configurations.
+* Form Views: For data entry, including creating, editing, and submitting forms.
+* Wizard/Step-by-Step Views: For multi-step processes such as onboarding or checkout flows.
+* Wizard/Step-by-Step Views: For guiding users through a process with multiple steps.
+* Table/Grid Views: For displaying tabular data with sorting, filtering, and pagination.
+* Search/Filter Views: For advanced search functionalities with filtering options.
+* Notifications/Activity Feed Views: For displaying alerts, notifications, and activity logs.
+* Inbox/Message Views: For managing messages, emails, or chat interfaces.
+* Modal/Popup Views: For transient interactions like alerts, confirmations, and quick data entry.
+* Error/Empty State Views: For handling errors, no data, or empty states gracefully.
+* Calendar Views: For scheduling, booking, and time management features.
+* Charts/Graphs Views: For visualizing data with different types of charts (e.g., bar, line, pie).
+* Reports/Analytics Views: For detailed reports and analytics with drill-down capabilities.
+* Card Views: For summarizing information in a card format, useful for dashboards and overviews.
+* Map Views: For geographic data representation, such as location tracking or service areas.
+* Help/Support Views: For providing user assistance, FAQs, and support ticket submission.
+* Documentation Views: For displaying manuals, guides, and documentation.
+* Landing Page/Marketing Views: For public-facing marketing pages with promotional content.
+
+Lower priority views
+* Kanban Board Views: For project and task management with drag-and-drop functionality.
+* Tree Views: For hierarchical data structures, such as file explorers or organizational charts.
+* Gallery Views: For displaying images or media content in a grid or masonry layout.