# Zola as (tower) service

**URL:** <https://zola.discourse.group/t/zola-as-tower-service/2302>\
**Category:** Feature requests\
**Created:** [September 24, 2024, 2:38pm UTC](https://zola.discourse.group/t/zola-as-tower-service/2302 "2024-09-24T14:38:48Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ARitz-Cracker](https://yyz2.discourse-cdn.com/free1/user_avatar/zola.discourse.group/aritz-cracker/32/1320_2.png) [@ARitz-Cracker](https://zola.discourse.group/u/ARitz-Cracker)\
**Post date:** [September 24, 2024, 2:38pm UTC](https://zola.discourse.group/t/zola-as-tower-service/2302/1 "2024-09-24T14:38:48Z")

</div>

The more I used Zola and its accompanying Tera templating, the more I fall in love with it. That said, eventually I may want to use it with user-tailored content. Though I don’t want to change anything with the way Zola currently structures webpages.

I propose having Zola importable as a tower/axum service, I imagine it working exactly like `zola serve`, except it allows you to provide the `extra` data at runtime. This keeps the scope of the service minimal, as it assumed that layers would handle everything else.

What do you guys think?