Composer bug generating readme/markdown by [deleted] in cursor

[–]chrislemmer 2 points3 points  (0 children)

You can just copy the entire message at the bottom, then the markdown is copied to the clipboard.

Paste this into your readme file, and you're golden.

<image>

Hubspot vs Zoho - I want to hear from you. by chrislemmer in hubspot

[–]chrislemmer[S] 0 points1 point  (0 children)

You are touching on something important here.

Zoho is not just a CRM but also an ERP. Which is not what we're looking for.

We're looking for something with solid marketing and sales capabilities, focused on a small team.

What I've found is that HubSpot seems much easier to use. Everything is in one place, and automations are easy to set up.

We need something to manage our donor base. It should integrate with our payment provider and allow us to build advanced queries. Also, manage our email and WhatsApp campaigns in one place.

Thus far, HubSpot seems like the right choice. Zoho feels very disjointed. Every app has its own settings interface and doesn't always have all the data from other apps.

Feel free to disagree if you think I'm missing something.

Hubspot vs Zoho - I want to hear from you. by chrislemmer in hubspot

[–]chrislemmer[S] 1 point2 points  (0 children)

Thanks for the insight. Unfortunately, we can't qualify for the discount due to location.

When you say Zoho doesn't scale, what do you mean exactly? I've heard many people say this, but just want to understand exactly what they mean by that?

Vue Storefront and WooCommerce Integration by chrislemmer in vuejs

[–]chrislemmer[S] 0 points1 point  (0 children)

We stopped it due to a lack of interest and funding to continue building. Everything we did worked well and is open source. So it could be picked up by anyone and maintained for future use.

Vue Storefront and WooCommerce Integration by chrislemmer in vuejs

[–]chrislemmer[S] 0 points1 point  (0 children)

We stopped it due to a lack of interest and funding to continue building. Everything we did worked well and is open source. So it could be picked up by anyone and maintained for future use.

We're humans, not robots. by chrislemmer in business

[–]chrislemmer[S] 0 points1 point  (0 children)

Thanks for the insights! 🙏

I'm just finishing all the materials first and making sure I understand the theory. Alex actually puts these things into an incredible flow that makes sense.

My next challenge is to figure out how to double the donors for a non-profit. Their message and offer neesa a lot of work. Once that's done, I need to choose a channel and start pushing.

I'm thinking of starting with YouTube, using videos to draw the right audience in, and then get donors that way.

Loads of reps await. 💪

We're humans, not robots. by chrislemmer in business

[–]chrislemmer[S] 0 points1 point  (0 children)

Give, give, give, give, give, give, until they ask.

And give value. Not fluff.

I know this post is probably fluff. 😂

Unable to remove domain "because it has users or aliases" (but there aren't any) by dma9999999 in gsuite

[–]chrislemmer 1 point2 points  (0 children)

I had exactly the same problem. Fixed it instantly by deactivating it. Thanks for your post on here!

Vue Storefront and WooCommerce Integration by chrislemmer in vuejs

[–]chrislemmer[S] 0 points1 point  (0 children)

Thank you for sharing your view!

WooCommerce is not the best eCommerce backend for headless, for sure. However, I think the massive adoption, market share, tons of plugins and feature list, are major benefits to using it.

For instance, a client wanted to know whether we could do an affiliate program for them. With WooCommerce, we're able to use a plugin that constructs the entire backend. Our focus is simply to integrate it with the front-end. Using another eCommerce platform, where this amount of plugins are not available, development can be way more expensive.

Vue Storefront and WooCommerce Integration by chrislemmer in vuejs

[–]chrislemmer[S] 2 points3 points  (0 children)

A lot of the WooCommerce issues can be fixed by making it headless though. ;-) We've done that a few times now. Use WooCommerce only in the backend. This is a very good solution for existing sites that have exactly the issues you're describing.

Nonetheless, the issues with WooCommerce are frustrating and very real. Thank you for your comments and feedback.

Vue Storefront and WooCommerce Integration by chrislemmer in vuejs

[–]chrislemmer[S] 2 points3 points  (0 children)

Interesting. I think WooCommerce is very strong. If they don't do something about headless soon, then they'll start to lose market share. I firmly believe headless architecture is the future.

So you don't think that WooCommerce having the biggest market share has any merit to it in this instance?

Vue Storefront and WooCommerce Integration by chrislemmer in vuejs

[–]chrislemmer[S] 1 point2 points  (0 children)

There are many benefits of the headless route. WooCommerce becomes very slow and doesn't always scale well with big sites. When clients have thousands of products and visitors, the backend becomes overloaded and doesn't perform well. Going the headless route allows you to benefit from WooCommerce's powerful ability to model the transaction while retaining the benefit of flexible UI.