A feed can just be a static file that’s updated with every change. The definition of not static is if you need to do processing on the backend, which you don’t.
How exactly do you think that static file gets ‘updated with every change’ automatically? You need a backend process or script to watch for changes, format the data, and rewrite the file to disk. That is backend processing.
I have the feeling you are confusing wordpress with “wordpress.com”. Because the alternatives you mentioned are alternatives to that.
// edit: correction because I think there is a misundestanding here.
I take the L and admit that what you say is possible. But for me it would not make sense.
Yes, static generation is an alternative. But my current setup is a WordPress/wp-cli publishing pipeline with scheduling, media handling, categories, archives, admin UI, and automation. Replacing that with Hugo or similar would be a migration/rebuild project, not just ‘remove the backend.’
A feed can just be a static file that’s updated with every change. The definition of not static is if you need to do processing on the backend, which you don’t.
How exactly do you think that static file gets ‘updated with every change’ automatically? You need a backend process or script to watch for changes, format the data, and rewrite the file to disk. That is backend processing.
I have the feeling you are confusing wordpress with “wordpress.com”. Because the alternatives you mentioned are alternatives to that.
// edit: correction because I think there is a misundestanding here.
I take the L and admit that what you say is possible. But for me it would not make sense. Yes, static generation is an alternative. But my current setup is a WordPress/wp-cli publishing pipeline with scheduling, media handling, categories, archives, admin UI, and automation. Replacing that with Hugo or similar would be a migration/rebuild project, not just ‘remove the backend.’