Functions called renderSomething (e.g. renderContent()) are such an anti-patten in react. You just want another component at this point!

Whew! Did you know that you can pass data to the @11ty.dev `renderContent()` filter?

You do now!

github.com/11ty/11ty-we...

I might need a reduced test case 😭 what about:

{% for item in components %}
{% for c in collections.components %}
{% if c.data.title | slugify == item.type %}
{{ c.data.template | renderContent("njk", { headingText: item.headingText }) }}
{% endif %}
{% endfor %}
{% endfor %}

How to turn your portfolio into content 😉

#3drendering #portfolioinmotion #archviz #visualizationartist #rendercontent #architecturalvisualization #creativestudio #3dportfolio #digitalarchitecture #visualcontent #renderinspo #3dsmax #archdaily #cgiartist

Functions called renderSomething (e.g. renderContent()) are such an anti-patten in react. You just want another component at this point!

Ok. It works properly for both posts & pages now. Pages in WordPress don't have tags & categories. Posts do.

- getDetails() exits if a page is sent to it, it only runs for posts
- renderContent() only gets & shows categories & tags for posts, not pages

Finally, consolidated renderPosts() & renderPages() into a single renderContent() because the logic was the same for both.

The Diagnosis: The previous renderContent function split content by Double Newlines (\n\n+). However, in your source text (specifically KRNL-11.1), the Header (### Vectors...) is likely followed immediately by the List (- **Epistemic...) with only a single newline. #vibecoding #debugging