dbt-sessionization VS Hugo

RudderStack is an open-source customer data platform that empowers you to track your customer events from your web, mobile, and server-side sources in real-time. We have also open-sourced our primary repository - rudder-server - on GitHub. This article will walk you through the process of integrating your Hugo site with RudderStack using our JavaScript SDK. It will also help you track the real-time user events and send them to the destinations of your choice.

By using RudderStack to understand how users are finding and interacting with your site and then combining that with the data collected by your Marketo forms, you'll get deeper insights about your potential customers and provide higher quality leads to your sales team.

RudderStack lets you send the rich analysis from your warehouse to your entire customer data stack. Read more about how RudderStack's Warehouse Actions feature unlocks the data in your warehouse.

RudderStack is an open-source Customer Data Pipeline that enables you to track events from your web, mobile, and server-side sources and send them to your whole customer data stack in real-time. We have also open-sourced our primary GitHub repository - rudder-server.

We highly recommend checking out our Sessionization repository on GitHub to see how to use the sessions in a practical scenario.

I've been looking at replacing my project's website with Hugo (https://gohugo.io). Rather than generating a web page dynamically every time someone comes to your site, you generate the entire website statically whenever you change something. That means hosting can be entirely a "dumb" web server (or a "dumb" web server + apis which feed info to javascript, if you really need it). It also means:

* you can keep everything in version control to roll things back

* content can be fed to it programmatically

* project members can send pull request to post content, rather than requiring a special account

I've only gone through some examples from a book so far, but it looks pretty powerful, and is has good recommendations from others in the community.

I don't (yet) have a personal web presence, but if I do, it will definitely be something like Hugo.

And https://gohugo.io

Reading the commit message:

You already know Hugo. It’s one of the most popular static site generators in the world, because of its optimized build speeds, built-in templates for SEO, analytics, commenting (and more!), and its flexibility for developers. But while frontend developers will usually be the ones who build and set up new Hugo websites, they’re far from the only people who use Hugo on a day-to-day basis. In fact, most content and marketing teams will spend more time adding, removing, and tweaking website content than a site’s developer will. (This is another reason Hugo’s blistering fast build speeds are vitally important for production sites which see a lot of content changes.)

No, then you'd have to render HTML pages to files with a static site generator. Check out Hugo.

For developers who build sites with the Hugo static site generator (SSG), this particular aspect of commercial website development can be especially perplexing. You know how to give prospective clients the snazzy features that have caught their eyes elsewhere, but making it possible for them to make non-destructive changes later — e.g., editing a product description, contact information, or a call-to-action (CTA) banner — can get hairy in a hurry.