Whoever said there was a universal recipe for Elaichi Chai? It makes sense that there would be different recipes. If you are more stringent with the prompt and give it the proper context of what you want the steps to be, you'll arrive at that consistency.
Technologies: Creative Skills, Tech and UX expertise including Figma, Adobe Suite, Proto.io, FCPX, DaVinci Resolve, LLM APIs + Local Models, Midjourney, Recraft, Ideogram, Flux, and Firefly. No-Code via Zapier, Make.com, n8n, and Airtable, AI Dev w/ Cursor, Windsurf, Cline + Dovetail and Useberry
The pitch alone on PayloadCMS shows that this is still a developer-focused CMS. Just look at the difference between the github page, the Payload website, and wordpress.org's landing. This is not purely a marketing difference but a strategic conversation.
I'm all about transitioning CMSes and yet WordPress has got the turnkey part of their open-source platform clear and easy to understand. You can self-host or choose a provider. Payload doesn't make that clear, it's either too dev-centric for running or wants you to "Schedule a Demo" (which is a way to capture enterprise dollars).
What about more consumer-friendly pitches and deployments? Any recommendations on that?
I worry about the criticisms I see about Payload not marketing to marketers and site builders, because as a dev I’m a huge fan and would love to see it thrive.
It’s a fair point, especially given that in so many cases the marketers are the ones procuring the CMS. And people who don’t code at all are a big portion of WP’s market.
My main concern is I’m not sure it’s easy for non-devs to see how much of the PHPish ecosystems are filling gaps in the CMS core. I don’t know how many previous CMSes the Payload folks had used before going about building it, but I’ve built tons of features and templates on most of the big ones, and IMO they did a phenomenal job of boiling it down to exactly what a developer needs to build any feature any customer or employer could ever want.
There’s no need for, say, a heavy SEO plugin. You can just define the fields you want your people to fill out and attach those fields to whatever content types you’d like. Then use those fields in the head when presenting the content out front in whatever frontend you want to use.
On top of that, you have all of the JS ecosystem you can plug right in. Dataviz for custom dashboards, data crunching, video and image processing, all of it. And because you’re not starting with a huge, opinionated plugin/module/contrib, it’s not the clunky and unfun when you need a feature that wasn’t there before. It’s so much easier to build exactly what you need if you’re comfortable with code.
SO much of a serious CMS is just content CRUD, and Payload makes it so simple to define your content types in code, where they objectively should be defined for the sake disaster recovery and reliable builds across all environments.
You can deploy Payload anywhere you can deploy any Nextjs app, and as of v3, you'll be able to deploy it to serverless environments too like Vercel and Netlify. We'll work on adding more deployment guides directly into our docs for various platforms as well to help with this.
Again, we read everyone's feedback about Payload itself and our website so it's very much appreciated and we'll be addressing this gap in how we present ourselves!
edit: I may have misunderstood your initial point, oops
Yeah we're not consumer facing in the way Wordpress is. It's quite a huge gap to fill
I rarely comment on HN but I needed to login and say THANK YOU for this walkthrough of Stage Manager. I didn't even know I could bring in other windows, remove it use Maximize, and more. Just wanted to share my appreciation.
I was actually surprised to find that it works really well for me in the end (contrary to my experience on iPad, where I don’t like using SM). I thought it could reasonably “just work” for casual users on intuitive basis, but most advanced users wouldn’t like it—not having a good concept of how things work is a big barrier, and there is absolutely no documentation or good way of discovering this—so I decided to share my understanding lest Apple kills this feature due to lack of demand.
To add to my description one thing that I noticed just now: there’s a distinction in behavior between “heterogenous” window sets and single-app window sets. For example, if your window set is heterogenous—contains windows of multiple apps—then command-` indeed switches only between windows in the same multi-window set (so you won’t leave that set). On the other hand, if current multi-window set consists only of windows from a single app (e.g., multiple Terminal windows), then command-` will switch between 1) windows in current window set, as well as 2) this app’s windows in other homogenous sets (and standalone windows). I’m not a fan of this particular behavior, because every time it kind of breaks my expectations when I leave a multi-window set due to command-`, but maybe it’s because I got used to thinking that command-` only works within a set too quickly.
Add: and there is an outright bug in that if you use command-` while in some non-English keyboard layouts, it starts command-`’ing infinitely. Guessing Apple might be aware but too lazy to figure out their ticket tracker…
Not sure if OP is accurate here? Please correct me if I’m wrong.
If you export from QuickTime using the Apple Devices preset on export, that is an MP4 profile. Simply export and then rename the file from .m4v to .mp4. I’ve done this countless number of times.
What's this trend of websites making it hard to find screenshots of their app off the bat? Should I really have to sign up just to see how your interface functions/flows?
Also, the link to view the main site is tiny and easily forgettable. I think the site could benefit from a stronger CTA that directs you to what I should do.
"please don't post it on HN and waste everyone elses time."
I didn't know you policed HN and determined what was a waste of time. Last I recall, Upvoting's purpose was that. Your arrogance is a detractor for others to grow and clearly you invested so much time to critique that you wasted your own time on something you didn't care about?
Kudos to you OP, you made something interesting and worth sharing. You've got this guy's attention. Please don't let other detractors mute your hacking.
You clearly misunderstood my post. It may have been badly phrased.
What I meant isn't "don't share it". I meant "get it right before you share it".
I'd have thought the fact I spent a significant amount of time reviewing his implementation and giving well-meant comments would have made that clear. I have no interest in suppressing anyones development -- the more everyone learns, the better for everyone. And do I care about that.
However:
1. HN submissions are 1:many communication. Like, say, mailing lists. For which I've been taught that the sender should make an effort to send a good message. freddiearch didn't put in that effort (see post #11098621). I care about HN, and I'd prefer to see high-quality articles here.
2. Beginners learning about new techniques and then immediately going on to write a low-quality tutorial is a very common phenomenon on the internet. It makes it unnecessarily harder for other beginners, who can't tell. The code didn't work and had several major flaws. It's just not good code to learn Ansible from. (Except for freddiearch of course -- writing bad code, then improving it, is part of learning. Nothing wrong with that! Everyone starts small!)
(@freddiearch: If you read this: I really hope I didn't discourage you from learning about Ansible or anything.)
a.k.a. they made mistakes and then remedied the problem quickly without much controversy. Sounds like the opposite of another trading firm that just collapsed.
These sound like mistakes that many beginner companies can easily make when trying to craft them. Why is there a demand for perfection out of the gate? And why are offers to remedy the situation not given the same kudos?
Hah, I can barely get clients to pay $50/hr an hour for Graphic Design and Web Design work let alone $100/hr. These formula conversions baffle me as well.
