url_for() equivalent to dynamically pick static files paths

[DreamDevourer]

This can be a little confusing to understand, so I will give you a case:

I have the following directory structure:

• @src/
  --static/
  ---styles/
  ----style_base.css
  ----style_module.css
  ----style_template.css
  ---styles_engine.css
  --base.html
  --index.html
  --about/
  ---about-me.html

For context, the "styles_engine.css" file has some {% include "style_*.css" %} tags there to import all the other CSS files.

The use for the url_for() would be great for the "base.html" file, where it is imported to all other HTML templates. In practice, manually importing the "styles_engine.css" file works on the index.html if I do the raw path method, but it breaks on a subdirectory in the case of "about/about-me.html". url_for() would fix the paths dynamically.

Another example of this, is if I use any image or font inside the CSS file, it would break depending on the directory position of the template.

Does anyone have any idea of any alternatives to the url_for()? Currently my turn around is to do semthing like this:

{# This is the global.html #}
{% set stylesEngine = "styles-engine.css" %}

{# This is the base.html #}

{% from '_partials/global.html' import stylesEngine %}

{% if internalDirectory %}
        {# Used for pages/templates inside sub directories #}
        {% set stylesEngine = "../styles-engine.css" %}
{% endif %}

<link href="{{ stylesEngine }}" rel="stylesheet" type="text/css" />

In this case "internalDirectory" is set manually inside the template.

[NickCrews]

I'm sorry, I don't think I understand your problem still. What would your code look like if this feature was implemented? Is this a jinja2 problem, or a staticjinja problem? Maybe if you link to a repo with the actual code and walk through what is annoying that would help. I'm tempted to say this isn't in the scope of staticjinja, and if you need this feature you should just write a script yourself that uses jinja.