After several years of being dissatisfied with existing group event tools (Meetup, Facebook events) we decided to build our own.
This will be a self-hosted Docker container that you can one-click deploy to the cloud, then configure through an admin panel. No coding required.
Your organization can host an instance of Chapter under a sub-domain of your website, such as chapter.sierraclub.org or chapter.womenwhocode.org.
You can use your own authentication tools. And all your user data will stay on your own server.
Our Vision statement provides more details on the reasons for Chapter.
To better communicate and more easily build an API and UI, the current contributors have decided on a collection of terminology to clarify discussions surrounding the Chapter project:
| Term | Definition | Example |
|---|---|---|
| instance | a web server deployment of the "Chapter" application, managed by an organization. | a Docker container running on a web host |
| organization | a non-profit with multiple chapters | Women Who Code at the sub-domain: chapter.womenwhocode.org |
| chapter | a container for events and users | Women Who Code - New York City |
| event | a meeting with a specific location and time to which users can RSVP | Coffee And Code - BistroOne, New York City, NY - April 9, 2020 |
| user | an authenticated user who is authorized based on their role(s) | Sally Gold - SallyG@example.com |
| visitor | an non-authenticated web browser session with view-only access to public content | Anonymous Web Browser Client |
| administrator | the role of a user to manage the entire "Chapter" application instance for an organization | Women Who Code - Global Chapter Administrator |
| organizer | the role of a user who can manage a chapter's events, RSVPs, communications, and users | Women Who Code - New York City, Local Organizer |
| member | the role of a user who can follow and receive notifications from a chapter and RSVP to events | Women Who Code - New York City, Local Member |
We are planning to use the following tools:
- Node.js / Express for our backend using JavaScript/TypeScript
- Postgres with TypeORM
- Next.js for both client and server-side rendering of the frontend (NextJS is based on React)
- JavaScript/TypeScript
- Styled Components for styling.
- Functional Components with Hooks
- chai for writing unit tests.
A lot of people know these tools, and they're proven to work well at scale.
We will focus on building an open API first. Then developers can use the API to build their own mobile clients and voice interface clients.
Requirements: Node.js, Docker, internet access
Follow instructions for downloading and installing Node.js for your operating system from the official Node.js website.
Ensure you are installing Node 10 or greater and npm 6 or greater.
See the Docker installation "Supported platforms" section and follow the instructions to download & install Docker Desktop for your operating system (or Docker CE for Linux).
You can find more resources on Docker here:
Open up Terminal/Powershell/bash and navigate to the directory where you want the project to live.
Clone this repository:
git clone https://github.com/freeCodeCamp/chapter
Navigate to the newly cloned repo:
cd chapter
Install dependencies:
npm install
If needed, set up environment variables under 'app -> environment' in the docker-compose.yml file.
Ensure that Docker Desktop is up and running, then run the following command:
docker-compose up
Wait for the logs to show "server started on port 8000", then navigate to localhost:8000 to view the app.
The server will automatically restart anytime you save a .ts or .js file within the server/ directory.
You can run any command within the container by prefixing it with docker-compose exec app, e.g. docker-compose exec app npm install express
Run tests
npm run test
Run tests in watch mode
npm run test:watch
We use Open API 3.0 to define the API structure of the application. You can see the full documentation with:
npm run speccyNavigate to http://localhost:8001 to see API docs
The MVP user stories are shown in the MVP Project kanban / cards and as issues marked with "MVP".
We are maintaining a list of post-MVP conversations and user stories using the "Roadmap" tag.
Quincy Larson is the project lead. FreeCodeCamp will start "dogfooding" the MVP with several of its local study groups.
Here's an out-dated example of an app with similar functionality: The freeCodeCamp Study Group Directory.
- You should join our Discord server to get connected with people interested in this project and to be aware of our future announcements.
- Please read the suggested steps to contribute code to the Chapter project before creating issues, forking, or submitting any pull requests.
Copyright © 2019 freeCodeCamp.org
The computer software is licensed under the BSD-3-Clause license.
Thanks goes to these wonderful people (emoji key):
This project follows the all-contributors specification. Contributions of any kind welcome!