I'm working on a community webapp for sharing content for a TTRPG (using their amazingly amazing creator license) and I'm wondering what the thoughts are behind partial hydration vs fully static pages.
Many (most?) of the creations that are going to be shared are nothing more than fill-in-the-blank data for custom elements, so there's not a lot going on. So for those types of entries I'm wondering if partial hydration is a better option instead of having to re-build the HTML each time something is change. When a page of such data is requested the server builds the custom element and sends it to the client which puts it where it needs to be and BOOM! Instant data.
Part of my reasoning for thinking this way is that later on (when I get around to it :p) these datapoints are going to be included in other documents. Think of one page for creating a bunch of special abilities/powers then on the "create class" page you include all the abilities/powers you made. I'll have to hit the database for the data anyway, I won't be pulling in an entire HTML page just to scrape the little data I need. Of course for those fuller-featured pages it'll be static all the way.
Thoughts?