Yes, quite a lot of the time! Pretty much any page which fills the two columns of text has had to have words and phrases chopped down to fit. Do you ever struggle to explain such complex subjects in such a minimal way? It can never replace experience and training in a field, just supplement it and give those starting out a helping hand. There's really no need to feel threatened about giving this sort of knowledge away. We're constantly looking for ways to improve our own processes and tools We're constantly looking for ways to improve our own processes and tools, and these shared projects are a great source of information, so let's see more of them out there. There's a lot of companies out there who are already giving away great resources for free, and we make use of a lot of them. Do you hope your guide and approach to sharing things will encourage others to do the same?ĭefinitely. No man is an island, and most of the time your files won’t be either! Good organisation is essential as it saves a lot of time for other people on the project You guys are very open about your working processes. Working with developers, both internally and externally, has taught us a lot about how to approach the transition from design to code. So any knowledge we can give to get the up to speed quickly is a great help. And if we're hitting these problems then it's a pretty sure thing that others out there are too.Īlthough there's a massive public aspect to the handbook, we still use it as internal teaching tool, and to inform new starters how we work as a studio. A lot of what's added to the handbook is based on our experiences as a studio, and areas where we've had pain points in the past. Was the new Design and Development chapter included following feedback or just things you wanted to share? For this release, I've managed to tick off every item in there. When it comes to adding new content I just go through that list, getting as much of it in there as there's time for. I keep a simple to do list where I'll note down any new pages I'd like to add as I come across new knowledge or tips. The only criteria for entry is that the information is useful. The allocation of the new content is based purely on things that I learn, or, new features which Adobe introduce The allocation of the new content is based purely on new things that I learn, or, as with much of the Photoshop chapter, new features which Adobe introduce. The other extra content is pretty evenly split between Pixel Perfect Principles, Accessibility, and the Photoshop chapters in the handbook. Sound advice from the ustwo team Aside from the new Design and Development chapter, what areas have been expanded upon? Grab attention with high contrast and large, bold type, or push items back with lower contrast and smaller, lighter type.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |