I got a 13 sierra 1500 with some mods i want to add a overcab camper it weights 1980 sticker on my truck is around 1500 im around 500lbs over with a full camper means gas food and everything so at max ill be 500 over is that over kill???
35s on 17s
Headers
Tranny cooler
Intake
Exhaust
Tuned
The Payload website template uses a 1-to-1 blocks to website mapping. This is reminiscent of Wordpress where the data inside the CMS controls exactly how the webpage design looks.
Since Payload is flexible, technically any other structure is possible.
For example:
Any visual element of the website would need a corresponding block created inside the CMS and the editor picks the block inside the admin panel. Changing anything including colors is done in the admin panel.
Like #3 but the CMS is unstructured and contains only a few generic blocks for generic list data or generic long form data.
The website is separately designed and pulls data from the CMS based on an ID.
Essentially the CMS is barely designed and just serves as a bare bones editor GUI.
Treat the CMS as a rich content store filled with FAQs, hero sections, call-to-actions, product descriptions but the actual appearance of the website is not determined by the CMS. The website designer can pull data from multiple points of the CMS and omit things that they don’t like.
Your website is separately designed but pulls whatever data it wants from the store.
I am trying to implement the MCP plugin to create blog posts drafts. In order to allow adding the hero image, I have to enable the media collection in the plugin; however, the tool payload_createMedia throws the error:
ERROR: [payload-mcp] Error creating resource in media: No files were uploaded.
It seems that either the tool does not allow performing the upload, or the model is not capable. I cannot upload the file using the REST API as the collection requires the user to be authenticated, with this in mind, do i need to use an API key strategy to authenticate and then upload the file via REST API and only use the MCP for the metadata?
Has anyone used the MCP for something similar and can provide some guidance?
I'm trying to figure out how to deal with repeated strings in content.
For example, I'm thinking about phone numbers or e-mail addresses that may appear on many pages but are always the same.
If I place these directly in the content, it means going back through every page if the phone or e-mail ever changes and the chances of missing a few are high on sites with a lot of pages that reference them.
Other CMS's provide ways around this like using replacement tokens so that the strings can be defined globally and then referenced via tokens in the content. Then in the final content, the token is replaced with the actual string. WordPress "short codes" are an example of this: https://codex.wordpress.org/Shortcode
Has anyone implemented something like this in Payload? I'd like to hear your approach if so.
[Design Feedback] My second Payload CMS website, built from the Website Template
This is my second website built with Payload CMS, using the Website Template as the starting point.
Eventblok.com
I wanted to share it here because I have really enjoyed how flexible the template has been from a design point of view. It gave me a strong structural foundation, but I was still able to take the visual direction much further and make it feel like its own sales and marketing site rather than a reskinned starter.
For this one, I aimed for a darker, more editorial and premium feel, with a little event-production energy rather than the usual generic SaaS look.
The frontend is built with Tailwind and Framer Motion, and I also made a small theme customiser so I can test different colour palettes and visual directions while refining the brand.
I am also using Payload for much more than the website itself. The wider project is EventBlok, an event operations platform for managing things such as agendas, speakers, showflows and live-event workflows. That is one reason I chose Payload in the first place: I wanted a flexible foundation that could support both a polished public-facing site and a more substantial product over time.
I have attached a work-in-progress screenshot of the audience-facing login area too.
I would genuinely value design feedback from other Payload users:
This is mainly a design-feedback post rather than a product promo. I have really liked using Payload as a flexible foundation for building something with its own visual identity.
eventblok.com
Just shipped payload-content-translator plugin v0.3 🎉
Rich text block-level elements are now translated as one unit using segment markers. So inline formatting stays aligned across locales. Plus more fixes!
Running a multi-locale payload setup? Give it a try: payload-content-translator V3 GitHub Release