7d0aeeefe5
* Improve format and clarity of the docs [ci skip] While this change produces a lot of git noise by enacting what seems like an arbitrary linewrap on most of the files in the documentation it will result in better version control and tracking of the changes in the documentation. For example, as it currently stands, if one was to make a PR to move a comma in a sentence because each paragraph in most of the files is on a single line, that small change would look in the git history like the author had modified the entire paragraph. In reality, this author just moved a comma. This change also includes a significant number of modifications to the more article-esque docs. Many of these docs were written in a sort of stream-of-conciousness and aren't as easy to read as they could be. Hopefully this is the first of several readability changes. If we could get these docs to a more accessible reading level, we would probably see an increase in contributions. :) * Delegate markdown wrapping to Prettier * Add linewrapping explanation in the docs [ci skip]
2.5 KiB
2.5 KiB
| title |
|---|
| Stack |
🔑 Key App tech/services
For the Dev.to tech stack we use:
- Puma as the web server
- PostgreSQL as the primary database
- Redis to store additional data and eventually replace memcache
- Fastly for edge caching
- Cloudinary for image manipulation/serving
- Airbrake for error monitoring
- Timber for logging
- Delayed Job and Active Job for background workers
- Algolia for search
- Redcarpet and Rouge to parse Markdown
- Carrierwave, Fog and AWS S3 for image upload/storage
- InstantClick (a modified version) instead of Turbolinks to accelerate navigation
- ImageMagick to manipulate images on upload
- Heroku for hosting
- Heroku scheduler for scheduled jobs
- Sendgrid for transactional mailing
- Mailchimp for marketing/outreach emails
- Figaro for app configuration
- CounterCulture to keep track of association counts (counter caches)
- Rolify for role management
- Pundit for authorization
- Service Workers to proxy traffic
- Preact for some of the frontend. See the Frontend Guide for more info
- Pusher for realtime communication between the application and users' browsers
- GitDocs for beautiful and SEO-friendly documentation
- Git for version control
- GitHub for hosting the source code and issue tracking
This list is non-exhaustive. If you see something that belongs here, feel free to add it.