Where the design community meets.
Founder at TRBL, Founder at Payload CMS Joined almost 9 years ago
No prob Joe! I would be thrilled to hear your feedback. My team and I are looking to make Payload everything that ACF ever was, without the WP!
We are wondering that at the studio currently
You and I are of very similar mindsets to the point of it being scary.
I don't have strong opinions regarding if it is ready for use with a typical PHP-based frontend, but for a use-case similar to our specific set of circumstances, I wouldn't recommend. It's too bad, really, because we actually like the UI.
I wrote this after my team hit a wall while trying to use the new WordPress Gutenberg editor. We build ReactJS sites that consume data from WP REST APIs, and as Gutenberg works now, it bundles all block data into a single HTML content string - which is difficult, if not stupid, to parse into React components on the frontend.
Hope you find it interesting!
Wow, I may be the lone ranger here but I love it and I think it's overdue. Literally zero complaints from me and I've been using it for months through the beta program.
I have been in beta for a month or two and I LOVE it. Big fan of the dark UI over here. No real problems since earlier on in the beta except for a slight issue with the font weight rendering.
I like it and I'm not a fan of Material Design. It seems minimal, fresh, and out of the way. The subtle color changes of the tab bar are nice, too.
I've actually started to do this as well, I think it provides a good parity between small and large screen sizes. But, I don't like that they haven't constrained their header width at all. Bothers me when content is restricted and headers / footers are not.
James hasn't upvoted anything yet.
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.
I am a co-founder of Payload CMS and I also run a design studio called TRBL where we specialize in custom UX and full-stack development, typically in TypeScript front to back.
I have been working on a new video series that describes, in detail, how professional design firms go about building completely custom websites using a headless CMS, React, and TypeScript. This series is going to be a bit different than the typical to-do style videos and I want it to show a much deeper level of project approach and code mentality, all the way from how to scaffold centralized, reusable TypeScript types to how to build websites with React layout-building components.
One of my other goals with this series is to provide a window into how professional design firms go about delivering sites with a lot of value to clients that absolutely need that level of quality, and are willing to pay for it. The site that we'll be building is actual, real-world work, and although it's more of a small-to-medium budget for us, the principles involved can be used to deliver websites where clients will happily pay $100K+, because they need it.
I often times see developers posting their work that they've poured their hearts and souls into, asking if $2-3K is a big enough budget for them to have charged. I say hell no. Not that there's anything wrong with smaller budget websites, but unless you're incredibly efficient, you should be using an off-the-shelf solution like Squarespace. There's absolutely nothing wrong with that.
My moral is: there is a segment of the market that still absolutely requires high-end development standards and approaches, and it's alive and well.
This is episode 1 - and it's my first ever YouTube video. I would appreciate any candid feedback that this community has for me, and if you haven't already, please check out Payload CMS - we've gotten incredibly positive feedback from our users so far and are committed to making it the best choice for JS / TS developers in 2021+.