4 ms·

I worked at Stripe for over five years. It’s a monorepo with multiple services. The marketing site, docs site, and API are separate services.

hoofhearted 3y ago
Nice! Thank you for you the insight! It's clear that it's a monorepo that they are packaging up at build time to create a seamless website. Any ideas on what they are using to accomplish this? Regarding the original topic of this post, I'm 99% confident that Stripe is not using WordPress to write their docs and content either way. P.S. On another note, I've been leaning on BDC to provide me with insight and feedback on my current project. I really doubled down on this modern content system idea after I interviewed with Increase for a senior frontend role under Ben. They asked me to critique the frontend and tell them what I would improve. The only improvements I could find was the lack of user docs and marketing content to promote all their development efforts. It's @bdc of course, how am I going to improve his work when he is setting the bar? Increase lacked content at the time because they hadn't yet found a seamless method of content management with their existing Vue.js codebase. My current project solves all of this with a simple Next.js app that comes baked with everything a startup could need for content.
- clintonb 3y ago
  You can learn more about the current system at https://stripe.com/blog/markdoc https://stripe.com/blog/markdoc. It was never WordPress. You may be over-indexing on “packaging”. It’s been a while since I’ve worked on docs, but much of what you’re calling “packaging” is simply routing to another app.
hoofhearted 3y ago
P.S. Yes! Developers want to package up their blog content, user docs, API docs, and app code into seperate repositories, but pack them up together into a single website during build time. Coming soon to Elegant: Split your docs, React code, and blog content into seperate repos, and pack them back up into one app during build time : ) Can WordPress or Ghost do that?

hoofhearted 3y ago

Nice! Thank you for you the insight! It's clear that it's a monorepo that they are packaging up at build time to create a seamless website. Any ideas on what they are using to accomplish this? Regarding the original topic of this post, I'm 99% confident that Stripe is not using WordPress to write their docs and content either way. P.S. On another note, I've been leaning on BDC to provide me with insight and feedback on my current project. I really doubled down on this modern content system idea after I interviewed with Increase for a senior frontend role under Ben. They asked me to critique the frontend and tell them what I would improve. The only improvements I could find was the lack of user docs and marketing content to promote all their development efforts. It's @bdc of course, how am I going to improve his work when he is setting the bar? Increase lacked content at the time because they hadn't yet found a seamless method of content management with their existing Vue.js codebase. My current project solves all of this with a simple Next.js app that comes baked with everything a startup could need for content.

clintonb 3y ago
You can learn more about the current system at https://stripe.com/blog/markdoc https://stripe.com/blog/markdoc. It was never WordPress. You may be over-indexing on “packaging”. It’s been a while since I’ve worked on docs, but much of what you’re calling “packaging” is simply routing to another app.

hoofhearted 3y ago

P.S. Yes! Developers want to package up their blog content, user docs, API docs, and app code into seperate repositories, but pack them up together into a single website during build time. Coming soon to Elegant: Split your docs, React code, and blog content into seperate repos, and pack them back up into one app during build time : ) Can WordPress or Ghost do that?