Redesign v6
Published: ....
Last modified: ....
Share this post on BlueskySee discussion on Bluesky
I have recently been looking into the many projects and tools that Zeit has been working on. If you don't know what Zeit is, its the company behind many cool projects like hyper (the terminal built with web technologies), Now a platform for deployments, and also Nextjs a server rendered react framework with support for routing both on the client and on the server. I decided to up my plan from free to the payed option on Now to give it a try. I have been looking at ways to cut down on my dependency on Github Pages because of limitations they have implemented and also because of the lack in server side control.
So after I had ponied up the $14.99 for a month of premium Now usage, I decided it was time to make use of that. I decided to start from scratch on my personal website and build it from Nextjs from the ground up. If you are reading this on matthamlin.me right now then you are experiencing that rewrite at the moment.
This is the first website I have made with Next, it took some time to learn how to use it properly and how to migrate my old structure over to using it too. Prior to this I did a full re-write in react and react-router which I thought was pretty advanced at the time. But now that I have used Next to handle all this it has made it so much easier to build things.
The core concept of Next is that your website lives in two core root folders,
pages
and static
, there are no limitations on what folders you make or use
but these are the two most common folders. Pages is where are your root page
endpoints will live, so if I put a test.js
file within there, then the
endpoint of mydomain.com/test
will render out the react component that that
file exports. Static on the other hand is where you store static assets like
.html files, images, external css, videos, etc. You can deploy a site with Next
and just some HTML if you wanted to by throwing an index.html file within
/static
.
On the css side of things I had to change my current implementation quite a bit.
I moved my css imports into template strings within <style jsx>
tags. This
means that the styles within the tag are scoped locally to the component. For
some things I had to use the Global scope within these style tags. A good reason
for this is when html is set within elements manually (Like how this page is
rendered from markdown to html), or if you want to style whole components within
another component.
I plan on converting my other domain goexploring.today
to use Next and Now in
the coming weeks, and also plan on launching another site for documenting my
families trip to New Zealand coming up really soon.
Let me know what you think about the site. In an ideal world it should just work like before.
Tags:
Related Posts
Redesign
Thoughts
Next.js
Published: ....
A quick tip to implementing CSS theming that's compatible with Server Side Rendered applications!
Published: ....
Some rough thoughts on building a file-system routing based web application
Published: ....
A quick look at a small but powerful pattern I've been leveraging as of late!
Published: ....
This is a quick post noting that Next.js should now work with Deno v2!
Published: ....
Feature toggles are often underused by most software development teams, and yet offer so much value during not only feature development but also refactors
Published: ....
webpack, and tools built on it like Next.js, don't support true dynamic imports, but I found a way to trick the system!
Published: ....
A(nother) deep dive into one of my recent side projects; tails - a plain and simple cocktail recipe app.
Published: ....
A deep dive into one of my recent side projects; microfibre - a minimal text posting application
Web Development
Published: ....
I recently launched a rewrite and redesign of this personal website, I figured I'd talk a bit about the changes and new features that I added along the way!
Published: ....
A quick tip to implementing CSS theming that's compatible with Server Side Rendered applications!
Published: ....
A brief overview on how we launched The Bikeshed Podcast, including a deep dive in our recording and distribution workflows!
Published: ....
A quick tip outlining how to provide specific TypeScript type definitions for a local module!
Published: ....
Some rough thoughts on building a file-system routing based web application
Published: ....
Slicing software: why vertical is better than horizontal.
Published: ....
What if you could author an entire web application in a single file?
Published: ....
A quick way to handle resetting internal state in components when a parent form is submitted!
Published: ....
A brief look at Import Maps and package.json#imports to support isomorphic JavaScript applications!
Published: ....
A collection of tech talks that I regularly re-watch and also recommend to everyone!
Published: ....
Some features and functionality that I'd like within a React Server Component compatible framework.
Published: ....
A (running) collection of Bluesky tips, tools, packages, and other misc things!
Published: ....
A quick look at a small but powerful pattern I've been leveraging as of late!
Published: ....
A proposal for a minimal variant of TypeScript!
Published: ....
Sharing a few core recommendations when working within monorepos to make your life easier!
Published: ....
This is a quick post noting that Next.js should now work with Deno v2!
Published: ....
React components have a fundamental contract that is often unstated in their implementation, and you should know about it!
Published: ....
Replace that old useState and useEffect combo for a new and better option!
Published: ....
A quick look at the applications and tools that I (generally) use day to day for web development!
Published: ....
There are a variety of different markdown "standards" out there, and sometimes they're not all that consistent
Published: ....
Proposing a solution for sharing core "business" logic across services!
Published: ....
There's a common gotcha when creating Web Request and Response instances with Headers!
Published: ....
Feature toggles are often underused by most software development teams, and yet offer so much value during not only feature development but also refactors
Published: ....
A quick introduction to my new side project, hohoro. An incremental JS/TS library build tool!
Published: ....
Two neat tricks for enhancing your site's favicon!
Published: ....
The various risks and pitfalls of open source software run by corporations.
Published: ....
A monorepo template for managing a library and documentation together.
Published: ....
How we solved an almost show-stopping production bug, and how you can avoid it in your own projects.
Published: ....
A(nother) deep dive into one of my recent side projects; tails - a plain and simple cocktail recipe app.
Published: ....
When did semver major changes become so scary?
Published: ....
Leveraging service monitors properly to improve service observability.
Published: ....
A brief recap of how Wayfair changed it's CSS approach not once but twice in the span of 5 years!
Published: ....
A deep dive into one of my recent side projects; microfibre - a minimal text posting application
Published: ....
Pair programming can be good sometimes - but not all the time
Published: ....
A few thoughts on using Suspense with GraphQL to optimize application data loading
Published: ....
A few thoughts on what to do after you launch a new project
Published: ....
A few quick thoughts on burn out and taking a break
Published: ....
A few thoughts on managing complex UI component state within React
Published: ....
A quick overview of the new lifecycle methods introduced in React 16.3
Published: ....
A few thoughts and patterns for using styled-jsx or other CSS-in-JS solutions
Published: ....
A few weird things about JavaScript
Published: ....
Building a calendar web application