vite-imagetools VS winter

The first thing is to install vite-imagetools from https://github.com/JonasKruckenberg/imagetools

Automatic image optimization via vite-imagetools.

The closest solution I’ve found is hacking something together yourself with vite-imagetools

The projects this solutions works with are customised Sveltekit projects I made. It has everything: markdown parser using Mdsvex, image converting tool using vite-imagetools, it has toml parser, and of course live preview and lots of other smaller things like markdown directives.

#2 - I'm not sure about the performance and/or resource usage implication around importing over 100 images like this. Would all of these images get bundled and included in the production build? The upside here is that something like vite-imagetools could be used if/when needed.

Hello HN,

I had some christmas free time over the last two weeks (Merry Christmas btw ;-)) and used that time to completely recreate the website of my app[1]. I used all the fancy new tools. I didn't know some of them when I started.

What was my goal?

* Pretty website

* Blazing fast

* Mobile first

* SSR

* Webp support

* Generally all the best website practices (high lighthouse score)

What did I use?

* Tailwindcss (https://tailwindcss.com/)

* Tailwind Components (https://tailwindui.com/)

* React (https://reactjs.org/)

* ViteJs (https://vitejs.dev/)

* Kubernetes (https://kubernetes.io/)

Well what can I say. I hate creating websites, but this was an awesome experience. Never have I created a website more efficiently. Tailwindcss + Components is just the best. ViteJS is so so so much easier to setup compared to webpack and has SSR support on top of it. React has been around somewhat longer and I did a lot of projects with it, so that was a nobrainer. Special thanks to all the people who created these awesome tools.

PS: If you work with lots of images, do yourself a favor and use something like https://github.com/JonasKruckenberg/imagetools. It saved me hours of dreadful work.

[1] https://stockevents.app

Spent the better part of today attempting to find a working alternative to svelte-images, which I had been using in Sapper, but found was not working in SvelteKit. Was referred to [vite-imagetools](https://github.com/JonasKruckenberg/vite-imagetools) on discord, which is a vite plugin that dynamically import and transform images (srcset). Here are the steps required to integrate vite-imagetools with SvelteKit:

Beside Symfony there is Laravel Framework , I will not go into deep difference between this frameworks as it really is just taste of what your team likes more (active record vs datamapper, facade/helpers vs dependency injection, blade vs twig, ...), as already mention above this kind of CMS make sense if Website is just one part of your application and you have to build more then just a simple digital business card / website. In Laravel world there are CMS like October CMS / Winter CMS, which target the same providing a CMS based on the Full Stack Larave framework and give you all features of that framework. Another already mention CMS in Laravel world is Statmatic.

Chances are a lightweight CMS already exists. Winter CMS is one such option.

Or Winter CMS (https://wintercms.com/) ;)

As someone who dabbled in PHP but is mostly a self-taught JS hobbyist dev, I have been using and loving Directus (https://directus.io) since around the time they switched to Node. Development velocity is exceptional with new features released every couple of weeks and bugfixes/enhancements even more frequent, the community and core team is fantastic, and I like the fact that if I ever decide to switch to another CMS for some reason, there's no real import/export process, I just delete the directus_tables in my database, and done.

Pocketbase (https://pocketbase.io/) piqued my interest after seeing it here and on ProductHunt, but I don't think it would be the right call for a client before it hits a stable release.

I also very much enjoyed OctoberCMS (although it has its quirks), but there was a fairly acrimonious split in the community there, and OctoberCMS is no longer open source, and I haven't used the fork (WinterCMS: https://wintercms.com/)

I enjoyed using Apostrophe (https://apostrophecms.com/) for a while, but ultimately I felt like I was doing a lot of stuff in a way that didn't come naturally to me, and although Mongo seems a logical choice when you look at Apostrophe's page model, it worried me a bit that the data would not be easy to move if I ever wanted to.

I'm biased, but it might be worth taking a look at Winter CMS. It's built on Laravel, so you get everything you would with Laravel but it also has some pretty powerful features on top of what you get out of the box with Laravel. Its plugin system and extensibility is also second to none. It's different from a few of the other options though in that you don't add it to an existing project, you build your projects from the start in it.

Winter CMS is an open source fork of OctoberCMS. They've just put Laravel 9 support in place as well.

If you're looking at October I'd give Winter a look too (https://wintercms.com), October is no longer open source and Winter is the open source fork of October. (Disclaimer: I'm the lead maintainer for Winter CMS)

Winter CMS? Laravel based and very developer friendly! https://wintercms.com/

If you're thinking of using Bolt but would also like to have access to the power of Laravel, I'd recommend taking a look at Winter CMS (open source fork of October CMS, built on Laravel / Symfony): https://wintercms.com

Have you ever looked at Winter CMS? https://wintercms.com it's a CMS built on Laravel that's super easy to customize and add your exact needs to.