.@trybible is coming soon! Check out some details about the app here: 24hrstartup.com/jordan-oconnor.
I thought I should mention some things about my workflow / frameworks of choice, because it's somewhat strange and I've never seen anyone do it like this. #24hrstartup
Here's what I use to build fast:
- Hosting: @github Pages
- HTML Framework: @jekyllrb
- CSS: @getbootstrap / @SassCSS
- JS: @jquery
- Auth / DB / Cloud Functions: @Firebase
This keeps things light, modularized and serverless.
🙅 No setting up servers. 🙅 Complicated hosting.
Github Pages is super fast, and of course by using it I get the benefits of a Github repo. All I do is push changes and Github takes care of the rest. No CI, no fluff, just results.
By using Jekyll's layout paradigm, I am able to build small HTML + CSS + JS components and use them on pages as needed. If I don't need it, I don't include it. This cuts down on bloat, and in-lines all of my code (sans Bootstrap and JQuery).
By using Firebase for my back-end, I am able to scale infinitely and use their offline data capabilities to make my app lightning fast like a PWA. The DB information is cached on the user's computer and only updated when necessary. More on that here: firebase.google.com/docs/firestore…
Instead of using routing, I use URL parameters. I typically use a few root pages (e.g. profile, app, etc.) but beyond that the information displayed is interpolated by the different URL parameters used. This makes it a static website with dynamic content.
So, what's my process?
1. Build out HTML + CSS components
2. Layout the pages
3. Add JQuery functionality
4. Add firebase Auth + DB Sync to populate data
You'll see this in the live stream!
What's your process? Any tricks or tips you use to ship fast? #24hrstartup
Share this Scrolly Tale with your friends.
A Scrolly Tale is a new way to read Twitter threads with a more visually immersive experience.
Discover more beautiful Scrolly Tales like this.
