You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Check out the alpha version of Pliny - the successor to tailwind-nexjs-starter-blog. It accomplished some of the things I set out to do in #275 including:
Modular components
Modular layouts
Contentlayer to define and process md/mdx files
CLI to bootstrap new starters and add content slices and themes
Tooling wise, it is very much inspired and adapted from Blitzjs. This allows recipes and starters to be defined and maintained in typescript while still being available in javascript and solves the 2 language, 3 branch problem that I am having in this repository. With much of the refactoring and tooling complete, I believe that it will set the grounds for new features, content types and themes to be created by the community! Hence, I decided to spin it off as a separate project and manage it as a monorepo.
What's going to happen to tailwind-nextjs-starter-blog? I might just update it from time to time with:
pliny new --no-ts --template=starter-blog tailwind-nextjs-starter-blog
The first update would probably be quite a significant change as much of the logic is now abstracted away and I would be using contentlayer only in new versions to come. Otherwise, most of the features and design remains the same.
There are some items in my to do list for the new project. If you wish to contribute or comment on the proposals, see: https://github.com/timlrx/pliny/issues
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi all,
Check out the alpha version of Pliny - the successor to
tailwind-nexjs-starter-blog
. It accomplished some of the things I set out to do in #275 including:Tooling wise, it is very much inspired and adapted from Blitzjs. This allows recipes and starters to be defined and maintained in typescript while still being available in javascript and solves the 2 language, 3 branch problem that I am having in this repository. With much of the refactoring and tooling complete, I believe that it will set the grounds for new features, content types and themes to be created by the community! Hence, I decided to spin it off as a separate project and manage it as a monorepo.
What's going to happen to
tailwind-nextjs-starter-blog
? I might just update it from time to time with:The first update would probably be quite a significant change as much of the logic is now abstracted away and I would be using contentlayer only in new versions to come. Otherwise, most of the features and design remains the same.
There are some items in my to do list for the new project. If you wish to contribute or comment on the proposals, see: https://github.com/timlrx/pliny/issues
Beta Was this translation helpful? Give feedback.
All reactions