Synchronized build

Author: lektor-bot

archives/old-tech-blog/entries/bridging-public-bugtrackers-and-local-tasklists/index.html

@@ -16,13 +16,13 @@
 <meta property="og:type" content="article" />
 
 
-<meta property="og:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/bridging-public-bugtrackers-and-local-tasklists/cc_blog_ccommons_screenshot2.png" />
+<meta property="og:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/bridging-public-bugtrackers-and-local-tasklists/cc_blog_ccommons_screenshot1.png" />
 
 <meta name="twitter:card" content="summary_large_image" />
 <meta name="twitter:title" content="Orgmode and Roundup: Bridging public bugtrackers and local tasklists">
 <meta name="twitter:description" content="So maybe you&#39;re already familiar with the problem. You&#39;re collaborating with other people, and especially if you&#39;re in a free software environment (but maybe even some install at your work) you have some bugtracker, and that&#39;s where everyone collaborates. But on the other hand, you have a life, your own todo systems, your own notes, etc. Even for the tasks that are on the bugtracker, you might keep your own local copy of that task and notes on that task. Eventually things start to get out of sync. Chaos!">
 
-<meta name="twitter:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/bridging-public-bugtrackers-and-local-tasklists/cc_blog_ccommons_screenshot2.png">
+<meta name="twitter:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/bridging-public-bugtrackers-and-local-tasklists/cc_blog_ccommons_screenshot1.png">
 
 <meta name="twitter:site" content="@creativecommons">
 <meta name="twitter:creator" content="@creativecommons">

archives/old-tech-blog/entries/cc-open-office-plugin-gets-a-new-ui/index.html

@@ -16,13 +16,13 @@
 <meta property="og:type" content="article" />
 
 
-<meta property="og:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/cc-open-office-plugin-gets-a-new-ui/Screenshot.png" />
+<meta property="og:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/cc-open-office-plugin-gets-a-new-ui/Screenshot-3.png" />
 
 <meta name="twitter:card" content="summary_large_image" />
 <meta name="twitter:title" content="Creative Commons Open Office Plugin gets a new UI and supports for Public Domain">
 <meta name="twitter:description" content="User Interface">
 
-<meta name="twitter:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/cc-open-office-plugin-gets-a-new-ui/Screenshot.png">
+<meta name="twitter:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/cc-open-office-plugin-gets-a-new-ui/Screenshot-3.png">
 
 <meta name="twitter:site" content="@creativecommons">
 <meta name="twitter:creator" content="@creativecommons">

archives/old-tech-blog/entries/cc-open-office-plugin-here-it-is-with-some-new-features/index.html

@@ -16,13 +16,13 @@
 <meta property="og:type" content="article" />
 
 
-<meta property="og:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/cc-open-office-plugin-here-it-is-with-some-new-features/Draw.png" />
+<meta property="og:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/cc-open-office-plugin-here-it-is-with-some-new-features/RDF.png" />
 
 <meta name="twitter:card" content="summary_large_image" />
 <meta name="twitter:title" content="Creative Commons Open Office Plugin. Here it is with some new features....">
 <meta name="twitter:description" content="Hi there!">
 
-<meta name="twitter:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/cc-open-office-plugin-here-it-is-with-some-new-features/Draw.png">
+<meta name="twitter:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/cc-open-office-plugin-here-it-is-with-some-new-features/RDF.png">
 
 <meta name="twitter:site" content="@creativecommons">
 <meta name="twitter:creator" content="@creativecommons">

archives/old-tech-blog/entries/destination-sanity/index.html

@@ -16,13 +16,13 @@
 <meta property="og:type" content="article" />
 
 
-<meta property="og:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/destination-sanity/2347986388_dd1c466a5e.jpg" />
+<meta property="og:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/destination-sanity/2347987536_5515b1f963.jpg" />
 
 <meta name="twitter:card" content="summary_large_image" />
 <meta name="twitter:title" content="Destination: Sanity">
 <meta name="twitter:description" content="Last week Kinkade asked me for a brief overview of how the license engine, web services and other bits of code all fit together to create the joy that is creativecommons.org. &#34;Sure,&#34; I thought; &#34;that&#39;s simple!&#34;">
 
-<meta name="twitter:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/destination-sanity/2347986388_dd1c466a5e.jpg">
+<meta name="twitter:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/destination-sanity/2347987536_5515b1f963.jpg">
 
 <meta name="twitter:site" content="@creativecommons">
 <meta name="twitter:creator" content="@creativecommons">

archives/old-tech-blog/entries/find-and-reuse-with-attribution-cc-licensed-images/index.html

@@ -16,13 +16,13 @@
 <meta property="og:type" content="article" />
 
 
-<meta property="og:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/find-and-reuse-with-attribution-cc-licensed-images/Screenshot-Creative-Commons-—-Attribution-ShareAlike-2.5-Generic-Google-Chrome.png" />
+<meta property="og:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/find-and-reuse-with-attribution-cc-licensed-images/flower.jpg" />
 
 <meta name="twitter:card" content="summary_large_image" />
 <meta name="twitter:title" content="Find and Reuse Images: Painless Attribution">
 <meta name="twitter:description" content="Finding CC licensed images and using them properly is something many people seem to struggle with: finding them can be straight-forward, but many sites don&#39;t provide copy and paste reuse code that complies with the license. Xpert, a project of University of Nottingham, has launched an image search tool that helps with this. Xpert Attribution tool searches Wikimedia Commons and Flickr and provides an easy way to get the image with the attribution information overlaid, or (even better, in my opinion) with RDFa suitable for embedding. I&#39;ve combined the two below (downloading the image with attribution, and adding the structured-data enriched embed code below it).">
 
-<meta name="twitter:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/find-and-reuse-with-attribution-cc-licensed-images/Screenshot-Creative-Commons-—-Attribution-ShareAlike-2.5-Generic-Google-Chrome.png">
+<meta name="twitter:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/find-and-reuse-with-attribution-cc-licensed-images/flower.jpg">
 
 <meta name="twitter:site" content="@creativecommons">
 <meta name="twitter:creator" content="@creativecommons">

archives/old-tech-blog/entries/flickr-image-re-use-for-openofficeorg-demo-availlable/index.html

@@ -16,13 +16,13 @@
 <meta property="og:type" content="article" />
 
 
-<meta property="og:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/flickr-image-re-use-for-openofficeorg-demo-availlable/mysearchvsflickradvsearch.jpg" />
+<meta property="og:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/flickr-image-re-use-for-openofficeorg-demo-availlable/popupmenu.jpg" />
 
 <meta name="twitter:card" content="summary_large_image" />
 <meta name="twitter:title" content="Flickr Image Re-Use for OpenOffice.org Demo availlable">
 <meta name="twitter:description" content="Never trust a programmer when he gives you a date for something to be done . Thats what i did in my last article (2 weeks i think i said then) and here we are a month later.">
 
-<meta name="twitter:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/flickr-image-re-use-for-openofficeorg-demo-availlable/mysearchvsflickradvsearch.jpg">
+<meta name="twitter:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/flickr-image-re-use-for-openofficeorg-demo-availlable/popupmenu.jpg">
 
 <meta name="twitter:site" content="@creativecommons">
 <meta name="twitter:creator" content="@creativecommons">

archives/old-tech-blog/entries/flickr-image-re-use-for-openofficeorg-new-updates/index.html

@@ -16,13 +16,13 @@
 <meta property="og:type" content="article" />
 
 
-<meta property="og:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/flickr-image-re-use-for-openofficeorg-new-updates/impress.jpg" />
+<meta property="og:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/flickr-image-re-use-for-openofficeorg-new-updates/writer.jpg" />
 
 <meta name="twitter:card" content="summary_large_image" />
 <meta name="twitter:title" content="Flickr Image Re-Use for OpenOffice.org new updates">
 <meta name="twitter:description" content="Since my last article new functionalities were implemented :">
 
-<meta name="twitter:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/flickr-image-re-use-for-openofficeorg-new-updates/impress.jpg">
+<meta name="twitter:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/flickr-image-re-use-for-openofficeorg-new-updates/writer.jpg">
 
 <meta name="twitter:site" content="@creativecommons">
 <meta name="twitter:creator" content="@creativecommons">

archives/old-tech-blog/entries/flickr-image-re-use-for-openofficeorg-updates/index.html

@@ -16,13 +16,13 @@
 <meta property="og:type" content="article" />
 
 
-<meta property="og:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/flickr-image-re-use-for-openofficeorg-updates/ccflickr2.JPG" />
+<meta property="og:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/flickr-image-re-use-for-openofficeorg-updates/ccflickr1.JPG" />
 
 <meta name="twitter:card" content="summary_large_image" />
 <meta name="twitter:title" content="Flickr Image Re-Use for OpenOffice.org update">
 <meta name="twitter:description" content="I`m happy to announce that i succeeded in doing, in a basic manner, all the 3 requirements for this project : search photos by tags, by license and to insert one photo into a document.">
 
-<meta name="twitter:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/flickr-image-re-use-for-openofficeorg-updates/ccflickr2.JPG">
+<meta name="twitter:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/flickr-image-re-use-for-openofficeorg-updates/ccflickr1.JPG">
 
 <meta name="twitter:site" content="@creativecommons">
 <meta name="twitter:creator" content="@creativecommons">

archives/old-tech-blog/entries/more-ccrel-licensing-science-and-liblicense-to-the-rescue/index.html

@@ -17,14 +17,14 @@
 <meta property="og:type" content="article" />
 
 
-<meta property="og:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/more-ccrel-licensing-science-and-liblicense-to-the-rescue/2590795748_48222821e5.jpg" />
+<meta property="og:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/more-ccrel-licensing-science-and-liblicense-to-the-rescue/2589954195_bb6f509717.jpg" />
 
 <meta name="twitter:card" content="summary_large_image" />
 <meta name="twitter:title" content="More ccREL, licensing Science, and liblicense to the rescue">
 <meta name="twitter:description" content="_
 _">
 
-<meta name="twitter:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/more-ccrel-licensing-science-and-liblicense-to-the-rescue/2590795748_48222821e5.jpg">
+<meta name="twitter:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/more-ccrel-licensing-science-and-liblicense-to-the-rescue/2589954195_bb6f509717.jpg">
 
 <meta name="twitter:site" content="@creativecommons">
 <meta name="twitter:creator" content="@creativecommons">

archives/old-tech-blog/entries/stand-up-meeting-2004-04-01/index.html

@@ -16,13 +16,13 @@
 <meta property="og:type" content="article" />
 
 
-<meta property="og:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/stand-up-meeting-2004-04-01/2385228781_b6962f4526_m.jpg" />
+<meta property="og:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/stand-up-meeting-2004-04-01/2386059670_9aa013cf66_m.jpg" />
 
 <meta name="twitter:card" content="summary_large_image" />
 <meta name="twitter:title" content="Stand-up Meeting 2004-04-01">
 <meta name="twitter:description" content="The Tech Team at Creative Commons has recently replaced our weekly one-on-ones (myself with each direct report) with semi-weekly stand-up meetings for the entire team. Note that we&#39;re not really agile &#34;purists&#34; -- our meeting involve some discussion of priorities, etc, either for the week ahead, or as a recap of the week past.">
 
-<meta name="twitter:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/stand-up-meeting-2004-04-01/2385228781_b6962f4526_m.jpg">
+<meta name="twitter:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/stand-up-meeting-2004-04-01/2386059670_9aa013cf66_m.jpg">
 
 <meta name="twitter:site" content="@creativecommons">
 <meta name="twitter:creator" content="@creativecommons">

archives/old-tech-blog/entries/understanding-the-state-of-sanity-via-whiteboards-and-ascii-art/index.html

@@ -16,13 +16,13 @@
 <meta property="og:type" content="article" />
 
 
-<meta property="og:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/understanding-the-state-of-sanity-via-whiteboards-and-ascii-art/2347986388_dd1c466a5e.jpg" />
+<meta property="og:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/understanding-the-state-of-sanity-via-whiteboards-and-ascii-art/2347987536_5515b1f963.jpg" />
 
 <meta name="twitter:card" content="summary_large_image" />
 <meta name="twitter:title" content="Understanding the State of Sanity (via whiteboards and ascii art)">
 <meta name="twitter:description" content="Since I started working at Creative Commons a number of months ago, I&#39;ve been primarily focused on something we refer to as the &#34;sanity overhaul&#34;. In this case, sanity refers to try and simplify what is kind of a long and complicated code history surrounding Creative Commons&#39; licenses, both as in terms of the internal tooling to modifying, deploying, and querying licenses and the public facing web interfaces for viewing and downloading them. Efforts toward the sanity overhaul started before I began working here, executed by both Nathan Yergler and Frank Tobia, but for a long time they were in a kind of state of limbo as other technical efforts had to be dedicated to other important tasks. The good news is that my efforts have been permitted to be (almost) entirely dedicated toward the sanity overhaul since I have started, and we are reaching a point where all of those pieces are falling into place and we are very close to launch.">
 
-<meta name="twitter:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/understanding-the-state-of-sanity-via-whiteboards-and-ascii-art/2347986388_dd1c466a5e.jpg">
+<meta name="twitter:image" content="http://opensource.creativecommons.org/archives/old-tech-blog/entries/understanding-the-state-of-sanity-via-whiteboards-and-ascii-art/2347987536_5515b1f963.jpg">
 
 <meta name="twitter:site" content="@creativecommons">
 <meta name="twitter:creator" content="@creativecommons">

blog/entries/2019-07-24-cc-search-wp-plugin/index.html

@@ -16,13 +16,13 @@
 <meta property="og:type" content="article" />
 
 
-<meta property="og:image" content="http://opensource.creativecommons.org/blog/entries/2019-07-24-cc-search-wp-plugin/04.png" />
+<meta property="og:image" content="http://opensource.creativecommons.org/blog/entries/2019-07-24-cc-search-wp-plugin/01.png" />
 
 <meta name="twitter:card" content="summary_large_image" />
 <meta name="twitter:title" content="Easy search and use of CC-licensed images for WordPress">
 <meta name="twitter:description" content="Inspiration and idea for the WordPress plugin">
 
-<meta name="twitter:image" content="http://opensource.creativecommons.org/blog/entries/2019-07-24-cc-search-wp-plugin/04.png">
+<meta name="twitter:image" content="http://opensource.creativecommons.org/blog/entries/2019-07-24-cc-search-wp-plugin/01.png">
 
 <meta name="twitter:site" content="@creativecommons">
 <meta name="twitter:creator" content="@creativecommons">

blog/entries/2019-09-25-ccgn-redesign/index.html

@@ -17,14 +17,14 @@
 <meta property="og:type" content="article" />
 
 
-<meta property="og:image" content="http://opensource.creativecommons.org/blog/entries/2019-09-25-ccgn-redesign/chapters-list.png" />
+<meta property="og:image" content="http://opensource.creativecommons.org/blog/entries/2019-09-25-ccgn-redesign/user-search.png" />
 
 <meta name="twitter:card" content="summary_large_image" />
 <meta name="twitter:title" content="Revamping the Creative Commons Global Network website">
 <meta name="twitter:description" content="The CC Global Network website is the face of our global community; it is the home for a community of advocates, activists, scholars, artists, and users working to strengthen the Commons worldwide.
 One of our organizational goals regarding the global network is to “create value for members, toward impact at global scale” and that’s why we plan on redesigning the Global Network website.">
 
-<meta name="twitter:image" content="http://opensource.creativecommons.org/blog/entries/2019-09-25-ccgn-redesign/chapters-list.png">
+<meta name="twitter:image" content="http://opensource.creativecommons.org/blog/entries/2019-09-25-ccgn-redesign/user-search.png">
 
 <meta name="twitter:site" content="@creativecommons">
 <meta name="twitter:creator" content="@creativecommons">

blog/entries/automate-github-for-more-than-CI CD/index.html

@@ -16,13 +16,13 @@
 <meta property="og:type" content="article" />
 
 
-<meta property="og:image" content="http://opensource.creativecommons.org/blog/entries/automate-github-for-more-than-CI CD/release-notes-screenshot.png" />
+<meta property="og:image" content="http://opensource.creativecommons.org/blog/entries/automate-github-for-more-than-CI CD/dependabot-example.png" />
 
 <meta name="twitter:card" content="summary_large_image" />
 <meta name="twitter:title" content="Automate GitHub for more than CI/CD">
 <meta name="twitter:description" content="Get started using GitHub bots and actions for community management and repository health.">
 
-<meta name="twitter:image" content="http://opensource.creativecommons.org/blog/entries/automate-github-for-more-than-CI CD/release-notes-screenshot.png">
+<meta name="twitter:image" content="http://opensource.creativecommons.org/blog/entries/automate-github-for-more-than-CI CD/dependabot-example.png">
 
 <meta name="twitter:site" content="@creativecommons">
 <meta name="twitter:creator" content="@creativecommons">

blog/entries/building-distributed-indexer/index.html

@@ -16,13 +16,13 @@
 <meta property="og:type" content="article" />
 
 
-<meta property="og:image" content="http://opensource.creativecommons.org/blog/entries/building-distributed-indexer/one_server_indexing.png" />
+<meta property="og:image" content="http://opensource.creativecommons.org/blog/entries/building-distributed-indexer/indexing1.jpg" />
 
 <meta name="twitter:card" content="summary_large_image" />
 <meta name="twitter:title" content="Building a Distributed Indexer for a Search Engine">
 <meta name="twitter:description" content="With CC Search, we want to make it possible to search all of the estimated 1.6 billion Creative Commons works on the internet. In order to make it possible for thousands of people to search billions of records in a reasonable period of time, we have to build a big inverted index (a data structure similar to the index in the back of a textbook), which allows very fast lookups of documents related to the user’s search query. To populate this index, we have to build a large database of Creative Commons works and then replicate it to our search index, which is powered by Elasticsearch.">
 
-<meta name="twitter:image" content="http://opensource.creativecommons.org/blog/entries/building-distributed-indexer/one_server_indexing.png">
+<meta name="twitter:image" content="http://opensource.creativecommons.org/blog/entries/building-distributed-indexer/indexing1.jpg">
 
 <meta name="twitter:site" content="@creativecommons">
 <meta name="twitter:creator" content="@creativecommons">