What was the pain points of getting your website up and running?
If your business has a website to present itself (a few pages and maybe a blog) what was the problems or pain to get it ready and live? What would be a better workflow? What is the 1 thing that should definitely be easier in the process?
Trending on Indie Hackers
Legal stuff aka. Terms of Service, Privacy Policy and GDPR. Also, setting up an automatic email system that doesn't crash and delivers emails reliably, meaning they don't end up in spam folders.
So I guess you build the website yourself and did not contract an agency right? Did you look for legal stuff generator online or copy them from other reputable website?
Yes. I used a generator to create a 'draft', but I guess you always need to adapt it to your product if you display 3rd party media, upload files, etc.
Ok is the theme or design really important? Or getting everything ready with little configuration and a way to write you content and add media is good enough?
Like all ready out of the box and you only need to write the copy, company info and changes the pictures, meaning only a few hours of work.
No no, the design is not important at all, I'm only talking about legal text that covers what you are doing, how you handle and store user data, etc. so that you do not get in legal trouble. Especially with all the scandals these days - Facebook aso. - people get more aware about this stuff and regulations become tougher.
Ok thank you, I think like you
Getting email to work is a beast.
last 5% takes a lot longer than it would seem. clearing last points from the checklist - legal, hookup and configuration of external services (stats, etc.), getting the kinks out of css, brushing up on UX, tweaks to copy.
So you would be happy to provide the minimum info (company info, API key for external services...) and get all that generated or deployed for you? Tweak the copy is a constant improvement I guess...
the issue is this is not that it's hard. it's tedious. people pay for hard and hire (in-house) for tedious ;) if you part ways with the details for your facebook stuff there is a chance its going to get used not 100% to your liking (cambridge analitica and such...), if you outsource data gathering like stats on views and clickthroughs you won't own that data 100%.
If you want to build a service like this I would rather pay for something I can deploy on my server, have it contained in my environment and tech stack, log in for time to time and configure basics so every other mundane tasks get done automagically.
Usually this sort of a thing gets written in-house. Right after all important stuff is done*.
*it's almost never done ;)