11. Once our translations are done, we can re-enable the Overlay module and click "Save configuration." You can also switch the site back to English by going to the home page and selecting English from the Languages block. Spotlight: Content Translation When it comes to translating your site's content in Drupal 7, we have two possibilities. There is the core "Content translation" module and the contributed "Entity transla- tion" module. They have quite different approaches to translation. The major difference is that "Content translation" lets you create multiple versions of the same content in different languages and associates the translated versions together as a set. Each trans- lation is an individual node, so for each piece of content on your site, you will have as many nodes as you have translations. For example, an English node with three other language translations (say, Danish, French, and Spanish) will be a set of four full nodes on your site. With "Entity translation," you only have one node (an entity), and each field on the node will have multiple values, one for each translation. Both systems have pros and cons, and you could mix and match both of them on your site for different content. Having multiple nodes can cause problems when you have associated metadata that you don't want spread out over several nodes. For example, if you have an event node and you want people to sign up for the event, you don't want people to sign up across four different nodes, depending on the language they read it in. You'd want one, central list of all the attendees for the event, regardless of language.