Cross Post - Case Study: Mike Johnston for Colorado #3993
Conversation
|
Deploy preview for gatsbygram ready! Built with commit 62969b0 |
ghost
assigned 
|
|
||
| Our goal was to provide a solid architecture to build a long-term future on top of. In later phases the site will become a full-fledged web application with an organizing and fundraising platform built-in, and the goal beyond that is to create an innovative “open source policy” platform to involve citizens in the policy-making process like never before! | ||
|
|
||
| To execute on this effectively, I prioritized a few architectural goals: |
There was a problem hiding this comment.
Use "we" instead of "I" -- need to maintain a consistent pluralization of subject and "we" reads better
|
|
||
| ## We’re Available! | ||
|
|
||
| While Ecliptic is finishing up the interactive features for the site, we also have wide availability opening up in February for new contracts! We can get started right away on your next project, from high-performance content-driven sites to richly interactive web and mobile applications. |
There was a problem hiding this comment.
Please move some of this content to the beginning to provide context on your organization. Please remove the plug though as this will be an official GatsbyJS blog post. It's fine to include contact details on the bottom of the post, eg, "if you'd like to hear more about how we did this, I would love to chat!"
|
|
||
| ### How we used React, Headless WordPress, GraphQL & Gatsby to build Mike’s new online platform | ||
|
|
||
| [Mike Johnston](https://www.mikejohnstonforcolorado.com) is a Colorado gubernatorial candidate with an ambitious vision. When I heard about his ideas for an online platform to truly engage with his constituents and give them a real voice, I was excited about the opportunity to make his ideas into reality! |
There was a problem hiding this comment.
include some info on your org here, see comment at bottom
|
|
||
| ## Static Site Generation with Gatsby | ||
|
|
||
| Since I had complete freedom on the front end, I wanted to pursue a solution based on [React](https://reactjs.org/), my framework of choice in the browser. I’ve used [Server Side Rendering](https://reactjs.org/docs/react-dom-server.html) solutions in the past based on [Node](https://nodejs.org/en/) and [Express](https://expressjs.com/), but over time they run into some of the same performance issues that PHP does. Server load is always a significant issue on dynamically rendered high-traffic applications, because they typically need to interact with a variety of other systems to construct each page. As concurrent requests grow, so does response time. |
|
This is an extremely well-written post. A couple of small comments -- make sure you change "I" to "we" throughout the article and then 👍 |
|
Great feedback! Thank you! I'll update this evening. |
|
Ping on this @bkonkle -- we'd love to post! |
|
Ping @bkonkle :-) |
|
Sorry about that! I got buried in work, but I've dug my way out! Working on this now. |
|
@calcsam All set - let me know if you have other suggestions and I can commit to getting them updated this weekend. 👍 Thanks! |
|
Looks great! Gonna merge this! |
No description provided.