#DailyBloggingChallenge (322/365)
The nice thing about #hugo is how quickly one can get a site up and running.
The tricky part of it is understanding its directory architecture. This can become more difficult if using a user predefined theme, especially if one wants to one's custom spin on nonexistent parameters.
#DailyBloggingChallenge (323/365)
One will learn that one will need to copy (usually) the whole file from the themes directory and mirror its directory structure onto the root level.
This can be quite a nuisance if one wants to change just one #CSS value.
#DailyBloggingChallenge (324/365)
Learning about the directory architecture opened the gates of writing custom partials.
I previous knew of their existence depending on the specific theme and usually could avoid them by injecting custom #HTML.
Now that I have been hired to work on a professional site, especially after propagating why to use #hugo over #Wordpress, I shall use the framework to its standards and fullest capabilities.
@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
Working together, Matching Wants / Wishlists, Payments and 'occasioal' Exchanges...
@barefootstache Great read actually and clarity... worthy preparation for the client - they should pay you in explaining it all! :)
What about payment options or ever done an exchange of services or material? (chances are low but if happen to find someone, say me to do some audio editing / podcast work in exchange for a site - I'm not asking btw)...
I know moolah 🏦 is #1 but both paying and also getting charged for it is a bit like hmm,...
And chances are low like every 100 Fediverse person you meet can do something if even chances are still super-low but well what do you think - do you have wishlist of project you could hand off a bit to someone else to start / continue / finish?.
yeah ACTUALLY matching wants would be cool - what do you think... actually like a website with #wishlist ?
Would by-pass somewhat the dirty rotten middle-men and at the same time encouraging those who have skills on #Fediverse! 🤔 
🤔 ?
Working together, Matching Wants / Wishlists, Payments and 'occasioal' Exchanges...
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.
Working together, Matching Wants / Wishlists, Payments and 'occasioal' Exchanges...
@barefootstache Sure from their view, and from another view those that are more intentional perhaps "For the Fediverse" (in very short) and other reasons (not the only one, we still genuinely give and take what we can and exchange meanwhile in other ways too). But practising / experimenting / a bit of self-development could go a long way else not losing much... We have a good wishlist to show each other at the end and perhaps pin it to our profile :)
Something else also is there for me like the "Doing if for ourselves" | DIY ways |"For the love it" | "On the Fediverse, For the Fediverse" means many reasons can be included as people prefer things here (interface, social, anti-cap) and I guess these are what might curve or re-direct people's existing wants and why... to make it the reason also! (it's not exclusive)
Even if it's a basic list to start off with just for me and only those that actually want to chat will write it, I think it's still very interesting :) even in the lowest responses... say just you and one by one for now... (do you mind a quick wish or project list? thanks!)
But to include Fediverse also is "in order to populate / propagate work here instead of 'there'..." and that could be a sort of principle written up for this idea so that it's as a 'Manifesto' or alignment of all our efforts or even something fun.
Much like a new way or new path or new software, it might serve people almost the same in the end while providing another eco-system here all the while... (a bit of ping pong and interest will soon prove itself and well there is actually time to let it simmer or slow-cook / seed etc)
If a few people get what they want done (even without caring much) they might use things as they are already here (like #hashtags for @freemo ALL the jobs he needed 11+ maybe but I remember it was just hashtags that did it!!) What a win for #Fedihire and #Job hashtag and I helped to overload hashtags to get that (he didn't have #Fedihire which is more respected now maybe for high quality jobs)
So just to stick a wish list on their pinned list for their practise and test to see what happens... might not be too bad!
Doesn't seem to cost much and even I could throw some money to it to help incentivise or get idea clear somewhere even on another external page (lol) but somewhere clean and clear and then back to here... maybe just images of the steps I'll work on as as wishlist icon and pinned post...
Summary... (that for reading and considering problems or what sounds best to you)
A kind of "doing it for ourselves" is really what's needed so this is part of that without trying to break ourselves over it or break the bridges of reality without something too new - just us more conscious or testing perhaps...
Even Gartner-effect it while being totally honest it's just starting or if I pay the way for people's wishes to be done in order to start things off and then "pay it forward"... then so be it, I'm seriously happy to throw money at Fediverse now and also before my own educational test and attempts here are complete...
https://en.wikipedia.org/wiki/Gartner_hype_cycle#Hype_in_new_media
#Wishlist #GiveTake #Opportunities #Jobs #FediHire #Activities #WantedAds #LocalAds #etc
Working together, Matching Wants / Wishlists, Payments and 'occasioal' Exchanges...
@freeschool
Like you state one would have to test it to get the most accurate response of how any group of individuals would react.
Pinning the wish list is a good ad hoc solution and having it on a secondary site as a backup or primary is also not bad.
The main place where I have seen wishlists is among streamers, thus there might be much lead way until the first items are brought into existence. Unless one already has a big fan community.
One could start doing an analytical evaluation of seeing how many reactions one gets onto one's own content.
It will definitely be much work to see any valuable results under our small (combined) followers.
From personal experience participating in many ideas, one will need a leader who is 110% behind the idea and constantly motivate the other members to continue progress towards the incentive.
There are two main downfalls: 1. taking too long to start creating the product, and 2. wasting too much energy building something the customer doesn't want.
Although such downfalls exist, an okay result would to create new friendships that break the confines of the project or realm.