blog/release-of-tailwind-nextjs-starter-blog-v2

[giscus[bot]]

blog/release-of-tailwind-nextjs-starter-blog-v2

Release of Tailwind Nextjs Starter Blog template v2.0, refactored with Nextjs App directory and React Server Components setup. Discover the new features and how to migrate from V1.

https://tailwind-nextjs-starter-blog.vercel.app/blog/release-of-tailwind-nextjs-starter-blog-v2.0

[timlrx]

Welcome to v2 😎

[SangeetAgarwal]

Hello @timlrx Thanks for the amazing work you've done! I had one very quick question about the way blogs are being generated with content layer.

In version 1.0 the blogs were being generated each time they were accessed via mdx-bundler where as in version 2.0, they would be generated at build time and stored in the .contentlayer/generated folder. So, say you wanted to edit a blog post once it was published then that would mean rebuilding the app all over again in v2 where as in v1 it would pick up the changes without having to rebuild the entire app.

Again, this isn't an issue at all, or a criticism and the only reason I'm asking this question is to get a better understanding about the way things were handled in v1 vs v2 and this would also help me understand what's beneath the hood so this is purely from a learning perspective, and probably in the present situation this really doesn't matter since the mdx files are part of the compiled code in both versions but suppose we were getting the mdx data at run time via (say) an API call or perhaps it was stored in a database.

Again, thanks for all the incredible work you've open sourced. Much appreciated.

Best
-Sangeet

[timlrx]

You are right that in v1, the blog pages are generated each time a route is encountered. This includes all meta information e.g. total number of posts, what's the previous / next post etc. In v2, this is generated once before the build, thanks to contentlayer and each page just retrieves the required information from the json file during the build.

In both cases, editing a blog or adding a new entry requires building the entire website again. With v2, there's actually less repetition in the build process. Another benefit - in dev, contentlayer watches the data directory and only rebuilds a specific post if it has changed.

[mudgal-m]

please guide me how i create a new blog (in v1 it was easy to create using script) and update the search.json to show in kbar search and also one more thing that in kbar search box there is homepage which redirect to homepage and i want to add more pages in search like about, projects etc.
And I tried algolia search but it was showing results which redirecting to its official site not out docs..

[timlrx]

To create a new blog post, I find it easier just to copy and paste an old one and edit the fields from there.

To customize the kbar search, I recommend creating your own version of SearchProvider.tsx that looks like this:

'use client'

import { KBarSearchProvider } from 'pliny/search/KBar'
import { useRouter } from 'next/navigation'

export const SearchProvider = ({ children }) => {
  const router = useRouter()
  return (
    <KBarSearchProvider
      kbarConfig={{
        searchDocumentsPath: 'search.json',
        defaultActions: [
          {
            id: 'homepage',
            name: 'Homepage',
            keywords: '',
            section: 'Home',
            perform: () => router.push('/'),
          },
          {
            id: 'projects',
            name: 'Projects',
            keywords: '',
            section: 'Home',
            perform: () => router.push('/projects'),
          },
        ],
      }}
    >
      {children}
    </KBarSearchProvider>
  )
}

You can pass in other routes to defaultActions or change it to an empty array if you do not wish to display anything. Replace the SearchProvider in the main layout.tsx with this component.

For algolia search, you need to apply here. Once you are approved, you can update AppId and apiKey in the config accordingly.

[mudgal-m]

Alright and thank you for the guide and this amazing template.

[mudgalz]

[
{
"id": "test",
"name": "testing",
"keywords": "file",
"path": "about"
}
]
i dont know whats wrong but search.json not generating automatically. so i tried to add manually some data. but its saying invalid date so can you tell me what are the required fileds to include for a post and from where i can edit them, i even tried to find in kbar in plenty but couldnt find.

[tszhong0411]

Great works! ❤️

[Susmita-Dey]

Good job

[elvoceouma]

I really like this blog template, working on a dashboard that can be used to write and post the articles

[boychawin]

21212

[reivajpg]

Hello, could this template work on Github Pages?

[IkboljonMe]

I am using this repo thnx

[DemuraAIdev]

hate Plinyi i can see the code like 20% code :(

[felipe-sbm]

Nice bro 👍🏽

[syan-dev]

Thank you so much for this

[Amirumna]

test

[Ist14k]

bgggg

[Tung-hehe]

Nice bro

[alestacul60]

uytytyuturutyurtuyu

[ryanfitton]

Test

[feroz39]

xcxcxc