Merge branch 'master' into update-python-deps

Author: TimidRobot

.github/workflows/lektor-build-deploy.yml

@@ -0,0 +1,20 @@
+name: Build and Deploy CC Open Source
+on: [push, pull_request]
+jobs:
+ build-and-deploy:
+  runs-on: ubuntu-latest
+  steps:
+   - uses: actions/checkout@v1
+   - name: setup python version
+     uses: actions/setup-python@v1
+     with:
+      python-version: 3.7
+   - name: Install dependencies
+     run: |
+      pip install pipenv
+      pipenv install
+      pipenv run lektor build -f webpack
+   - name: Deploy to production
+     if: github.ref == 'refs/heads/master'
+     run: |
+      pipenv run lektor deploy ghpages --username ${{ secrets.LEKTOR_DEPLOY_USERNAME }} --password ${{ secrets.LEKTOR_DEPLOY_PASSWORD }}

.lektorproject

@@ -12,3 +12,5 @@ lektor-google-analytics = 0.1.3
 lektor-webpack-support = 0.5
 lektor-atom = 0.3
 lektor-disqus-comments = 0.4.1
+lektor-strip-html-tags = 0.3.1
+lektor-markdown-excerpt = 0.1

README.md

@@ -93,6 +93,12 @@ Here's how the code is structured in the top level of the repository:
 - `/cc-vocabulary/` to https://cc-vocabulary.netlify.com/
   - Added so that the `opensource.creativecommons.org/cc-vocabulary/` will
     continue to work with that project moving to utilize Netlify.
+- `/cc-vue-vocabulary` to https://cc-vue-vocabulary.netlify.com/
+  - Added so that the `opensource.creativecommons.org/cc-vue-vocabulary/` will
+    continue to work with that project moving to utilize Netlify.
+- `/cc-fonts` to https://cc-fonts.netlify.com/
+  - Added so that the `opensource.creativecommons.org/cc-fonts/` will
+    continue to work with that project moving to utilize Netlify.
 
 
 ## License

content/404.html/contents.lr

@@ -0,0 +1,4 @@
+_model: page
+---
+_template: 404.html
+---

content/archives/old-tech-blog/entries/banshee-now-with-creative-commons-support-devel/contents.lr

@@ -8,7 +8,7 @@ body:
 
 Great news from [Gabriel Burt](http://gburt.blogspot.com/), lead developer for the Open Source media player [Banshee](http://banshee-project.org/):
 
-[![](banshee-cc.png)](http://labs.creativecommons.org/files/2009/01/banshee-cc.png)  
+[![](banshee-cc.png)](banshee-cc.png)
 (click for larger version) 
 
 **Search based on the license of a song/album with direct support of displaying CC license logos!**

content/archives/old-tech-blog/entries/bridging-public-bugtrackers-and-local-tasklists/contents.lr

@@ -32,15 +32,15 @@ Anyway, enough talk, let's give it a spin. You'll need a recent version org-mode
 
 Next open up the relevant org-mode file. Move to the "Roundup" line, hit Tab to cycle its visibility, and move to the line that starts with "#+call:"
 
-[![](cc_blog_ccommons_screenshot1.png)](http://labs.creativecommons.org/files/2010/11/cc_blog_ccommons_screenshot1.png)
+[![](cc_blog_ccommons_screenshot1.png)](cc_blog_ccommons_screenshot1.png)
 
 Now press "Ctrl+c Ctrl+c". You'll see it populate with issues from [my issues list](http://code.creativecommons.org/issues/issue?status=-1,1,2,3,4,5,6,7&@sort=-activity&@search_text=&@dispname=Your%20Issues&@filter=status,assignedto&@group=priority&@columns=id,activity,title,creator,status&assignedto=40&@pagesize=50&@startwith=0):
 
-[![](cc_blog_ccommons_screenshot2.png)](http://labs.creativecommons.org/files/2010/11/cc_blog_ccommons_screenshot2.png)
+[![](cc_blog_ccommons_screenshot2.png)](cc_blog_ccommons_screenshot2.png)
 
 What's happening here? So we're executing an org-babel block at point. [Org-babel](http://orgmode.org/worg/org-contrib/babel/intro.php) is an org-mode extension that allows you to make blocks of code executable, and even chain from one language to another (it also has some stuff relevant to Donald Knuth's "literate programming" which is cool but I'm not using here). If we look at the code blocks:
 
-[![](cc_blog_ccommons_screenshot3.png)](http://labs.creativecommons.org/files/2010/11/cc_blog_ccommons_screenshot3.png)
+[![](cc_blog_ccommons_screenshot3.png)](cc_blog_ccommons_screenshot3.png)
 
 Anyway, there are three code blocks here.
 

content/archives/old-tech-blog/entries/cc-legaleratta-errata-annotations-without-republishing-licenses/contents.lr

@@ -6,7 +6,7 @@ author: lunpa
 ---
 body:
 
-[![Screenshot of the errata tool.](errata_highlighted1.png)](http://labs.creativecommons.org/files/2012/02/errata_highlighted1.png)
+[![Screenshot of the errata tool.](errata_highlighted1.png)](errata_highlighted1.png)
 
 The html for the legalcode pages cannot be changed once they are published. The reason for this is because we provide sha1 hashes of them so that they may be redistributed. It also is a reason of credibility; that the license you've applied to your work today will still be the same one tomorrow. However, sometimes there are errors. They need to be accessible, yet they usually are too small to merit releasing a new version of the license.
 

content/archives/old-tech-blog/entries/find-and-reuse-with-attribution-cc-licensed-images/contents.lr

@@ -17,7 +17,7 @@ Nino Barbieri [CC BY-SA 2.5](http://creativecommons.org/licenses/by-sa/2.5/)
 
 The inclusion of structured data with the HTML means you can click the license link above and the license deed will display the attribution information, as well as our generated attribution HTML.
 
-[![](Screenshot-Creative-Commons-—-Attribution-ShareAlike-2.5-Generic-Google-Chrome.png)](http://labs.creativecommons.org/files/2010/10/Screenshot-Creative-Commons-—-Attribution-ShareAlike-2.5-Generic-Google-Chrome.png)
+[![](Screenshot-Creative-Commons-—-Attribution-ShareAlike-2.5-Generic-Google-Chrome.png)](Screenshot-Creative-Commons-—-Attribution-ShareAlike-2.5-Generic-Google-Chrome.png)
 
 ---
 pub_date: 2010-10-04

content/archives/old-tech-blog/entries/flickr-image-re-use-for-openofficeorg-demo-availlable/contents.lr

@@ -30,11 +30,11 @@ What has be done since my last article :
 
 Some screenshots :
 
-[The results from a search by the extension vs Flickr search](http://labs.creativecommons.org/files/2008/07/mysearchvsflickradvsearch.jpg)
+[The results from a search by the extension vs Flickr search](mysearchvsflickradvsearch.jpg)
 
-[Right click on an image](http://labs.creativecommons.org/files/2008/07/popupmenu.jpg)
+[Right click on an image](popupmenu.jpg)
 
-[Inserted image into Writer](http://labs.creativecommons.org/files/2008/07/insertedimageinwriter.jpg)
+[Inserted image into Writer](insertedimageinwriter.jpg)
 
 Also i would to add that this extension, at this momment, works only in Writer.