[www] Blog Adding "Why Narative loves Gatsby" post #5883
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Deploy preview for using-drupal ready! Built with commit 5b106eb |
|
Deploy preview for gatsbygram ready! Built with commit 3d09908 |
|
Thanks @brotzky! Preview url: https://deploy-preview-5883--gatsbyjs.netlify.com/blog/2018-06-18-why-narative-loves-gatsby/ It looks like there's a space in the filename of the plugins image, which is preventing it from loading. |
m-allanson
reviewed
Jun 15, 2018
|
|
||
| Gatsby allows our team to use the powerful React API when creating page based websites with almost no drawbacks. All the principles and techniques we've learned from using React for the last few years can be leveraged with Gatsby. This has enabled us to create a team that is extremely dynamic and cohesive without the worry of creating silos or losing knowledge across teams. Our team is able to learn once, write everywhere. With an engineering team that's familiar with React and Gatsby we're able to tackle more problems faster, which is highly beneficial to our partners and the services we offer. | ||
|
|
||
| One concern we had when adopting Gatsby is that page based websites are not the same web apps. Even though we're using similar tools to build them there are different principles that drive each type of development. Luckily, our team doesn't have to worry about that problem, because the team behind Gatsby is focused on delivering the perfect experience to end users for us. The Gatsby team has baked in all the necessary features to make our websites fast and up to standard. |
There was a problem hiding this comment.
missing as?
are not the same as web apps
|
|
||
| Narative strives for technical excellence for all its products, which can be achieved with React, Gatsby, and GraphQL for us. We've landed on a solution that allows our team to stay cohesive and flexible. Thanks to the popularization of React and the principles behind it Narative has been able to build page based websites and web apps with the same expertise. In the past, it was hard to share knowledge and tools between page based websites and web apps but now there's very little difference. | ||
|
|
||
| Gatsby streamlines our process with an excellent developer experience and all the features you could ask for in 2018. The heavy lifting of delivering a technically sound website with performance that users will love has slowly shifted towards frameworks such as Gatsby, which has freed up our team to focus on even better best experiences and products. |
There was a problem hiding this comment.
remove best from better best?
|
@m-allanson thanks so much! great suggestions. pushed up a commit to resolve those.
|
m-allanson
previously approved these changes
Jun 15, 2018
…lines :-) Super nice post!
KyleAMathews
added a commit
that referenced
this pull request
Jun 17, 2018
* Update gatsby-starters.md (#5917) New Gatsby Starter Project: Gatsby eCommerce store using the Moltin eCommerce API * Adding Jersey Watch to list of Gatsby sites (#5923) * [www] Blog Adding "Why Narative loves Gatsby" post (#5883) * Adding why narative loves gatsby blog post * Fixing grammar and removing space from start of image filename * Made a few small copy changes + added a bit of emphasis on the money lines :-) Super nice post! * Fix markdown link syntax * Update yarn.lock + prettier * Publish - gatsby-image@1.0.54 - gatsby-plugin-catch-links@1.0.24 - gatsby-plugin-google-tagmanager@1.0.19 - gatsby-plugin-manifest@1.0.27 - gatsby-plugin-postcss-sass@1.0.22 - gatsby-plugin-sharp@1.6.48 - gatsby-plugin-stylus@1.1.21 - gatsby-plugin-typography@1.7.19 - gatsby-remark-autolink-headers@1.4.19 - gatsby-remark-code-repls@1.0.11 - gatsby-remark-copy-linked-files@1.5.37 - gatsby-remark-embed-snippet@2.0.2 - gatsby-remark-images-contentful@1.0.2 - gatsby-remark-images@1.5.67 - gatsby-remark-prismjs@2.0.4 - gatsby-remark-responsive-iframe@1.4.20 - gatsby-source-contentful@1.3.54 - gatsby-source-drupal@2.0.41 - gatsby-source-filesystem@1.5.39 - gatsby-source-lever@1.0.11 - gatsby-source-mongodb@1.5.21 - gatsby-source-wordpress@2.0.92 - gatsby-transformer-excel@1.0.9 - gatsby-transformer-json@1.0.20 - gatsby-transformer-remark@1.7.44 - gatsby-transformer-sharp@1.6.27 - gatsby-transformer-sqip@0.0.11 - gatsby-transformer-yaml@1.5.18 - gatsby@1.9.272 * Merge from master * Run prettier * Fix merge errors * Publish - gatsby-link@2.0.0-alpha.3 - gatsby-plugin-catch-links@2.0.2-alpha.3 - gatsby-plugin-page-creator@2.0.0-alpha.3 - gatsby-remark-images-contentful@2.0.0-alpha.3 - gatsby@2.0.0-alpha.60 * Fix lint errors * Specify next as gatsby-link version * Publish - gatsby@2.0.0-alpha.61
|
Hiya @brotzky! 👋 This is definitely late, but on behalf of the entire Gatsby community, I wanted to say thank you for being here. Gatsby is built by awesome people like you. Let us say “thanks” in two ways:
If you have questions, please don’t hesitate to reach out to us: tweet at @gatsbyjs and we’ll come a-runnin’. Thanks again! 💪💜 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi!
I've shared this blog post with @KyleAMathews through twitter and he asked if we'd like to add it to the official Gatsby blog. So, I'd like to add a blog post we've been working on recently Narative, "Why Narative loves Gatsby".
If possible, this would be amazing to have live by June 18th. Otherwise, any time that fits your schedule at Gatsby!
Let me know if I missed anything. First PR to Gatsby!
We're excited to be using your software :). If there's any way we can lend our skills to help improve it please let us know! For now, we'd like to share some kind words through this blog post.
✌️Narative