Designer News
Where the design community meets.
Chicago Senior Product Designer Joined over 8 years ago
Rachel hasn't posted any stories yet.
Finally! Love that you can link multiple libraries and that updating a component in one linked library file updates across all of the instances of that component in other files :o
I read the texture app on my ipad often, and fast company really pushes the design of their editorial features & includes interactive bits. May be worth exploring that! (texture has tons of great editorial features)
I too would love to see this, if you don't mind sharing! I never felt like Ai was as intuitive as sketch for me. Always interested in other design workflows
Had no idea they killed that, major bummer!
I second Jon's response! Building out a style guide and more intentional design system across the sites I work on. That, and business/brand strategy!
Prev/Next buttons at the end of a project page would help users navigate around the site a little more seamlessly! I found that as I got to the bottom of each project, I wanted to see more, but had to click your name pinned at the top then scroll down the landing page to your work.
Really enjoyed reading through your insights on projects... nice hierarchy used throughout!
*Edit: Just saw your comment about the nav! Nevermind :)
Design Matters by Debbie Millman! http://www.debbiemillman.com/designmatters
In favor of the right column! Dig that extended K
Designer News
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.
Have feedback?
Our process looks something like this:
PM, PD, & PMK have a monthly meeting together to discuss new projects
PD creates flows & mocks with copy that they write. Before uploading the mocks to Invision, we add underscores before and after copy that hasn't been "finalized" (mainly so devs know that they will need to update if looking at mocks) [Example:
___This is copy that needs some love___
]PD adds copy from designs to a google doc that is structured page by page and formatted (h1, body copy, links, buttons.) This is annotated with some notes on user behavior or pieces of the flow & includes a link to the invision
PMK is added to google doc and adds comments suggesting revisions
PM, PD, & PMK discuss revisions and approve (or, if not approved, the cycle continues until we reach a consensus or user test options)
Once everything has been approved, devs are added to the copy doc and add the "finalized" copy to the code