3 ms·

Hi, I'm one of the engineers who worked on this new dashboard. If anyone has a question, feel free to ask me here :)

by thejameskyle 11y ago

SEJeff 11y ago
Is it written in go, like most cloudflare things?
- philip1209 11y ago
  As far as I understand, it's still in PHP.
- thejameskyle 11y ago
  The WWW API is written in PHP which interacts with a lot of Go codebases elsewhere in CF. We're going to be publishing more engineering-related blog posts about the new dashboard in the coming days/weeks.
  - MichaelGG 11y ago
    Out of curiosity, why PHP?
    - thejameskyle 11y ago
      The API hasn't been completely rewritten like the front-end. It was already in PHP and so it stayed in PHP.
rhc2104 11y ago
Have you guys considered A/B testing different parts of the new design to figure out which parts of the new design are more effective?
deleted 11y ago
[deleted]
- jbergknoff 11y ago
  "less usable than before" -- this is completely the opposite of my experience. Kudos to cloudflare for ditching the dysfunctional infinite scroll.
- corobo 11y ago
  Forgive me for coming off as a jerk but I think you might be getting phased out of the comments as your site - at least the one pulled from your comment - is not amazingly designed for a UX/UI person. You're using #666 text on a black background on an almost too-minimal design, which is really hard to read even as someone that doesn't have much trouble in the vision department. Do you have any other sources of work to sell yourself a bit better on the design credibility side? You're also using a heck of a lot of hashtags on the page that aren't even links, what's behind that?
TimWolla 11y ago
What is this 'Shared Accounts'? Can one link an organization account to a personal account in the future, instead of sharing a password?
- thejameskyle 11y ago
  We support having multiple users within an organization account, we're publishing a blog post about it later this week.
manigandham 11y ago
I actually just sent in a suggestion/support ticket last week but here's what I think would be an improvement: Right now the page rules system seems like an added feature but I think it should be the heart of the settings system. When a new site is created, it would be logical to just create a default page rule that covers everything like "example.com/*" Each rule can have a summary of settings as they do now and all the other separate pages can go away. Speed, Caching and ScrapeShield can just be settings for each rule instead of full pages. It'd be a lot faster to manage settings this way and more natural to view a site's settings as a cascading set of rules with their own configuration. Likewise, Traffic can probably just be made another tab under Firewall. Hope that makes sense.
- terinjokes 11y ago
  We're working internally on a number of different ways of how to integrate Page Rules better into the user interface, include a few ideas on these lines.
- rdl 11y ago
  Traffic actually originally was underneath Firewall, but Traffic will expand to other kinds of traffic/log related data in the future, so we decided to break it out now. (i.e. this is the 1.0 release...we have a LOT of stuff planned for the next months in various areas)

Hi, I'm one of the engineers who worked on this new dashboard. If anyone has a question, feel free to ask me here :)

SEJeff 11y ago

Is it written in go, like most cloudflare things?

philip1209 11y ago
As far as I understand, it's still in PHP.
thejameskyle 11y ago
The WWW API is written in PHP which interacts with a lot of Go codebases elsewhere in CF. We're going to be publishing more engineering-related blog posts about the new dashboard in the coming days/weeks.
- MichaelGG 11y ago
  Out of curiosity, why PHP?
  - thejameskyle 11y ago
    The API hasn't been completely rewritten like the front-end. It was already in PHP and so it stayed in PHP.

rhc2104 11y ago

Have you guys considered A/B testing different parts of the new design to figure out which parts of the new design are more effective?

deleted 11y ago

[deleted]

jbergknoff 11y ago
"less usable than before" -- this is completely the opposite of my experience. Kudos to cloudflare for ditching the dysfunctional infinite scroll.
corobo 11y ago
Forgive me for coming off as a jerk but I think you might be getting phased out of the comments as your site - at least the one pulled from your comment - is not amazingly designed for a UX/UI person. You're using #666 text on a black background on an almost too-minimal design, which is really hard to read even as someone that doesn't have much trouble in the vision department. Do you have any other sources of work to sell yourself a bit better on the design credibility side? You're also using a heck of a lot of hashtags on the page that aren't even links, what's behind that?

TimWolla 11y ago

What is this 'Shared Accounts'? Can one link an organization account to a personal account in the future, instead of sharing a password?

thejameskyle 11y ago
We support having multiple users within an organization account, we're publishing a blog post about it later this week.

manigandham 11y ago

I actually just sent in a suggestion/support ticket last week but here's what I think would be an improvement: Right now the page rules system seems like an added feature but I think it should be the heart of the settings system. When a new site is created, it would be logical to just create a default page rule that covers everything like "example.com/*" Each rule can have a summary of settings as they do now and all the other separate pages can go away. Speed, Caching and ScrapeShield can just be settings for each rule instead of full pages. It'd be a lot faster to manage settings this way and more natural to view a site's settings as a cascading set of rules with their own configuration. Likewise, Traffic can probably just be made another tab under Firewall. Hope that makes sense.

terinjokes 11y ago
We're working internally on a number of different ways of how to integrate Page Rules better into the user interface, include a few ideas on these lines.
rdl 11y ago
Traffic actually originally was underneath Firewall, but Traffic will expand to other kinds of traffic/log related data in the future, so we decided to break it out now. (i.e. this is the 1.0 release...we have a LOT of stuff planned for the next months in various areas)