17
12 Comments

The perfect customer onboarding

Yesterday I invited Peter Suhm from Branch CI to the Sitesauce private beta.

He initially reached out to me asking if Sitesauce would work with their WordPress site, to which I responded with a link to a generated static site for their site. He was instantly sold, and I gave him access to the private beta to get their website to production. In less than five minutes, their static website was up-and-running on their main domain.

I've done other onboarding sessions before, but this was the first one where everything truly clicked from the start. He went from registration to production in around a minute with no roadblocks and no questions. I'm starting to feel like Sitesauce can really help people!

The Sitesauce public beta will be dropping soon, so make sure to leave your email on our landing if you're interested to get notified when that happens! (and if you can't wait, DM me on Twitter and we might be able to work out something ;)

, Founder of Icon for Sitesauce
Sitesauce
on January 30, 2020
  1. 1

    This is great -- well done here! Huge fan of static sites, but to others points about showing the value of a static site

    What if you show an example of a popular site using WP and then a static'd version of it to immediately show the value of what a static site can do for performance?

    Or better yet, allow folks to enter their site, run a job in the background and create this for them. Then ask for email of where to send the build to?

    Both could go a long way to showing the value, and building a list.

    1. 1

      Hey @jefff

      Per your advice I've started creating some demos. I have the WordPress blog and a few other CMS, but would love some recommendations as to which sites would be helpful to have.

  2. 1

    Congrats on the beta!

    Looking at the "What do I get?" section, I'm not quite sure how this is different from putting your site behind a CDN. And based on the other comments here, I think this might be a common confusion and worth pointing out on the landing page.

    1. 1

      Do you have any suggestions on how to improve this without using a giant wall of text right in the middle of the landing? How would you change the "What do I get?" section after reading the comments and hopefully understanding a bit better what Sitesauce does?

      As you probably know, it's really hard to explain these things when you're really familiar with them, so if you could answer the above questions (especially the second one), that'd help a lot 😊

  3. 1

    congrats on that onboarding. seems like a good niche to be in.

    i'll second what @ycm8 asked, and would add, how is this any different than say running wp-rocket for wordpress? i understand there may be different use cases than wordpress, but then maybe not use wordpress as an example?

    1. 1

      First of all, I tend to use WordPress in the examples because it's by far the most known CMS out there, but as I mentioned in the last paragraph of my response to @ycm8, it works for any CMS.

      As for the difference with WP Rocket, Rocket just does some caching work while Sitesauce builds a truly static site and uploads it to a different static site host, like Netlify or Zeit.

      1. 1

        Got it, thanks. So how do you deal with SEO, more precisely Redirects (301 and 302), GET-parameters, that may be used to pass different information from different landingpages and altering the pages? As well as First or Last Cookie Wins strategies?

        example.com/pricing?coupon=indiehackers would look the same as example.com/pricing

        Mind-boggling tech, really curious how this magic works. Would love to give it a testrun... Didn't find a demo/test plan on your site? Any chance, we the IndieHackers community, could get a 2-3 day demo?

        1. 1

          Redirects can be configured from the Sitesauce dashboard, and you can keep page configuration via GET query parameters if you do it in JavaScript.

          Sitesauce provides a 7-day trial, which isn't listed yet on the website because we're currently on private beta (as mentioned in the post above). If you leave your email on the landing, you'll get notified when the gates open!

  4. 1

    what does it mean to convert a dynamic site to a static one? I read the benefits section, but does it mean there are two versions of the same website? how do they coexist?

    1. 2

      Imagine you have your WordPress site hosted at wp.yourdomain.com. With Sitesauce, you can serve a static version of your site at yourdomain.com. This allows your team to keep accessing your WordPress dashboard to manage content while you continue to serve an always-updated static version from your main domain.

      If you don't need your WordPress dashboard publicly available, you can also use our CLI tool to deploy your static site from a locally-hosted website, that is, a WordPress instance running on your computer that doesn't need to always be on.

      Of course, Sitesauce does not only work with WordPress but with any backend-powered site, like Ghost, Statamic, CraftCMS, Laravel or Joomla.

      1. 1

        Few q's:
        If the users visit static site, how does the interactions with the backend work? for example, how does sending a form works on the static version?

        Also didn't quite understand the example - the wp.yourdomain.com is the wp admin panel for the yourdomain.com?

        1. 1

          I'm still working on perfecting interactions with the backend. For now, you can keep using your backend forms by proxying the form endpoints directly to your backend, but I'd recommend to fully embrace the JAMstack and switch to something like @derrickreimer's StaticKit for forms.

          And yeah, in the example wp.yourdomain.com would host a regular WordPress installation, while yourdomain.comwould host the static version of that same site.

  5. 2

    This comment was deleted 4 years ago.

    1. 2

      This comment was deleted 4 years ago.