Trying to apply the DRY Principle in relation to Framework Dynamics

[floatingpurr]

I'm trying to wrap my head around how to apply the DRY principle in a Framework-based project.

Here's my experiment

Two possible generalizations

1. Inferring the TOC at build time

In my experiment, there's a collection of monthly charts. I'd like to have a specific section for each chart listed in the TOC. AFAIU, the TOC is created at build time. So, to render it properly, I had to repeat all the sections in the md like this:

 ## Gennaio

 ```js
 display(monthlyPlot(topics.filter(d => d.date.getUTCMonth() === 0), { width, minWidth }))
 ```

Ideally, this could be rendered with a loop and using a custom md function (not yet implemented in Framework, see #895). Given the current state of Framework, is there an alternative (and better) pattern to my approach?

2. Sharing content between index and some parametrized routes

In my example, the main content is index.md. Moreover, there is an archive section as well, that contains parametrized routes for similar pages. Currently, index.md and years/[year].md are separate files. I'm wondering if i can somehow manage in single page structure that handles both the content in the index and what is in years/[year].md.

I tried to tinker with the config file, mapping in pages the index route to the path /years/2025. Then, I was able to build a custom rendering for the index, by building a custom logic around observable.params.year, but I'm pretty sure this is not a good approach. Any hints?

Bye

[mbostock]

Sounds like you could use a page loader to generate the page dynamically?

[floatingpurr]

Hi @mbostock! Yes, it seems like the right approach to address what I described. I'll try it soon.

Thanks!