Church Information Management Web Application
Budget: $30 – $250 USD
1. Introduction
This application aims to modernize and optimize the administrative processes of the church by enabling efficient management of member data and automatic generation of important documents. The application will use React.js for the frontend and Firebase for the backend and storage, ensuring a seamless user experience for administrators and church members.
2. Technical Requirements
■ Frontend: React.js
⦿ Objective: To build a user-friendly and responsive interface.
⦿ Technology: React.js, utilizing reusable components for forms, tables, and document display.
■ Backend and Database: Firebase
⦿ Firestore: For storing member information and related details.
⦿ Firebase Authentication: For access control, ensuring only authenticated users can modify data.
⦿ Firebase Hosting: For deploying the application using the free plan.
3. Page Design
3.1 Home / Login Page
■ Purpose: Authenticate users. Access is restricted to administrators and members.
■ Elements:
⦿ Form with "Email" and "Password" fields.
⦿ "Sign In" button.
⦿ "Recover Password" option that verifies the user's email, sends a reset email, allows the user to set a new password, and updates their credentials securely.
3.2 Member Registration and Profile Page
■ Purpose: Allow registration of new members and enable members to view and edit their personal data. Admin can create and modify everyone’s data while a member only can touch his personal data.
■ Fields:
⦿ Personal Data:
▪ First Names: (text)
▪ Last Names: (text)
▪ Date of Birth: (date)
▪ Place of Birth: (text)
▪ Gender: (bool - Male/Female)
▪ Marital Status: (switch - Single, Married, Divorced)
▪ E-mail
⦿ Documents:
▪ Type of Document: (switch - Tarjeta de Identidad, Cédula de Ciudadanía, Cédula de Extranjería)
▪ Document Number: (text)
⦿ Spiritual Data:
▪ Conversion Date: (date)
▪ Baptism Date: (date)
▪ Biblical Studies Completed: (text)
▪ Church Role: (text)
⦿ Family Data:
▪ Father's Name: (text)
▪ Mother's Name: (text)
▪ Spouse's Name: (text - optional)
▪ Children's Names: (text - optional, repeatable)
⦿ Professional Data:
▪ Profession: (text)
▪ Occupation: (text)
⦿ References:
▪ Friend References: (name and phone) (repeatable)
▪ Family References: (name and phone) (repeatable)
■ Member Role Functionalities:
⦿ View personal information.
⦿ Edit and Submit changes for pastor/admin validation.
3.3 Automatic Document Generation Pages
■ Objective: Facilitate the creation of documents based on stored information.
■ Documents:
3.3.1 Member CV: This document will compile all the information from the member's profile into a structured format.
▪ Personal Data (Last Names, First Names, Date of Birth, etc.)
▪ Documents (ID)
▪ Spiritual Data (Conversion Date, Baptism Date, etc.)
▪ Family Data (Father's Name, Mother's Name, etc.)
▪ Professional Data (Profession, Occupation)
▪ References (Friend and Family References)
3.3.2 Course Certificate:
▪ Member's Name: (text)
▪ Completion Date: (date)
▪ Course Name: (text)
▪ Course Volume or Level: (text)
3.3.3 Baptism Certificate:
▪ Full Member Name: (text)
▪ Baptism Date: (date)
▪ Pastor's Signature and Name: (text)
3.3.4 Membership Card:
▪ Member's Photo: (image file)
▪ Full Names: (text)
▪ Identification Number: (text)
▪ Title or Position: (text)
▪ Card Expiry Date: (date)
▪ Church Authority Signatures: (text)
3.4 Pastor and Administrator Pages
■ Purpose: To manage and validate changes made by members.
■ Functionalities:
⦿ Review and approve or reject changes submitted by members.
⦿ Full access to member profiles for updates and corrections.
⦿ Generate and manage document templates.
4. Navigation
■ Sections:
⦿ Member Registration/Profile
⦿ Document Generation (Member CV, Courses, Baptisms, Membership Card)
⦿ Validation (Pastors' access to validate member changes)
5. Authentication and Authorization
■ Implementation: Use Firebase Authentication.
■ Roles:
⦿ Administrator/Pastor: Full access to the application, including member management and document generation.
⦿ Member: Can view their information, request edits to their profile (subject to pastor validation), and download necessary PDF documents.
6. Deployment
■ Platform: Firebase Hosting.
■ Plan: Utilize the free plan, ensuring optimization to stay within usage limits.
7. Documentation, support and others
■ Source Code: Complete and well-documented.
■ Design: Ensure generated documents maintain a clean and professional design.
■ Instructions: on how the application was developed and deployed on Firebase.
■ Documentation: on how to use the application, including details on each section/tab.
■ Website must support Spanish language as principal
This application aims to modernize and optimize the administrative processes of the church by enabling efficient management of member data and automatic generation of important documents. The application will use React.js for the frontend and Firebase for the backend and storage, ensuring a seamless user experience for administrators and church members.
2. Technical Requirements
■ Frontend: React.js
⦿ Objective: To build a user-friendly and responsive interface.
⦿ Technology: React.js, utilizing reusable components for forms, tables, and document display.
■ Backend and Database: Firebase
⦿ Firestore: For storing member information and related details.
⦿ Firebase Authentication: For access control, ensuring only authenticated users can modify data.
⦿ Firebase Hosting: For deploying the application using the free plan.
3. Page Design
3.1 Home / Login Page
■ Purpose: Authenticate users. Access is restricted to administrators and members.
■ Elements:
⦿ Form with "Email" and "Password" fields.
⦿ "Sign In" button.
⦿ "Recover Password" option that verifies the user's email, sends a reset email, allows the user to set a new password, and updates their credentials securely.
3.2 Member Registration and Profile Page
■ Purpose: Allow registration of new members and enable members to view and edit their personal data. Admin can create and modify everyone’s data while a member only can touch his personal data.
■ Fields:
⦿ Personal Data:
▪ First Names: (text)
▪ Last Names: (text)
▪ Date of Birth: (date)
▪ Place of Birth: (text)
▪ Gender: (bool - Male/Female)
▪ Marital Status: (switch - Single, Married, Divorced)
⦿ Documents:
▪ Type of Document: (switch - Tarjeta de Identidad, Cédula de Ciudadanía, Cédula de Extranjería)
▪ Document Number: (text)
⦿ Spiritual Data:
▪ Conversion Date: (date)
▪ Baptism Date: (date)
▪ Biblical Studies Completed: (text)
▪ Church Role: (text)
⦿ Family Data:
▪ Father's Name: (text)
▪ Mother's Name: (text)
▪ Spouse's Name: (text - optional)
▪ Children's Names: (text - optional, repeatable)
⦿ Professional Data:
▪ Profession: (text)
▪ Occupation: (text)
⦿ References:
▪ Friend References: (name and phone) (repeatable)
▪ Family References: (name and phone) (repeatable)
■ Member Role Functionalities:
⦿ View personal information.
⦿ Edit and Submit changes for pastor/admin validation.
3.3 Automatic Document Generation Pages
■ Objective: Facilitate the creation of documents based on stored information.
■ Documents:
3.3.1 Member CV: This document will compile all the information from the member's profile into a structured format.
▪ Personal Data (Last Names, First Names, Date of Birth, etc.)
▪ Documents (ID)
▪ Spiritual Data (Conversion Date, Baptism Date, etc.)
▪ Family Data (Father's Name, Mother's Name, etc.)
▪ Professional Data (Profession, Occupation)
▪ References (Friend and Family References)
3.3.2 Course Certificate:
▪ Member's Name: (text)
▪ Completion Date: (date)
▪ Course Name: (text)
▪ Course Volume or Level: (text)
3.3.3 Baptism Certificate:
▪ Full Member Name: (text)
▪ Baptism Date: (date)
▪ Pastor's Signature and Name: (text)
3.3.4 Membership Card:
▪ Member's Photo: (image file)
▪ Full Names: (text)
▪ Identification Number: (text)
▪ Title or Position: (text)
▪ Card Expiry Date: (date)
▪ Church Authority Signatures: (text)
3.4 Pastor and Administrator Pages
■ Purpose: To manage and validate changes made by members.
■ Functionalities:
⦿ Review and approve or reject changes submitted by members.
⦿ Full access to member profiles for updates and corrections.
⦿ Generate and manage document templates.
4. Navigation
■ Sections:
⦿ Member Registration/Profile
⦿ Document Generation (Member CV, Courses, Baptisms, Membership Card)
⦿ Validation (Pastors' access to validate member changes)
5. Authentication and Authorization
■ Implementation: Use Firebase Authentication.
■ Roles:
⦿ Administrator/Pastor: Full access to the application, including member management and document generation.
⦿ Member: Can view their information, request edits to their profile (subject to pastor validation), and download necessary PDF documents.
6. Deployment
■ Platform: Firebase Hosting.
■ Plan: Utilize the free plan, ensuring optimization to stay within usage limits.
7. Documentation, support and others
■ Source Code: Complete and well-documented.
■ Design: Ensure generated documents maintain a clean and professional design.
■ Instructions: on how the application was developed and deployed on Firebase.
■ Documentation: on how to use the application, including details on each section/tab.
■ Website must support Spanish language as principal