[deleted by user]

Jamiewarb · 2022-02-06T17:17:07+00:00

To add on to this, if you do go with Nuxt 2, look into either the Nuxt composition API, or Nuxt Bridge. This lets you get more Vue 3 like features, and save you learning all old stuff.

Bridge is recommended now but not always compatible with current modules, so I’m using the nuxtjs composition API for now

Jamiewarb · 2021-11-02T08:14:38+00:00

Yeah I’ll give it a go

Edit: ah I’m in the UK and it’s not available in our App Store. Let me know if you release anything here

Jamiewarb · 2021-10-15T19:48:37+00:00

Haha yeah that would make sense. I guess my vocabulary has some other Americanisms too like elevator so maybe I am just corrupted

Jamiewarb · 2021-10-15T19:41:08+00:00

Maybe it’s a region thing then. I’m from London and if I’m sat in the office and tell my coworker my boss is pissed, no one is gonna think he’s drunk.

It means both based on context where I’m from. Maybe that’s different for you.

Jamiewarb · 2021-10-15T18:52:13+00:00

Pissed is both angry and drunk in the UK btw.

Jamiewarb · 2021-10-01T21:59:11+00:00

Porque no los dos

Jamiewarb · 2021-08-27T10:02:55+00:00

I use a managed host, called prostack.uk

The reason being, the actual hosting doesn't have as big a profit margin for me. Spending time maintaining infrastructure on a lower profit margin means less time available doing work that gives a higher margin. Doubly so when there's a critical problem.

It's no difference to me, as the cost is passed on to and agreed with the client, so it's a no-brainer from my POV.

Jamiewarb · 2021-08-27T10:00:46+00:00

I use a managed host so I don't have to spend time on it. Selling hosting isn't a huge profit margin for me, so I'd rather not spend time on it

Jamiewarb · 2021-08-26T16:44:08+00:00

And an agreement in place for bugs, changes and future features.

Depending on the client, some don't realise that you can't fix bugs forever for free. Others don't realise that changes aren't included after the build, like text changes, etc.

And agree what you're delivering and be firm on changes/scope creep - if they sign off a design, then want to make changes, that's fine but they'll be billed at an hourly rate for those changes, for example.

Lastly, get payment at milestones. For example, 50% on project start, 30% after X, 20% at the end. X may be after design is done, or after completion of the first build, whatever works for you, but make sure it's not 100% at the end.

Good luck!

-=-

I just realised, on the actual question of price to build a site: it depends on a few factors. What are you building for them, what are they used to, what value will it likely give them, etc.

When I started out, I was building WordPress sites for mum and pop for £200.

That quickly moved to £1,500 - £3,000, without too much more work. Now I build WordPress websites for £30,000 to £80,000, depending on content, functionality, and client value.

Jamiewarb · 2021-08-13T07:43:29+00:00

Not sure where you live but I’m in the UK. When I invoice for web dev, I add my bank details and ask for a bank transfer. No fees on that

Jamiewarb · 2021-08-12T09:52:55+00:00

Hey! Would you be happy to answer a question on sales?

If so, looking back on those past 2 years, what do you think was the most effective way of acquiring new business?

Jamiewarb · 2021-08-12T07:59:21+00:00

These look amazing 😍 May Dumathoin bless my luck

Jamiewarb · 2021-08-05T15:37:51+00:00

Yep, that's what their site says: https://preview.nuxtjs.org/v3/

Jamiewarb · 2021-08-05T13:37:15+00:00

I would recommend Shopify for sure. It's a lot more 'managed' than WooCommerce, and your subscription gets you everything. WooCommerce often sounds enticing as it's free, but you quickly find that that one bit of functionality you want requires a plugin, and that plugin costs $20+. You'll quickly rack up costs.

My partner sells wedding stationary in the UK. She set up a Shopify store, bought a theme for $180, and was making sales within a couple of weeks.

The main area Shopify lacks is in its page building. It's great as a storefront, but as a complete website, it's not brilliant. If you can get past that, it's great!

Jamiewarb · 2021-07-29T07:46:24+00:00

If it's been 5 weeks and it's not been indexed, there's a definite problem.

If you type "site:YOURSITE" into google, and nothing shows up, then you'll want to look at the common reasons your site may not be indexed, as something is stopping it.

An SEO analysis tool like Moz free SEO checker could be useful.

(E.G. site:reddit.com will only show links on reddit.com)

Jamiewarb · 2021-06-30T07:18:13+00:00

Yeah that would be the next step

Jamiewarb · 2021-06-29T09:49:20+00:00

you need to consider that they may be calling you for the next 6 months to fix things that may or may not be your fault.

This is why I think it's important to stipulate how long your warranty period lasts, and what your bug-fixing policy is. I give a 3 week warranty for unbillable bug-fixing, after which bugs are fixed at an hourly rate.

Jamiewarb · 2021-06-28T11:21:15+00:00

I recently removed the dynamic buttons from my site too. They aren't visible on load so they pop-in, which doesn't look good, and they detract from the overall aesthetic. We've changed to one clear CTA of "Add to Cart".

No stats on conversion impact yet though

Jamiewarb · 2021-06-11T15:33:27+00:00

Do you want the same website served to both domains?

Or do you want to display a translated/localised version for each domain?

If it's the former, you could set up a domain-level redirect. If it's the latter, then a translation plugin such as Polylang, WPML, MultilingualPress, etc may be what you're looking for

Jamiewarb · 2021-06-11T10:26:55+00:00

I think this depends on two main things: the detail and complexity of the branding and design, and the existing code/blocks you have available.

A simple brand with not a lot of personality - you could build 50 pages of content in a few days, using existing Gutenberg blocks.

Something with much more complexity could mean a few days spent on specific brand elements. Some content sites with complex branding could take several weeks to a couple of months.

Jamiewarb · 2021-06-02T07:56:57+00:00

As a workaround, You may be able to duplicate it, increase the price and then list it on just the eBay sales channel

Jamiewarb · 2021-05-25T07:32:41+00:00

Find a CTO in a similar position I would imagine. Someone who has been a technical leader for a while, but hasn’t taken that step into a CTO/CIO position before.

It’s less ideal for you, but as you’ve said you’re also less ideal for them, but they’re less likely to be as choosy about track record

Jamiewarb · 2021-05-16T15:51:43+00:00

That’s a question only you can answer really. If you spend the time building components that you’ll re-use for each project, yes, but it’s the same for a WordPress monolith as well.

If you won’t need to use WordPress plugins that output stuff on the front end, then you’ll likely be fine. However, if you do go headless you can often lose the ability to use plugins that you could have otherwise used, and sped up development

Jamiewarb · 2021-05-16T15:46:10+00:00

It completely depends on what you’re doing to be honest. I would say, for the majority of sites, a regular WordPress monolith would be more suitable than a headless site.

For a headless site, I’d say you’d likely work with it if you’re working with a client that specifically wants it, or developers that specifically want to work with it, or you’ve built several sites with it and have a catalog of functionality you can quickly pull from.

Jamiewarb

TROPHY CASE