Basic Site Info

While I can see the use-case for needing this information, I don't think it makes sense to ship this information on every ce-api page response, since it would grow all the responses, while the information is usually only needed once. Thus, it seems to be better solved with a dedicated endpoint + a separate request to fetch it from nuxt. When done so, we shuold be able to leverage caching in nuxt such that the request is done only once in the server instance, and cached then.

On how to providing the information, I don't think there is a pre-existing API for it. So it makes sense to add it.

However, when adding it: The question becomes, what exactly shall we add? It seems very use-case specific what shall be added, there are definitely more config-settings that one might want to use in the frontend, for example a configured google analytics key.

Thus, I feel like we could build a solution for exposing any kind of config as "Site-info" and make it configurable, e.g. by specifying the keys you want:
system.site:name
system.site:slogan
system.site:mail

and just output a data structure like
{ system.site : {
name: "..",
slogan: "..",
mail: "..."
}}

and make the result a public API, e.g. at /lupus/site-info

I guess, that would make sense to provide as a new optional module, Lupus Decoupled Site Info ?

Sounds like a perfect idea to me, and as you say it can be added to depending on your needs. Totally agree on the lookup once and cached on Nuxt end. We can achieve this via useState

I created the Lupus Decoupled Site Info module and added some initial configuration.

@useernamee great news. This will be very helpful. My only suggesting is the API route /api/lupus/site-info changes to /api/site-info seems more appropriate to me. Great job!

that seems pretty good already, thank you!

A few remarks:
- please check the MR comment
- I am not sure about the /api/lupus prefix also, what about just /api/site-info or /lupus-site-info ?
- We need some configuration form or README that documents how to use it
- We need some basic test coverage before merge!

> I am not sure about the /api/lupus prefix also, what about just /api/site-info or /lupus-site-info ?

I went with the /api/site-info but this is also a limitation of the Rest resource which I picked for the task, since it would seem nicer to have a resource at the endpoint of /site-info, for uniformity.

thank you! that looks pretty good now. I've added one remark with this missing value though, please check MR review.

I removed the missing config option and added a watchdog error for that case instead:

{"system.site":{"name":"Drush Site-Install","slogan":"lupus.digital Publishing","mail":"admin@example.com","missing":null},"missing":{"missing":null}}

thank you! Reviewed it and edited a bit. Seems good to go now!

However, I did not test it yet. So it still needs a manual test before it's ready for merge!

Test failed, cache is not being invalidated after config changes.

To reproduce:

• Install lupus_decoupled_site_info module
• Go to /api/site-info -> Info is correct
• Go to /admin/config/system/site-information and update the slogan
• Go to /api/site-info -> Info is outdated

Thank you @arthur. I wasn't paying attention to caching.

- Added cacheable dependencies to the response.
- Cache is tested.

Great, thank you :)

Tested it locally -> RTBC ✅

Thank you! Merged!