How we do at Wakeflow
This repo provides some documentation of our processes at Wakeflow. We share it publically so that our client and potential hires can learn about how we go about our business.
If you have any questions/comments/inspiration please don't hesitate to reach out to contact@wakeflow.io or contribute directly by making a Pull Request (see How we contribute below).
Professional Development
Coding
- How we define good software
- How we contribute
- How we Javascript
- How we deploy
- How we handle secrets
- How we configure our dotfiles
- How we test
- How we make API requests
- How we sort arrays
- How we do dates
- How we CSS
- How we lint
- How we CI/CD
- How we backup Firestore
- How we track events
- How we validate
Our Microservices
There are a number of microservies that we have developed in-house that we universally use on our projects:
- tokens.wakeflow.io for authenticating
- events.wakeflow.io for event tracking
- timer.wakeflow.io for delaying API calls
- emails.wakeflow.io for sending emails
- 2fa.wakeflow.io for multi-factor authentication
- payments.wakeflow.io for taking payments
- team.wakeflow.io for internal affairs
- db.wakeflow.io for quick DB requirements
- files.wakeflow.io for non-public file storage
- crm.wakeflow.io for keeping track of our customers
