Oh goodie, now there's a canonical description of how to make a US gov't website for all the phishers out there...
Introducing U.S. Web Design Standards
31–40 of 90 posts
Re: Introducing U.S. Web Design Standards
#32Nice, they use SASS/Bourbon/Neat for their styling.[0][1] Huge fan and recommend it to anyone using Ruby for web development. [0] - https://playbook.cio.gov/designstandards/getting-started/ [1] - http://bourbon.io/
I second this recommendation, even for those not using Ruby! The Sass compiler is written in Ruby but that doesn't mean you have to know Ruby to use Sass.
Re: Introducing U.S. Web Design Standards
#33Doesn't this make it incredibly easy for phishing websites to be created? I suppose such websites would exist anyway, but this would certainly diminish a user's ability to differentiate between a legitimate .gov or another page with malicious intent at a glance.
Re: Introducing U.S. Web Design Standards
#34When looking at a random website I expect to know roughly what I'm looking at within 20 seconds - max. Ideally 5 if not text heavy.
>shared set of tools [...] government websites
That is exactly what I wanted to know. Pity thats hidden on page 3 and I had to read credits & something about some Joanne's problems first.
The narrative story flow is fine...but you've got to give something solid up front. e.g. Do the startup cliche and say how you're revolutionising the world in a short sentence. Then launch into the speech about Joanne's problems...
Re: Introducing U.S. Web Design Standards
#35When design becomes a standard, is its purpose not lost?
No, it's fullfilled. The design of the average table, pencil, glass, fork, spoon, text-based book etc. is fairly standard (save for few ornamental details).
That's not because its purpose is lost for design conformity, but because those are peak designs that work best for what they need to do.
The only purpose design for government sites has is to be able to give information quickly and in a legible and accessible way. No artistic ambitions here. That can be standardized very well.
Re: Introducing U.S. Web Design Standards
#36Nice, they use SASS/Bourbon/Neat for their styling.[0][1] Huge fan and recommend it to anyone using Ruby for web development. [0] - https://playbook.cio.gov/designstandards/getting-started/ [1] - http://bourbon.io/
I second this recommendation, even for those not using Ruby! The Sass compiler is written in Ruby but that doesn't mean you have to know Ruby to use Sass.
If you can do without the latest of the latest in Sass I highly recommend using a libsass implementation. So much faster than the Ruby version!
OT: I also like that they've used a BEM-like approach, although I personally prefer a double underscore as separator between elements.
Re: Introducing U.S. Web Design Standards
#37Oh goodie, now there's a canonical description of how to make a US gov't website for all the phishers out there...
The design level is the wrong level to solve the fishing problem. Any site can be immitated, and 100 differently-looking sites can be immitated with almost the same ease as 100 same-looking ones...
For one, you don't even have to create anything -- you just download the original assets, and merely inject some JS or change a form destination in your version.
So mirrorring (wget -mkp http://foo.bar) designs is not that more difficult...
Re: Introducing U.S. Web Design Standards
#38"It doesn't do anything useful and it only loads Saturdays at 3am, but it sure has some syntactically awesome stylesheets!" ...Anyway, it sounds good on paper.
Re: Introducing U.S. Web Design Standards
#39Nice! I did notice some of the component definitions look like very close paraphrases to Semantic UI's component descriptions though, but I'll take that as a good thing.
Re: Introducing U.S. Web Design Standards
#40When design becomes a standard, is its purpose not lost?
No, it's fullfilled. The design of the average table, pencil, glass, fork, spoon, text-based book etc. is fairly standard (save for few ornamental details). That's not because its purpose is lost for design conformity, but because those are peak designs that work best for what they need to do. The only purpose design for government sites has is to be able to give information quickly and in a legible and accessible wa…
> average table, pencil, glass, fork, spoon, text-based book etc. is fairly standard (save for few ornamental details).
Except that's the point of the OP's comment. These items actually do not have any explicitly declared standard like this design standard published by the government. Design became standardized through people landing on a good design, not through a government mandate.