Juxt
免費訂閱
文章 · 收錄於 2024.02
MGN-BLOG-MIGRATIN
索引 · 部落格

Migrating from Gatsby to Next.js 14

2 分鐘閱讀

This website has entered v3 of its iteration! v2 was created using Gatsby and integrated with my previous design resources dojo.today. Entering v3, I'm migrating the website from Gatsby to Next.js 14!

Things that I'm considering during the revamp:

What's the best approach to decide where should the content saved?

For me there are two key pillar of content that require to migrate from this website

  1. Blog articles on juxtdesign.cc that previously saved as Markdown stored on Github
  2. List of bookmarks that previously stored on Prismic.io

Ease of Access <--> Ease of Development

My conclusion have based on the follow questions:

  1. Do you want to create, edit and delete your content on mobile?
  2. How many images do you want to attach per record?
  3. Is there long paragraph of content that need to be processed with styling, image support?

| | Mobile Edit | Image Per Record | Article | | --------- | ----------- | ---------------- | ------- | | Blog | ✅ ❌ | >1 | ✅ | | Resources | ❌ | 1 | ❌ |

With Obsidian support of Properties, it's way easier to do simple data mark up (e.g. Boolean on draft's status, set title, date, categories and tags)

索引 · 相關文章

延伸閱讀

文章 · 01
預覽圖
nextjs
PrevNext Blog Component for NextJS Using ContentLayer

Using ContentLayer, it's easy to create a Prev & Next component if you want to encourage users to read one blog article and then the order. All it takes are two simple step. 1. Create related posts logic on blog single page You should already have blog single page setup in the file like `/blog/[slug].tsx`. In addition to it you will need to create an index of posts, assuming you want to build a ch

部落格
文章 · 02
預覽圖
nextjs
NextJS Modal with shadcn for Intercepting and Parallel Routes

Intercepting Routes was a new feature firstly released in NextJS 13. Currently NextJS file-based route system is like a sitemap, there are no specific order on how the route is read or triggered. In NextJS documentation, it also wrote: Note that the `(..)` convention is based on _route segments_, not the file-system. Intercepting route thinks differently by thinking how would a user enters a route

部落格