Closed hermwong closed 10 years ago
After some thought, it may make more sense to model the design after build.phonegap.com.
phonegap.com is designed as a website.
build.phonegap.com is designed as a web app.
Build's design of buttons, labels, and grid views make more sense for an application. However, Build's design is a little dated, so we can be loose with how we follow it. For example, I think the text size should be changed and the modal dialogs may look simpler (for our sake).
Thoughts?
Let's discuss some of the expected features of the UI and then create issues for each:
Anything else?
Those look like all of the features that we need for an initial releasable product.
Cool.
I'll create some sub-tasks for these.
for visual design assets/styling, i'll forward you to the following:
for icons: we've traditionally used icons from the "Picons" family. Alternatively, you could try using icons found on topcoat.io/icons.
link/action colour, PhoneGap blue: #27a1c5
Font: again, traditionally, we have used Adobe Clean (at the behest of Adobe Branding) for both Phonegap.com and Build, with Helvetica-Neue as the fall back, then Arial, then San Serif. Helvetica-Neue is the longest running font used for PhoneGap (it is the logo font). Topcoat uses Adobe Source Sans.
Edit: removed the direct link to Picons.
Great, thanks. That should be enough to get us up and running!
Closing this issue. I think it's served the purpose of initial design.
Model the UI after the phonegap.com design.