tailwind-nextjs-starter-blog
tailwind-nextjs-starter-blog copied to clipboard
timlrx
How can we update our cloned project to the latest version of this source repository?
It is will be very nice if we can keep up with the latest version of this repository on our blog. So, we do not miss the new feature.
Once you have modified the template a bit, keeping track of the changes with fork and sync becomes a bit cumbersome. This is because you also have to consider changes for components you don't care about. Also merging becomes more and more complicated the more you modify the template.
An - in my opinion better - approach would be to split the template into a collection of packages that can be included, updated or forked all independent of each other. I detailed the idea a bit more in https://github.com/timlrx/tailwind-nextjs-starter-blog/discussions/275#discussioncomment-2227502.
Yes, that's what v2 is shaping up to be - a collection of packages that you can install via npm with various convenient CLI commands that you can use to bootstrap a content heavy site. Sorry, it's taking a while...
I agree that it is tedious to update to upstream changes in the repo - I don't even do it on the blogs that I run.
Is there anyway we can help to develop the v2 @timlrx ? I would like to help, I really love the idea of this project.
Let me try to get the new version out and it will be easier to contribute from there. Thanks for your interest!
hey @timlrx, when can we expect v2 to be available?
I'm a tourist here who was about to fork this repo but if v2 launch is around the corner I might as well wait.
Hi @reubence, it's around the corner - end of the week. But, it will be an alpha release so expect breaking changes :)
If anyone is tracking this issue, I fixed a bunch of issues related to packaging and the new version should be relatively stable now, so you can just use the https://github.com/timlrx/pliny packages directly.