Setting up a service for weavers: WordPress/Dokan research, ongoing costs and integrating open-source alternatives.
There were real choices in the Kindred Hands software journey. I looked at the initial WordPress and Dokan route, the continuing costs changed the direction, and I brought a couple of open-source alternatives together with guidance. The wider project also included research, evaluation and integ
The reason for comparing costs came from the purpose of Kindred Hands. I wanted a direct route to customers without our taking commission, and the initiative was intended as not-for-profit. Continuing costs around the first software route led me to explore alternatives. The purpose and the comm
The change of software route was part of the work I took responsibility for in Kindred Hands. After looking at WordPress and Dokan, the continuing costs led me towards a couple of open-source alternatives. I brought those components together with guidance. I was building with existing software,
My work on Kindred Hands included the e-commerce platform and multi-vendor functionality. The wider project also involved research and integration of virtual try-on. Those are different kinds of work, and I find them more useful to explain separately than to collect under the word advanced. Int
Running costs were one of the reasons I changed the first route considered for Kindred Hands. That made the question of what continues later much more practical. A service might be easy to choose at the beginning, while the reason for that choice becomes harder to explain once other work takes
The continuing costs around the first route changed the direction of my Kindred Hands setup. I had looked at WordPress and Dokan, then explored open-source alternatives and linked the chosen pieces with support. The cost question did more than send me looking for a lower price. It changed what
WordPress and Dokan were part of the initial route I looked at for the multi-vendor side of Kindred Hands. They gave me something concrete to investigate. Instead of imagining one website that somehow handled everything, I could begin asking which part managed content, which part handled vendor
Kindred Hands was intended to help weavers sell more directly to customers without our taking commission. My technical responsibilities included the e-commerce and multi-vendor side of the initiative, with support. That made the route after a product page part of my responsibility too. A photog
I offered to upload the products myself. That was a practical part of Kindred Hands, not just a feature on a website. In Pochampally, the first conversations did not turn into participation as quickly as I expected. After about a week, only one initial contact had sent photographs and descripti
