It completely depends on nature of your site or business you intend to manifest virtually. So I would keep it generic and to the point that is required for most of business models.
General Checklist: Terms of use Contact page About page Transactional emails setup SMTP setup Google analytics setup Strong passwords on server, backend, etc Google webmaster setup Server monitoring setup Server backups setup Server security Minify JavaScript, css, html, svg, etc SSL setup Setup conversion goal tracking in google analytics for sign up, buy, etc Change nameservers Add sitelinks search box schema to Homepage Cross browser tested Create social network accounts Logging Security (you may have different layers like, django security, Web server security for Apache, Nginx or whatever you choose to work with) SEO related CheckList: Sitemap Robot.txt Meta title tags Meta description tags Image alt tags Image title tags H1 tag SEO friendly URLs No follow tags Google pagespeed insights Category names Duplicate pages Canonical tags Redirect www to non-www Redirect http to https For high level deployment checklist related to Django please see: https://docs.djangoproject.com/en/1.9/howto/deployment/checklist/ You can add more depending on nature of your site but again that depends what you are doing. Regards, Mudassar On Tue, Aug 9, 2016 at 4:13 AM, Andreas Kuhne <andreas.ku...@suitopia.com> wrote: > Hi, > > I don't know what level you are interested in, but I think this course > will be interesting: > https://www.kickstarter.com/projects/mikeckennedy/python- > for-entrepreneurs-video-course > > It'll probably contain some of the items you are requesting. > > Regards, > > Andréas > > 2016-08-09 12:59 GMT+02:00 <david.va...@gmail.com>: > >> Hi Serge, >> >> Thanks for the reply. >> >> I agree it is a mix of different tasks, but they are all needed when >> starting a new business/product/service website. As it happens it is >> something I had to do on quite a few occasions lately for some of my >> customers. >> >> I'm trying to find out if there is a better way to do this (as it feels >> that it always the same process) and see if it is a problem that other >> people are facing (and how they are solving it if they are). This is mostly >> when launching the site to the public. I can and have done all the steps >> multiple times. However, it feels like there should be quicker way to do >> it. It can easily take up to a full day when adding all of them. >> >> Thanks >> >> Arnaud >> >> On Monday, August 8, 2016 at 7:02:08 PM UTC+1, Sergiy Khohlov wrote: >>> >>> Hello David, >>> You have mixed different tasks. I have a question for you. >>> What kind of goal do you have? >>> Are you planing to have mail server, web server, dev box etc? >>> How much money are you going to spend? >>> Do you have sysadmin ? >>> Of course first question has high priority. >>> >>> Thanks., >>> Serge >>> >>> 8 серп. 2016 18:20 <david...@gmail.com> пише: >>> >>>> Hi, >>>> >>>> This is slightly off topic, but I can imagine some of you might have >>>> faced this situation. I've been launching quite a few websites lately. It >>>> usually involves at least the following for me: >>>> - Domain registration and DNS setup >>>> - Server/Host configuration: Heroku setup (registration, environment >>>> variables for some of the steps above) or Docker setup >>>> - Deployment >>>> - Security aspects: TLS certificates, HTTPS setup, HTTP security >>>> headers, etc >>>> - Legal aspects: cookie policy, T&Cs, privacy, etc (implications from >>>> other steps) >>>> - Email: basic setup, SPF/DKIM for the spam, create RFC email >>>> addresses, etc >>>> - Mailing list setup (MailChimp or others) >>>> - Social media: signup to a few social networks, add "social sharing" >>>> buttons >>>> - Analytics/instrumentation/monitoring (Google Analytics, New Relic, >>>> etc) >>>> - Search engine registration/indexation (Google, Bing) >>>> - etc >>>> >>>> Some of these steps are interlinked and that's only for fairly "basic >>>> website" without any payment, A/B testing, user feedback or advertising >>>> requirements. >>>> >>>> None of it is particularly complex, although it does require some >>>> knowledge/experience, but it takes quite a lot of time and feels >>>> repetitive. >>>> >>>> There are lots of great products/services for the individual steps >>>> involved, but I can't find anything to streamline the whole (or at least >>>> part of the) process. >>>> >>>> Does anyone know any good tool, product, checklist or website for this? >>>> Do you have the same problem? How do you handle this yourself? >>>> >>>> Thanks for your help. >>>> >>>> David >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Django users" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to django-users...@googlegroups.com. >>>> To post to this group, send email to django...@googlegroups.com. >>>> Visit this group at https://groups.google.com/group/django-users. >>>> To view this discussion on the web visit https://groups.google.com/d/ms >>>> gid/django-users/5de3b67d-5b14-4e98-a1ae-0638addbce1b%40goog >>>> legroups.com >>>> <https://groups.google.com/d/msgid/django-users/5de3b67d-5b14-4e98-a1ae-0638addbce1b%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "Django users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-users+unsubscr...@googlegroups.com. >> To post to this group, send email to django-users@googlegroups.com. >> Visit this group at https://groups.google.com/group/django-users. >> To view this discussion on the web visit https://groups.google.com/d/ms >> gid/django-users/1198c456-b840-4401-828d-29012ddc7889%40googlegroups.com >> <https://groups.google.com/d/msgid/django-users/1198c456-b840-4401-828d-29012ddc7889%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-users+unsubscr...@googlegroups.com. > To post to this group, send email to django-users@googlegroups.com. > Visit this group at https://groups.google.com/group/django-users. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/django-users/CALXYUbkYWbAOn%3D1eKQhfD16r2kiTCduVPPjmB8bMqF > G7PvRkDw%40mail.gmail.com > <https://groups.google.com/d/msgid/django-users/CALXYUbkYWbAOn%3D1eKQhfD16r2kiTCduVPPjmB8bMqFG7PvRkDw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CANoUts5w_xw-fZf8i2xD4zNoLfha%3DSbhDNvKfPjhVaREr_Mk5w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
