Architecture: multi-template with dynamic API-driven config
Unanswered
Polar bear posted this in #help-forum
Polar bearOP
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?
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?
1 Reply
Polar bearOP
trying to figure out the cleanest folder structure, same content/components across all templates, only styles differ