@barefootstache Hi, hired to work on which professional site?

How did you win over to work using #Hugo over #Wordpress?

(i.e. was it specifically some points of convincing them or more their ability / skill more neutrally to not need be swayed from typical "Wordpress" standard as a site?)

@freeschool still in development:

https://munich-rucking-crew.codeberg.page/

Main points were: ownership of content, speed, green development, accessibility, independence

Downside for me is that I will have more overhead in the long run.

@barefootstache Ah great, rucking-related stuff, just what you're into also. Glad to hear!

How does one even price this kind of work, if you don't mind me asking? There like an X factor perhaps of hours and the degree of difficulty involved... where Wordpress perhaps designates that to owner and it's main users with GUI interface (IF I'm right there?)

@freeschool it all depends on what kind of pricing model one prefers.

I prefer the project plus optional service model.

Things to consider:

1. Who and how will it be hosted? Prefer with codeberg using two repos, one for development, and one for publishing.
2. How will it be themed: predefined or custom? Prefer predefined, since it is less work for me and customer can see results quite quickly. Some customers like predefined with customizations like different styling colors. For custom, a designer will need to be hired separately.
3. How many additional components will need to be made? Do all the components aka partials from the theme suffice, or do new components have to be integrated. This is the most work, since one will need to abstract component just enough so that the customer can add the different values for the variables without needing to deal with the underlying code.

Optional service: maintenance

The concept of git is just too much for the basic individual, thus one will have to maintain this step.

Next the abstraction of markdown is too difficult for many to understand, thus one will have to pattern match between documents and markdown.

Next the meta data of each markdown file might be too much on top of the abstraction of markdown to understand which patterns are acceptable and which ones are not, so more maintenance here.

In the end, unless the customer is willing to learn the services and technology, they will purchase the whole package.

Project: one time cost
Services: either monthly subscription or per entry

@freeschool

The question that each individual should ask themselves before taking upon any task is why are they doing it?

Is it because they want to or is it because they have to.

As long as one finds individuals that want to do a specific job, then an exchange of services could work.

And this is the core concept behind open source projects or non-profits.

Individuals who have to do task are more prone to lose motivation and thereby might delay or in the worst case cancel the whole gig altogether. Thus a formal contract should still exist to catch such cases where states something in the lines of:

> If one does not provide the service as advertised, then this price is due.

Further one should put also a clause that manages the expectations. This in the long run won't discourage the employer to quit potential further gigs.

The only benefit I see behind wish lists is that it could be an option to circumvent income tax.