Merge remote-tracking branch 'upstream/master'

Author: soccerdroid

content/blog/entries/cc-browser-extension-week9-10/contents.lr

@@ -0,0 +1,39 @@
+title: CC Browser Extension Week 9, 10
+---
+categories:
+gsoc
+gsoc-2019
+cc-browser-extension
+open-source
+---
+author: makkoncept
+---
+pub_date: 2019-08-12
+---
+body:
+
+For the context, I am working on my GSoC project that is to make a browser-extension to search CC Licensed content in the public domain by interacting with CC Catalog API.
+
+**Previous Blogs**:
+-  [CC Browser Extension - A GSoC Project](https://opensource.creativecommons.org/blog/entries/cc-browser-extension-a-gsoc-project/)
+-  [CC Browser Extension Week 5, 6](https://opensource.creativecommons.org/blog/entries/cc-browser-extension-week5-6/)
+-  [CC Browser Extension Week 7, 8](https://opensource.creativecommons.org/blog/entries/cc-browser-extension-week7-8/)
+
+### Work Done
+These weeks were spent on adding bookmarking feature to the extension and writing some unit tests.
+
+On clicking the bookmark icon, that appears when the image thumbnail is hovered on, the image will be bookmarked. Under the hood, the unique image identifier is saved in the local storage of the extension. The images ids are enough to get all the required image and attribution data needed using the `/image/{identifier}` endpoint of [CC Catalog API]([https://github.com/creativecommons/cccatalog-api](https://github.com/creativecommons/cccatalog-api).
+
+Bookmarked images persist even when the extension session terminates. User can view, inspect, delete the bookmarked images in the _'Bookmarks'_ section. There is also a button to delete all the bookmarks at once. 
+
+To let the users organize and share bookmarks, importing and exporting feature is also added. The buttons to export and import the bookmarks are in the options page. Simple `json` files are used for this feature.
+
+The rest of the time was spent on writing tests for the extension. One positive side-effect of this was cleaner and modular code. Finally, the CircleCi config file was modified to let the tests to run in CI pipeline.
+### Coming Up
+- Write more tests.
+- Test and fix bugs.
+- Modifying webpack config to spit out code for production.
+
+You can check out the project on [Github](https://github.com/creativecommons/ccsearch-browser-extension) and join the discussion on `#gsoc-browser-ext` channel on [slack](https://opensource.creativecommons.org/community/#slack).
+
+*Special Thanks*:  [Alden](https://creativecommons.org/author/aldencreativecommons-org/), [Timid](https://creativecommons.org/author/timidcreativecommons-org/) and [Kriti](https://creativecommons.org/author/kriticreativecommons-org/).

content/blog/entries/cc-chooser-lastweek/contents.lr

@@ -0,0 +1,26 @@
+ title: GSoC cc-chooser Final Post
+---
+ categories:
+ gsoc
+ gsoc-2019
+---
+ author: akmadian
+---
+ pub_date: 2019-08-22
+---
+ body:
+ Summer of Code is drawing to a close, and so is my work on the chooser project (well, sort of, I'll continue to help build and support the project for some time). These have easily been some of the best months of my life for a number of reasons. I remember vividly getting my first Slack message from my mentor, Breno, and being in utter disbelief that I was chosen. I have been fortunate enough to have this project be my own, complete with a whole Git repo just for this project!
+
+ My work started with an empty GitHub repository, and bunch of planning: layout, wireframes, usability testing, etc. It wasn't until week 3 when I could start on actually building the site. To reflect on this time, I thought it would be cool to take a look back at the most significant PRs of the last three months.
+ 
+  - My first PR with anything of substance was [#9 - Refactor Modal System](https://github.com/creativecommons/cc-chooser/pull/9). This changed the site's modal system from using a cooler approach to one not quite as flashy, but the old method was lacking some critical features.
+  - Then came [#10 - Add Chooser Functionality](https://github.com/creativecommons/cc-chooser/pull/10). This was a pretty big deal, as this brought the functionality behind the main point of the page: the License Chooser.
+  - Next up, [#11](https://github.com/creativecommons/cc-chooser/pull/11): a big change to page layout. This changed the layout of the help section itself, and the layout of the page as a whole.
+  - Another big design change: [#14](https://github.com/creativecommons/cc-chooser/pull/14). This PR changed the method of displaying the chosen license from the legacy look that was essentially just copied over from the legacy chooser, to a newer, more modern, and more informative card.
+  - Then, [#23 - Add HTML Generator Functionality](https://github.com/creativecommons/cc-chooser/pull/23). This added functionality to the HTML Generator, previously just a collection of dummy controls and fields.
+  - Currently still open, [#18](https://github.com/creativecommons/cc-chooser/pull/18). This PR changes the look and functionality of the chooser controls. Previously they were just some standard switches. Now, they are (in my opinion) more modern, and more informative, although maybe more difficult for the average user to grasp.
+  - Lastly, and most recently, [#24 - Refactor Site to Vue Components](https://github.com/creativecommons/cc-chooser/pull/24). This is a complete rewrite of the entire site to shift from a standard HTML5/ CSS/ JS toolset to Vue.js.
+
+  For all of these merged PRs, there is still work to be done: more usability testing, ensuring that all content on the page meets the proper legal requirments, localization, adding CSS for mobile and tablet breakpoints, and deployment!
+
+  I plan to have #24 done and merged by Monday, August 26, and I hope to continue my work on the chooser project either in my free time, or by moving into a mentor type role.

content/blog/entries/cc-wp-plugin-final-phase/cc-block.png

@@ -0,0 +1,81 @@
+title: Creative Commons WordPress Plugin Final Phase
+---
+categories:
+cc-wp-plugin
+gsoc-2019
+gsoc
+open-source
+wordpress
+---
+author: ahmadbilaldev
+---
+pub_date: 2019-08-23
+---
+body:
+
+For the context, I am working with my mentor [Timid Robot](https://creativecommons.org/author/timidcreativecommons-org/) on Creative Commons WordPress Plugin in GSoC 2019. It is basically an attribution tool, allowing users to attribute their content and include a CC license on their WordPress website.
+
+GSoC is about to end, and I am excited that we have the plugin ready with all the possible attribution features.
+ We had a stable version of the plugin up and running in the last phase. This allowed us to use it and
+look for possible improvements and increments. We managed to get a handful of suggestions and feedback
+from some users, which turned out quite applicable. First, let's take a quick look at the releases in
+this phase and their changelogs.
+
+### Releases
+
+#### v2019.7.2
+
+- Bug fixes.
+- New license selection settings.
+- Old license chooser removed and plugin linked to the [current chooser](https://creativecommons.org/choose/)
+- Plugin settings page redesigned for better user experience.
+- New feature to add additional text after the license.
+- Gutenberg blocks for CC licenses redesigned.
+- Added customization settings for Gutenberg blocks for backend and front end.
+
+#### v2019.8.1
+
+- Re-wrote license widget for the plugin. Added option to display the default license
+ as a widget or in the footer.
+- Refactored and improved code quality.
+- Submitted plugin to WordPress.org for review.
+
+#### v2019.8.2
+
+- All necessary Default/Site license settings added.
+- Plugin settings page design completed.
+- Rich-text components added to previously static Gutenberg blocks converted to allow attribution of any content.
+- Gutenberg blocks redesigned to include settings.
+- Security improvements.
+- i18n improvements.
+- Minor bug fixes and refinements.
+
+### Blocks
+
+The CC blocks are now editable with a bunch of options. We integrated rich-text in each block, which
+ renders a rich content-editable input, providing users with the option to format the content.
+ This makes sure that the requirements of describing the title, author and the source
+ while using a CC licensed content can be met..
+
+![CC License Block](cc-block.png)
+
+### Re-designed Settings
+
+The redesigned plugin settings are straightforward and have every required field. We have added widget as a display
+option, which is much better than previous footer implementation.
+
+![Plugin Settings](settings-1.png)
+
+*Selecting a license is simple and quick with a link to the chooser*
+
+![Plugin Settings](settings-2.png)
+
+### What's next
+
+- Implement GitHub Actions or similar for automated deployment on release from GitHub to WordPress SVN directory.
+- Integrate WPGulp workflow and improve i18n.
+- Improve documentation with a visual walk-around of every feature.
+
+Thank you for reading. For more, see the [GitHub repository](https://github.com/creativecommons/wp-plugin-creativecommons).
+
+If you have any feedback or suggestions, let us know in the discussion on `#cc-dev-wordpress` Slack channel. Looking forward!