At Third and Grove, we can’t help but blend the best technologies in an effort to create modern web front ends. Luckily for us, BigCommerce also likes to push the envelope. So far we have partnered with BigCommerce on projects like Drupal’s ACF reference architecture and the Gatsby source plugin which supports the game-changing Gatsby preview.
Our latest challenge arose from conversations leading up to JAMStack Conference SF. We kicked ideas around what it would take to eliminate pain points when building an ecomm site. Especially pain points keeping people from using JAMStack. …
A rebuke of “hello world”, in Node, Go, Python, and Rust.
This will serve as both an announcement and an explanation. An announcement that our Accounts-UI react/redux app will be open to the public.
We are looking forward to having this work open for developers to view, learn from, and even inform us on places where we could make improvements. In the process of this build we have made decisions, many in fact that deserve a walk through.
There are about 25000 lines of code in this app, so we can only cover some ideas in this article. …
Recursion is a concept that can be hard to grasp at first. So I’ve asked Mr Meeseeks to help me out. If you’re aware of this lovely character from the cartoon Rick and Morty, you may know where I’m going. If not, Mr Meeseeks is a magical character that is able to grant wishes. If you can, take a look at the episode. If not here’s a synopsis from wikipedia:
When the rest of the Smith family asks Rick for solutions to several mundane problems, he gives the family a Meeseeks Box, a gadget capable of causing helpful beings named…
I use Webpack.
I have used it in create-react-app (CRA) through react-scripts, and in other projects that have custom configs set up before I lay a finger on them. But I don’t really know how it works. I look at the configs, I understand some of the ideas behind it, but I’ve never written a Webpack config, or tried to set my own up. That is what this article will be about. Going from no config, to a basic functioning setup that will bundle HTML, CSS, and Javascript.
My goal is to demystify as much of the process as possible…
Testing, how does it work? Well, to be honest, I don’t know much about it. I have used jest a handful of times, I have manually tested UI, and done my best to error-proof (go ahead, laugh at that) response handlers in my front end code. But as for actually making a good habit of testing the overall functionality of my code I have fallen, staggeringly short of my goals. The main hurdle for me was getting down to what needs to be tested. There are schools of thought on this, but my opinion would follow along with Guillermo Rauch…
To get things started, Ive created a git repo that I’ll be referencing later in the article. You can fork that here.
We’ll first need to have an endpoint to consume. With a new account on Zesty.io the first thing it will ask you to do is create a web property. Once you’ve named your property it will ask about a blueprint. Since we are using Zesty as a headless CMS we don’t have to worry about that, select one, or none and the manager app should open up from that point. Now that we have a web property, we…
