Is it necessary to have a website with a package name as domain or not?
Does that prevent user to trust the developer?
Is it ok to have it in the developer website.
ā¹ļø I know there are successful packages like Translation Manager
& uSync but here is my question in case there is something to share before launch.
Yeh all my packages just point to the GitHub repo if its open source, but if I was going closed source/commercial then I would go for a custom site/domain IMO to help build trust and to read learn more about the package etc a place to contact support enquiries etc
But for open source projects a GitHub repo with issues is great for this IMO
t
Tarik
07/17/2024, 8:16 PM
> but if I was going closed source/commercial then I would go for a custom site/domain IMO to help build trust and to read learn more about the package etc a place to contact support enquiries etc
Yes, it is closed source but I plan to use Github to manage issues and discussions but your opinion is important Warren.
Thank you all.
s
Sebastiaan
07/18/2024, 10:24 AM
No worries! If you're developing a commercial package, let me just warn you that it's difficult to get people to pay for a package š
I would recommend you listen to the Package Manifest podcast which has a lot of information about making commercial packages for Umbraco in it. There's some great tips on what works and what doesn't: https://open.spotify.com/show/7BQFm8NKL0RboHGLDx2OmX
Sebastiaan
07/18/2024, 10:25 AM
Listen to all 13 episodes, not just the last one š
t
Tarik
07/18/2024, 11:23 AM
Thank you @Sebastiaan, I hope the package simplify the Umbracians and clients daily job on the backoffice.
The plan is to offer free features and premium.