In recent years, the practice of designing websites in HTML prototypes has become increasingly prevalent. And with a good reason – designing "in-browser" has many merits over static mock-ups.
But how do we ensure a good process? When do we move from design to development? And is it the time to implement the prototype in Drupal?
Here are some insights from a session on Prototypes and Drupal at DrupalCon Barcelona, which answers these questions.
In Browser Designing
When is it appropriate for the client to look at your Prototype?
"We give the prototype URL to the client the day 1" good tip in Designing in browser #DrupalCon session
— Cristina 🎗 (@chumillas) September 23, 2015
A different point of view
IN #DrupalCon prototype session :"Always trust users". In security session: "never trust users"
— Kaja Jacobsen (@kajajacobsen) September 23, 2015
Talking about Styleguide
Our Services
Customer Experience Management
- Content Management
- Marketing Automation
- Mobile Application Development
- Drupal Support and Maintanence
Enterprise Modernization, Platforms & Cloud
- Modernization Strategy
- API Management & Developer Portals
- Hybrid Cloud & Cloud Native Platforms
- Site Reliability Engineering
