posthog.com VS docx

It's because we wanted our team to be aware that we'd have this intention so we don't miss out! If someone leaves PostHog voluntarily to start a new company (i) that's sad for us but is a pretty cool reason to leave and (ii) if we were willing to employ them, we'd be willing to invest in them more.

There are some pieces of missing context I guess. Primarily that we're small still (30 people) so we tend to hire a lot of ex founder / generalist type people (and most are technical) who'd be quite well suited as founders.

One thing I will do is add a more detailed handbook entry to create more clarity around this benefit. Issue made (https://github.com/PostHog/posthog.com/issues/4013)!

OP's calculator is just using open source data from Gitlab. In it's data, New Jersey:

Since I don't have much knowledge of web development, the application has a very basic structure: html + css + javascript. To generate the document, I use a library called docx.js (https://docx.js.org). When the user clicks to submit the form, the request is passed to a function in the main file (app.js), which , through conditional logic, assembles the document using docx.js.

Looks like this library wasn't meant to open existing files: https://github.com/dolanmiu/docx/issues/1513

Had such requirement in the past, this worked well https://docx.js.org/

Honestly with this brief I'd avoid Ruby/Python and go straight with JavaScript. UIs with javascript are pretty easy, and there are great libraries out there like https://github.com/dolanmiu/docx which make it relatively easy to edit word documents.

For Excel it's much easier to convert your raw data to CSV than to put it into an HTML document and then extract it back out again. Similarly for .docx format, you're probably better off using a package like docx and building the document in a way more suited to the file format than trying to smush HTML into a new format.