I might be next. Hey, am I?
I'm kb and I develop websites for my micro company K16E, Inc. I build with Nuxt exclusively with everything CSS coming from the beautiful Tailwind.
I hit on the "jamstack" way of building websites in year 2018, with Jekyll being my first love. I still have a couple client projects in that. I eventually fell in love with Vuejs and Nuxt was just the natural evolution. I did have a stint with Gridsome, but it ended all too quickly.
If you've noticed, all along, I haven't quite mentioned how I get content into the websites I build - CMS. To be honest this has been a pain, no solution has really worked for me. This may be why I'm here on Prismic, and I'm hoping it should do it for me as far modeling my content and "slicing" it into my design is concerned. I've used a lot of the "headless" CMS's and I'm really wanna stick with one that works at least 90% of the way, for most things I do with content.
First impression with Prismic, welcome Slice Machine I like it...but there's a few areas I'd love some improvements, and also currently stuck on a use-case that is critical to how I consume content - relationships to other content/routes.
I would also love Prismic to do a lot better with its docs, I might have a suggestion or two on how to improve the language and presentation along with examples, even some of them drawn from a forum like this one, so users don't study all the docs and still can't do much with the software.
In my estimation, a CMS is really a system for developers, not website owners, perhaps not even designers. These later ones only need to be able to edit content, create new pages based on pre-built comps/layouts, and that type thing. So, I'd really love more recipes for different ways developers can get the best use out of Prismic.
This is supposed to be only an intro...I'm typing too much