#Architecture: multi-template with dynamic API-driven config

1 messages · Page 1 of 1 (latest)

coral pebble
#

hey! Need architecture structure advice for multi-template system:
my app needs to support multiple visual templates (template 1, 2, 3, etc.) so
the template selection gonna come from a backend endpoint like /api/config {template: "1"}. Has anyone built a similar multi tenant system? what approach worked best?

echo wedgeBOT
#

🔎 This post has been indexed in our web forum and will be seen by search engines so other users can find it outside Discord

🕵️ Your user profile is private by default and won't be visible to users outside Discord, if you want to be visible in the web forum you can add the "Public Profile" role in id:customize

✅ You can mark a message as the answer for your post with Right click -> Apps -> Mark Solution
(if you don't see the option, try refreshing Discord with Ctrl + R)