32 lines
1.6 KiB
Markdown
32 lines
1.6 KiB
Markdown
# Functional Requirements
|
|
|
|
## FR1: CORA Data Ingestion
|
|
The system must ingest and extract specified data from a CORA .xlsx file to create a new project entry in the database.
|
|
|
|
## FR2: AI Content Generation
|
|
The system shall use AI to generate titles, outlines, and full-text content based on the ingested data.
|
|
|
|
## FR3: HTML Formatting
|
|
The system must format the generated text content into a standardized HTML/CSS template.
|
|
|
|
## FR4: Multi-Cloud Deployment
|
|
A module will automatically deploy the generated HTML files to multiple cloud storage providers, including AWS S3, Bunny.net, Azure Blob Storage, Digital Ocean Spaces, Linode Object Storage, Backblaze B2, and Cloudflare Pages.
|
|
|
|
## FR5: Interlinking Module
|
|
An interlinking module must be able to query a target subdomain, identify existing content, and inject new interlinks into the HTML.
|
|
|
|
## FR6: URL Logging
|
|
All generated URLs must be logged to both the central SQLite database and a local .txt file for tracking. The database record must include the content Tier (e.g., distinguishing links to other owned properties).
|
|
|
|
## FR7: Internal API
|
|
An internal API endpoint must be available to transmit job data to the separate link-building machine.
|
|
|
|
## FR8: User Authentication
|
|
The system will include a basic user authentication system (username/password) with each user having one of two roles: "Admin" and "User".
|
|
|
|
## FR9: Admin User Management
|
|
Users with the "Admin" role can manage users (add/remove) and edit the master JSON configuration files.
|
|
|
|
## FR10: User Content Management
|
|
Users with the "User" role can execute content generation jobs and have the ability to edit the generated content.
|