Writing CSS on Growing Teams
写CSS在成长的团队
This fall,my team started a new project and for the first time in a long while, I was working with another developer as I started to write the styles for the Interface.
今年秋季，我的团队开始了一个新的项目，并在很长一段时间，我正与另一个开发人员，我开始写的界面风格的界面。
In fact, I started the styles, and then went on vacation while they took over.
事实上，我开始的风格，然后去度假，而他们接手。
This project has been an exercise in writing modular CSS , which I love, when working in a team .
这个项目已经在CSS编写模块的练习，我的爱，在一个团队中工作时。
Having been a solo front-end developer for quite some time , this was a new challenge to me .
作为一个单独的前端开发人员相当长一段时间，这对我来说是一个新的挑战。
When you want your CSS to be reusable , how do you want your CSS to be reusable , how do you have several people working in git branches on different pages without writing completely separate styles?
当你想你的CSS可重用的，你想怎么做你的CSS可重用的，你怎么有几个人工作在git分支在不同的页面上没有写完全不同的风格？
surprise:it's not really about how we write CSS , it's about the process.
惊喜：这真的不是关于我们如何写CSS，它的过程。
Communication
通信
Communication is the biggest piece of making this work .As we work throughout the day ,we talk about the styles we're writing and where they might be used across the application, so the other person knows how work in progress could impact the parts of the application they're focused on
沟通是这项工作的最大组成部分，正如我们在工作中的一天，我们谈论的样式，我们的写作，他们可能会在整个应用程序，因此，其他人都知道如何工作的进展可能会影响到他们的应用程序的部分
For example , if I change a wrapper to meet the new design spec and want to be consistent across the entire application
例如，如果我换一个包装器来满足新的设计规范，并希望在整个应用程序中保持一致
when my coworker normalizes buttons in one branch, they let everyone know that this will be taken care of for the whole team when that branch gets merged into the master branch.
当我的同事将按钮中的一个分支，他们让每个人都知道，这将是照顾整个团队当分支被合并到主分支。
Code review
代码审查
I’ve worked on teams that did code reviews,but my current team didn’t always do them as we worked . As the team grew ,we decided to incorporate code reviews into our process . The best part of a code review is learning from each other . Maybe the way I’ve done a layout works , but could it be better?Are there styles I’m not familiar with that would make it better?
我曾经在做代码审查的团队工作，但是我现在的团队并不总是在我们工作的。随着团队的成长，我们决定将代码审查纳入我们的过程中。代码审查的最佳部分是互相学习。也许我做了一个布局的方法，但能更好吗？是否有我不熟悉的风格会让它更好？
When we review code , we discuss our modules to ensure everyone agree they’re going to be best way to move forward . When talking through how to use SVGs in our code ,for instance , we discuss when it’s appropriate to use them as background images as opposed to images ,or inlining them by putting the SVG code right into the template
当我们回顾我们的代码，我们讨论我们的模块，以确保每个人都同意，他们将是最好的方式向前发展。当讨论如何在我们的代码中，使用SVG为实例，讨论了在适当的时候使用它们作为背景图像相对于图像，或内联他们把SVG代码到模板
Documentation
文档
Finally , we came up with what’s important to our team when writing CSS and we documented that . We use the ideas from Jonathan Snook’s SMACSS to guide us , along with explaining features of Sass we want to stay away from (such as nesting ), so the entire team has an easy reference.
最后，我们想出了什么是重要的对我们的团队写CSS时我们发现。我们用乔纳森的思想对smacss指引我们，随着解释特征SASS我们要远离（如嵌套），所以整个团队有一个简单的参考
By making this explicit , we can refer back to it for reminders as we review code . In the near future , we also hope to build a style guide to further document our work . That way ,we’ll have documented how we want the code written , and we’ll have a more visual documentation of the styles we’re using to retain consistency as we continue working on the application .
通过把这个明确的，我们可以把它作为提醒，因为我们审查代码。在不久的将来，我们也希望建立一个样式指南来进一步证明我们的工作。这样，我们就已经记录了我们想要的代码，我们将有更多的视觉文档的样式，我们使用的是保留的一致性，我们继续工作的应用程序。
As a team grows there are always bumps along the way , but it’s been a great challenge to start documenting our process , thinking about how we write CSS in a more formal way , and reviewing it together to make sure we’re all on the same page .For me , the challenge of going from being the only person writing everything , to adding new team members and working together , has been fantastic.
作为一个团队的成长，总是有颠簸，但它已经开始记录我们的过程杰出的挑战，我们如何写CSS在更正式的方式思考，回顾起来确保我们都在同一页上。对我来说，离开是唯一的人写的一切挑战，加入新的团队成员一起工作，真是太美妙了。