Introduction

Today I'm going to be doing a pretty deep dive on the landing page technology we used to launch and manage Kore Tools.

Let's get right into it!

Tech Stack

The landing page for Kore Tools uses some new tech to Kore Tools: NextJS and Tailwind!

Although these aren't entirely new (after all, this blog is built on the same stack!) it was the most custom implementation I've done on the frontend since I started working on Kore Tools. It still started from a template, but was more heavily modified than the blog.

These technologies have been very interesting to work with. I can highly recommend the NextJS getting started tutorial, as well as the strength of the docs for Tailwind has been fantastic. It made building the landing page a breeze when compared to previous frontend work I've been involved in.

Hosting

Both the blog and the landing page utilize the AWS App Runner service, with DNS services provided by Route 53 and analytics provided by Google Analytics. This allows us to provision the applications quickly, and can deploy changes to production in just a few minutes. Overall, working with these services has been very efficient.

Due to connectivity reasons and cost, the rest of the platform (and the Kore Tools main UI itself) will not be hosted on App Runner. I'll write a separate blog article on the overall architecture (which contains several components) and hosting design for the rest of the platform for another time.

Going Forward

I'll carry the learnings from this blog and the landing page on into building the UI application frontend for Kore Tools, which will (hopefully!) span multiple products and many features that Kore Tools provides. First on the docket is launching Kore Cache, iterating on that and evaluating other product opportunities (and especially those that can leverage Kore Cache ourselves).

You can email me questions at matt@kore-tools.com, or visit us on Twitter or me personally on Twitter any time!