{"id":84,"date":"2009-02-14T06:24:02","date_gmt":"2009-02-14T14:24:02","guid":{"rendered":"http:\/\/fox-gieg.com\/tutorials\/?p=84"},"modified":"2009-02-26T14:10:21","modified_gmt":"2009-02-26T22:10:21","slug":"media-management-tips","status":"publish","type":"post","link":"https:\/\/fox-gieg.com\/tutorials\/2009\/media-management-tips\/","title":{"rendered":"Media Management Tips"},"content":{"rendered":"<p><strong>1.  Label files accurately.<\/strong><br \/>\nIt&#8217;s always a good idea to give your files clear, descriptive names.  But it becomes critical in collaborative projects, when your colleagues need to be able to distinguish between, say, a draft file that they can expect to change in the future, and a final file that they can expect to stay the same. <\/p>\n<p><strong>2.  Use version numbers.<\/strong><br \/>\nSave a new copy of your file each time you make a major change to it, adding a version number to the end of its name.  This is called &#8220;versioning.&#8221;  Not only can you find the most recent version at a glance this way, but you also create a simple timeline of the file&#8217;s evolution, with every major change available for inspection.  (For more complex projects, you could come up with more elaborate naming schemes, or turn to automated version control software like Version Cue.)<\/p>\n<p><strong>3.  Avoid duplicate filenames.<\/strong><br \/>\nIf you replace a file with a new file that has the same name, nobody but you may be aware that it&#8217;s been changed.  Duplicate filenames may sometimes be necessary, but there&#8217;s always some potential for confusion.  Even though you fixed a given problem with an old version, for example, someone else might be operating on the assumption that it&#8217;s still there.<\/p>\n<p><strong>4.  Don&#8217;t delete old files.<\/strong><br \/>\nSpace permitting, you should archive every version of your file.  Even after the project&#8217;s done, keeping old versions around can be a great help in case something goes wrong in the future.  You can comb back through your files in reverse order and pinpoint where the problem first occurred.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>1. Label files accurately. It&#8217;s always a good idea to give your files clear, descriptive names. But it becomes critical in collaborative projects, when your colleagues need to be able to distinguish between, say, a draft file that they can expect to change in the future, and a final file that they can expect to [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[2],"tags":[],"_links":{"self":[{"href":"https:\/\/fox-gieg.com\/tutorials\/wp-json\/wp\/v2\/posts\/84"}],"collection":[{"href":"https:\/\/fox-gieg.com\/tutorials\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fox-gieg.com\/tutorials\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fox-gieg.com\/tutorials\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/fox-gieg.com\/tutorials\/wp-json\/wp\/v2\/comments?post=84"}],"version-history":[{"count":0,"href":"https:\/\/fox-gieg.com\/tutorials\/wp-json\/wp\/v2\/posts\/84\/revisions"}],"wp:attachment":[{"href":"https:\/\/fox-gieg.com\/tutorials\/wp-json\/wp\/v2\/media?parent=84"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fox-gieg.com\/tutorials\/wp-json\/wp\/v2\/categories?post=84"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fox-gieg.com\/tutorials\/wp-json\/wp\/v2\/tags?post=84"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}