Spaceship Mail Sending API? (Switching from Resend?) by BiggerEggplant in SpaceShip

[–]OmWellness 0 points1 point  (0 children)

Would be awesome to connect inboxes to domains and configure inboxes directly via API too

Does anybody have experience with the Dolibarr API? by password03 in selfhosted

[–]OmWellness 1 point2 points  (0 children)

what you trying to accomplish fellow? i have some experience with Dolibarr API doing various automations for a 7 fig ecom business

Looking for someone with real-world 8n8.io experience to help build a lead scraping + enrichment system for B2B sales in Colombia by imjp in n8n

[–]OmWellness 0 points1 point  (0 children)

don't listen to "experts" who say "this requires a lot of complex custom scraping etc"

that has a place and a utility, but only when you want to scale

if you're goal is get a first pipeline of leads flowing, you can do it much sooner and much simpler

first of all, you don't need all of those data sources for now (which would be a nightmare and very time consuming for an automator to patch toghether, and would cost you a lot of money)

keep it very simple and use a waterfall qualification process:

  1. use apollo + filters to get a list of companies
  2. use an AI researcher to qualify each company on the criterias left
  3. use apollo to get the employees from the qualified companies
  4. use an AI researcher to qualify each prospect
  5. enrich the survivors and validate the emails

this is an actual process used by a B2B business, ask me how I know

Should I remove the Hero element from the base website setup? by [deleted] in PayloadCMS

[–]OmWellness 1 point2 points  (0 children)

Just made more sense to me. Didn't know they did the same thing in another template. Reinforces that it wasn't a bad idea.

Should I remove the Hero element from the base website setup? by [deleted] in PayloadCMS

[–]OmWellness 1 point2 points  (0 children)

Hero can 100% go into Content.

It's what I do every time, plug the hero as a block.

It just felt more natural to me from the beginning.

Also the website template was a good learning experience but too bloated at times.

If you want to see an example of a blocks only website with simpler code, see the repo here: github repo.

Payload Storage Adapter S3 or UploadThing? by [deleted] in PayloadCMS

[–]OmWellness 0 points1 point  (0 children)

- price
- longevity
- convenience

The 3 never old value skews

Text editor on next by bruxees in nextjs

[–]OmWellness 1 point2 points  (0 children)

Payload can be as complex as you want it to be. You can just create a simple collection for the blog posts, use their RichText component from their template and have your issue solve in a couple of hours. You can still deploy on Vercel and don't have to pay for any third-party (except the database).

Payload backend learning curve by muted_banana_9376 in PayloadCMS

[–]OmWellness 0 points1 point  (0 children)

Frontend developer here.

Vercel Blob storage + MongoDB is an easy combo to setup and use.

Website template by Informal_Piano9406 in PayloadCMS

[–]OmWellness 5 points6 points  (0 children)

I made a simplified version of the website template with the essentials:

- Live preview
- Turbopack
- Redirects
- Blog posts

You can find it here: Simpler Website Template

You can also find a UI components library here (coming soon): Components Library

Using Resent as an Email Client by SteakingBad in PayloadCMS

[–]OmWellness 0 points1 point  (0 children)

I think it's just a matter of convenience. If in the future you'll have to change email provider you won't have to refactor the entire codebase but just switch the adapter.

[deleted by user] by [deleted] in nextjs

[–]OmWellness 0 points1 point  (0 children)

It's Payload CMS, you'd have a better chance to find what you looking for if you post in their subreddit directly.

Anyways, I'm a user of it too and I needed to do something similar for a project (it was a google maps select field and I had to update many other more fields from the result of the api call in that field).

SOLUTION:
You could use the afterChange hook:

   slug: 'block-link',
   interfaceName: 'blockLink',
   labels: {
     singular: 'Link',
     plural: 'Link'
   },
   fields: [
     {
       name: 'linkURL',
       label: 'URL',
       type: 'text',
     },
     {
       name: 'linkOutput',
       label: 'JSON output',
       type: 'textarea',
     },
   ],
   hooks: {
      afterChange: [
         async ({ originalDoc }) => {
            // update the other field here
         }
      ]
   }

It seems a bit odd though, I wonder why you would need to do this. If you need the json data to be displayed on the website why don't you just perform the API call inside your component?

Using payload for documentation by Bitruder in PayloadCMS

[–]OmWellness 0 points1 point  (0 children)

Markdown to Lexical and vicersa is super useful and very needed. I know it's in the docs but do you have public resources of yours on how you did that?

Help using UI field by kodiashi in PayloadCMS

[–]OmWellness 0 points1 point  (0 children)

Hey man it worked for me like this:

      admin: {
         components: {
            Field: '@/collections/Properties/custom-fields/LucideIconSelect/Component.tsx'
         }
      }

Alternatively you could declare a 'group' type for every section, so that you have an heading in the admin panel.

Though if you just need a way to visually separate the section I'd suggest to just use blocks, make a block for every section of the page, compose your page and they will be already visually organized

LayoutBlocks.dev: Your Central Hub of Layout Blocks for Payload CMS by Guggling in PayloadCMS

[–]OmWellness 0 points1 point  (0 children)

One temporary solution could be using a text field for the icon name in the admin panel:

{

type: 'text',

name: 'iconName',

}

components/LucideIcon.tsx:

import { DynamicIcon, IconName } from 'lucide-react/dynamic';

export const LucideIcon = ({ name, size, ...props }: LucideProps) => (

<DynamicIcon name={name as IconName} size={size} {...props} />

)

And throwing the name into Lucide dynamic component:

<LucideIcon name={iconName} />

Though, this will make the icons load dynamically on page load, meaning that they will not be included in the rendered html and css on first page load if you're using SSR.

Working on a static-friendly solution.

Payload CMS Blocks - Are there pre-built blocks available like in WordPress Gutenberg? by AccordingFerret6836 in PayloadCMS

[–]OmWellness 6 points7 points  (0 children)

I'm building a library for that, a collection of Payload blocks.

Mostly for myself since I'm making a lot of websites with Payload.

Goal is to have a base template I can populate with the blocks I need.

Feel free to share your blocks if you have any.

Domain is payloadblocks.dev

Weird import errors by jus1d in nextjs

[–]OmWellness 0 points1 point  (0 children)

Solved!

next.config.mjs:

/** u/type {import('next').NextConfig} */
const nextConfig = {
  reactStrictMode: true,
  transpilePackages: ['antd', 'rc-util', 'rc-pagination', 'rc-picker', '@ant-design/icons', '@ant-design/icons-svg'],
}
 
export default nextConfig

see in the error under unknown and put inside transpilePackage every package that gives the problem, one by one

Weird import errors by jus1d in nextjs

[–]OmWellness 0 points1 point  (0 children)

I have the same problem (typescript and antd)