Github user seanbarclay commented on the pull request:
https://github.com/apache/couchdb-fauxton/pull/204#issuecomment-69387245
The reason behind the dark code editor was to bring in some consistency and
familiarity with modern developer code editors (e.g. SublimeText), which
leverage a dark, high contrast palette. It helps to differentiate the
functionality a bit between normal UI controls and code. The docs and the
editor were designed to be dark to be consistent. However, they were also
designed with a lot of functionality that hasn't been baked in yet (e.g.. table
views). I designed a lot of this close to a year ago and it's just starting to
make it's way in , which is a good sign... but there's still a long way to go.
Also, a few developers that I tested with preferred the dark theme vs. a
white or lighter theme. It seemed like a safe bet.
That being said, we can definitely continue to tweak the contrast on the
colors to pop or be toned back. The colors we submitted are meant to help
developers differentiate between keys (white) and values such as strings
(teal), numbers (light blue) and boolean (orange). I'm not opposed to shifting
colors to help with contrast and readability.
I'll take a look at lightening up that green and post an update soon.
Cheers
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
