-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Description
Pros and Cons
Pros
- Could reduce our dependence on services like Bandpage if our information (e.g. upcoming shows) is easy enough to update.
- Easy for non-devs to update our EPK.
- Song documentation will already be stored in Google Drive, so we can easily publish it if we want. Might be nicer than using the Google Drive interface to reference songs.
- Google Docs is a good interface for blogging if we want to roll our own blog. Medium is also a good option.
- Easy to fix typos, etc.
- If we store tour planning data in Google Drive, it could automatically generate reports using our tour planner. Reports could be presented on our website.
Cons
- Cost in development time.
- Cost in maintenance.
- Maybe scaling too soon? Are devs really a big enough bottleneck to website updates?
- Making our site even faster and giving it a better design seem like higher priorities.
Implementation
I can imagine two rendering pipelines. Client-side rendering is slightly less performant, but easier to implement:
Client-side rendering
- A user updates a song’s lyrics in Google Drive.
- A user publishes those updates using Drive CMS.
- Drive CMS posts the updates to the Firebase database.
- When a visitor opens partials.co/songs, the app fetches all song info from the Firebase db.
- The app renders the songs dynamically with React.
Server-side rendering
Another option, server-side rendering, is more complicated but also probably faster:
- A user updates a song’s lyrics in Google Drive.
- A user publishes those updates using Drive CMS.
- Drive CMS posts the update to a build server.
- The build server renders each song page dynamically and saves the rendered page to disk.
- The re-built app with all the rendered song pages is deployed to Firebase hosting.
More on server-side vs. client-side rendering:
https://www.quora.com/What-are-the-tradeoffs-of-client-side-rendering-vs-server-side-rendering
If we decide to do this, Max Berry has built a Google Drive CMS that integrates with Firebase.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels