Ideal way to handle pseudo-dynamic content (pre-1.0.0)

[noelforte]

I'm aware that Serverless bundles and programmatic triggers will ship in v1.0.0 but I wanted to get some opinions on how to handle the following setup before 1.0.0 gets released, and maybe even after...using Eleventy Serverless or the Node API might be overkill for what I'm trying to do.

If anyone has any other ideas, I'd love to hear them. I don't use static hosting due to some server side processes that I maintain on my own and so while I do have the power of a server-side environment behind my website, I definitely want to stay as static as possible.

---

Scenerio: I'm trying to restrict access to some content on my personal site and have set up a (already implemented) method of authenticating who has access and who doesn't, setting a cookie for people that have access. Restricting access to pages is the easy part, the webserver can handle access to specific paths depending on whether a cookie was sent or not. Whats more difficult is the handling of index pages where I'd like to display the hidden pages to those who are "logged in" and keep them hidden from the index for those who aren't.

The way I see it, I've got a few ways of handling this:

1. Render 2 versions of the index pages for both the hidden and unhidden content on them, then use some URL rewrites to swap them out for authenticated visitors, downside of this is that it'll be cumbersome to manage separate pages beyond 2 variations.

2. Use Eleventy Serverless (post 1.0.0) to render the authenticated specifically for authenticated visitors and display that instead.

3. Run Eleventy via a node script on a express server as a seperate process listening on a proxied port to replicate the functionality of serverless on my VPS.

4. Retrieve content via client-side logic (would like to avoid this if possible)

[noelforte]

Did some looking into this, while I think using serverless infrastructure might be a little too specific for what I'm trying to do, I think the Node API forthcoming in 1.0.0 will do what I want, setting up hooks to serve different content based on context. I'll mark this off for now until I either have more information to share or others have insight to offer.