The document discusses copy for a website homepage and different approaches to managing it. It describes the traditional process of committing code changes with copy to a repository and deploying them. It then introduces an alternative using a Ruby gem called Copycopter Client that allows editing copy without needing to deploy code, provides automatic synchronization, and a standard API for Ruby and Rails applications. The gem is presented as a way to more easily manage copy without worrying about deploys or technical steps.

2. Every app has copy.

4. <div id="letter">
<p><strong>Hi, we're thoughtbot.</strong></p>
<p>We created Trajectory to solve our own problems.</p>
<p>
<span id="with-love">Love</span>,
Developers like you.
</p>
</div>

6. “Hey, we have the final copy for the homepage.”

7. $ git commit -am “wip”
$ git checkout master
$ git pull
$ vim app/views/homes/show.html.erb
$ git commit -am “New homepage copy”
$ bundle exec rake
$ git push
$ git log
$ git push heroku master

8. “Hey, we have some changes for the homepage copy.”

9. We have a better idea.

10. $ gem install copycopter_client

11. CopycopterClient.configure do |config|
config.api_key = 'magic api key numbers'
end

12. <div id="letter">
<p>
<strong>
<%= t(".greeting",
:default => "Hi, we're thoughtbot.") %>
</strong>
</p>
<%= t(".letter",
:default => "We created Trajectory to solve our own problems.") %>
<p>
<span id="with-love" class="with-love">Love</span>,
<%= t(".signature", :default => "Developers like you") %>
</p>
</div>

17. • Don’t worry about copy when developing
• Edit without a deploy
• Non-technical team members can edit
• Automatic synchronization
• Minimal performance impact
• Standard Ruby API (Ruby/Rails I18n)