Chelsea and I recently designed and developed Vintage or Instagram, a cute little game that tests your ability to distinguish between photos actually taken in the 70′s and 80′s and those altered by the Instagram app to appear vintage. The gameplay mechanics (switching between photos, evaluating answers, keeping track of scores) is done with Javascript and jQuery. We decided to use WordPress to manage the photographs and other content.
It seems as though every time we begin designing a new WordPress theme, we quickly have to make typographical and layout decisions that promote good screen readability. These decisions can be very broad and influenced by other layout factors (such as text column width), but quickly work their way down to the minutiae of text color, size, and leading (line height). All these choices work together to influence the site’s readability.
Smashing Magazine published an article yesterday advocating the use of Adobe Illustrator as the primary tool for designing websites, from wireframe to graphic comp. On a good day, a majority of my time is spent using Adobe Illustrator, so I couldn’t agree more. Of course, Photoshop has its place in my web design workflow (for instance, making sure my sharp-edge vector objects do not end up fuzzy when converted to rasterized graphics), but Illustrator is superior in all the ways mentioned in the article.
This is the third part in a three-part series about using WordPress as a client area. Read the introduction here, and the second part here.
We needed to correct a few outstanding issues to make the client area totally off the hook:
These are quick little fixes, let’s tackle them one by one…
This is the second part in a three-part series about using WordPress as a client area. Read the introduction here, and the third part here.
The first challenge in establishing a WordPress client area is limiting the client’s access to project-specific posts. Out of the box, WordPress doesn’t exactly have this capability; it allows you to create users with a few specific roles, but these roles are designed to limit who can create and manage content, not who can access it. The user role names are emblematic of their purpose. They range from subscriber (a regular reader with a login and profile, but with no administrator or authoring privileges) to contributor, author, editor, and finally administrator.
