Skip to content

Instantly share code, notes, and snippets.

@seahyc

seahyc/frontend_interview.md

Last active March 22, 2018 03:54
Show Gist options
  • Save seahyc/83494d6c7c546a1aef0a7323060160c1 to your computer and use it in GitHub Desktop.
Save seahyc/83494d6c7c546a1aef0a7323060160c1 to your computer and use it in GitHub Desktop.
Download ZIP
Customization and Configuration
Raw
frontend_interview.md

Customization and Configuration

Glints whitelabels its platfrom to several client. These are sites that share the same codebase as the main glints site, but has its custom styles and at times components.

An example is IE Singapore and JOS, vs main Glints.

How would you design our architecture to support flexible and extensible configuration/customization for whitelabel sites?

@tagraha
Copy link

tagraha commented Mar 22, 2018

I would say with Feature flag for an extensible feature toggle/flip. there are several approaches to achieve that. for example, we can control the feature toggle/flip with envar; or maybe we can use REST api. We can get complete control over releasing new functionality to our users based on their user location, membership status, and whatever else we can think of. Feature flags are a powerful technique, allowing teams to modify system behavior without changing code..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment