UserExperience: Difference between revisions

From SoylentNews
Jump to navigation Jump to search
No edit summary
m (Obfuscated style@soylentnews.org to hide from spammers)
Line 1: Line 1:
The User Experience team develops art, CSS, and other UI elements and is connected with the Dev team. Take a look around at what we are working on currently and what we'd like to start working on next, if you see anything you might be able to help with just contact '''style@soylentnews.org'''.
The User Experience team develops art, CSS, and other UI elements and is connected with the Dev team. Take a look around at what we are working on currently and what we'd like to start working on next, if you see anything you might be able to help with just contact '''style AT soylentnews.org'''.


'''See also: [[Style]]'''
'''See also: [[Style]]'''

Revision as of 13:27, 22 January 2019

The User Experience team develops art, CSS, and other UI elements and is connected with the Dev team. Take a look around at what we are working on currently and what we'd like to start working on next, if you see anything you might be able to help with just contact style AT soylentnews.org.

See also: Style

There's a lot of documentation on CSS work being done and you can find some notes on future UI Design here.

Who we are

User Experience Team Main Page

nick

position

timezone

mrcoolbp Interim Leader UTC-5
audioguy On Occasional Loan UTC-8 (PST)

Retired Members

Former editors that have lost their roles due to inactivity or retirement

Retired members

nick

position

timezone

FrogBlast Art Team ?

Current Projects

Soylent Swag

  • flesh out the store with more options
  • come up with SN memes or nerdy sayings for products
    • prospectacle has ideas for a "monogram" graphic for formal wear

Site Graphics and Icons

  • may need to add some new topics (work with Editor's Team)
  • separate topic icons for non-red themes (only /dev/random, meta, Answers, and maybe Soylent)

Todo

  • update the comment expand/collapse buttons (cross-theme compatibility)
  • Define single column layout requirements - see: this mobile layot sketch linked on the Mobile Design page.
  • Typographic and typesetting guidelines (with LaminatorX) - awaiting feature request, then work with CSS ppl on a specification
  • Weekly comic