Difference between revisions of "Wave"

From CoTech
Jump to: navigation, search
Line 22: Line 22:
 
*Specific expertise (web design: Print)
 
*Specific expertise (web design: Print)
  
""Skills""
+
'''Skills'''
  
 
*Design workshops
 
*Design workshops
Line 30: Line 30:
 
*Liaison
 
*Liaison
  
""Collaboration software""
+
'''Collaboration software'''
  
 
*Evernote
 
*Evernote
Line 40: Line 40:
  
  
""Web design""
+
'''Web design'''
  
 
*Uxpin
 
*Uxpin
Line 53: Line 53:
 
*Zeplin/Avocode
 
*Zeplin/Avocode
  
''''Web front end code''''
+
'''Web front end code'''
  
 
*Basics are html, css, javscript and in our case php for server side.
 
*Basics are html, css, javscript and in our case php for server side.

Revision as of 21:42, 16 November 2016

Wave grey reversed sq.png
  • Hastings
  • megazord@wave.coop
  • 01424 235000
  • Main contact: Felix Lozano
  • Main business Web development, Design, Marketing
  • Sector public sector, third sector/charities, education


  • Specific expertise (web design: Print)

Skills

  • Design workshops
  • Siteplanning UX/UI
  • Design concepts/visuals)
  • Basic protoyping (most of our clients cannot afford high level prototyping in budgets)
  • Liaison

Collaboration software

  • Evernote
  • Basecamp
  • Skype
  • Googledrive
  • Email
  • Taiga


Web design

  • Uxpin
  • Invision
  • Illustrator
  • Photoshop
  • Sketch
  • Indesign
  • MS Word
  • CC Libraries/Lingo
  • Nounproject
  • Zeplin/Avocode

Web front end code

  • Basics are html, css, javscript and in our case php for server side.
  • We use Dreamweaver for most web based activities, because we have the Adobe bundle.
  • We use scss as the preprocessor. For scss processing, originally I used Terminal, then Compass, then Scout, but DW 2017 has it built in now.
  • For javascript mostly work in jquery.
  • For html5 canvas use Adobe Animate, but most of the work is actually writing javascript.
  • For cms we like WordPress but also have done Drupal, bespoke cms etc…
  • We use lots of other bits and pieces to do various things that the Adobe products miss out. Eg to tidy, format and “beautify” code, to check that accessibility standards are being met, to test for different browsers and devices, to do speed tests, to improve spelling and grammar, to optimise SEO etc.
  • Some of the ideas in Foundation as a source for certain theming issues but tend to recode them our own way.
  • We test and dev using mamp locally in the early stages of theming.