Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upwhitelabeling strategy? easy html/css for jr. programmers #888
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
process-bot
Jul 28, 2017
Thanks for the issue! Make sure it satisfies this checklist. My human colleagues will appreciate it!
Here is what to expect next, and if anyone wants to comment, keep these things in mind.
process-bot
commented
Jul 28, 2017
|
Thanks for the issue! Make sure it satisfies this checklist. My human colleagues will appreciate it! Here is what to expect next, and if anyone wants to comment, keep these things in mind. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
Falieson
commented
Jul 28, 2017
Falieson
closed this
Jul 28, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Falieson commentedJul 28, 2017
•
edited
Edited 1 time
-
Falieson
edited Jul 28, 2017 (most recent)
I've been considering Elm for a while and am now in a position to start a new project and stack the latest version against the needs of my team. The main push-back against using React is the long-term vision of our project, for it to be easy to whitelabel by companies who don't have sophisticated programming resources.
With a templating language (the prototype was made in spacebars) its easy to hand over .html and .scss files and the customer goes to town making the components look and structure the way they want.
With React (and I think Elm) the customer could provide the html/css but a javascript developer has to finish the job, am I wrong? Is there a way to approach white labeling for functionally composed frameworks?
Thanks!