From 9bd97f5b5e1402f57085409a2149c36d225368ef Mon Sep 17 00:00:00 2001 From: Lektor Bot Date: Mon, 8 Apr 2024 16:14:02 +0000 Subject: [PATCH] Synchronized build --- .../old-tech-blog/authors/cwebber/index.html | 4 +- archives/old-tech-blog/entries/index.html | 2 +- .../old-tech-blog/entries/page/2/index.html | 2 +- blog/authors/dhruvi16/index.html | 4 +- blog/authors/zackkrida/index.html | 2 +- blog/categories/cc-search/index.html | 2 +- blog/categories/community/index.html | 2 +- blog/categories/open-source/index.html | 6 +- blog/categories/outreachy-2020/index.html | 4 +- blog/categories/outreachy/index.html | 4 +- blog/categories/tech/index.html | 4 +- blog/entries/page/3/index.html | 2 +- blog/entries/page/5/index.html | 2 +- blog/entries/page/6/index.html | 2 +- blog/feed.xml | 138 +++++++++--------- 15 files changed, 90 insertions(+), 90 deletions(-) diff --git a/archives/old-tech-blog/authors/cwebber/index.html b/archives/old-tech-blog/authors/cwebber/index.html index bee0c59c8..bd160d29f 100644 --- a/archives/old-tech-blog/authors/cwebber/index.html +++ b/archives/old-tech-blog/authors/cwebber/index.html @@ -303,7 +303,7 @@

cwebber on 2012-07-11
- The Liberated Pixel Cup style guide, which is the cornerstone of coordinating collaboration in... + The Liberated Pixel Cup style guide, which is the cornerstone of coordinating collaboration in...
@@ -375,7 +375,7 @@

cwebber on 2011-07-05
- _Libre Graphics Magazine 1.1 cover_ / CC BY-SA 3.0 + _Libre Graphics Magazine 1.1 cover_ / CC BY-SA 3.0
diff --git a/archives/old-tech-blog/entries/index.html b/archives/old-tech-blog/entries/index.html index 594ed18fc..d29baa48b 100644 --- a/archives/old-tech-blog/entries/index.html +++ b/archives/old-tech-blog/entries/index.html @@ -444,7 +444,7 @@

cwebber on 2012-07-11
- The Liberated Pixel Cup style guide, which is the cornerstone of coordinating collaboration in... + The Liberated Pixel Cup style guide, which is the cornerstone of coordinating collaboration in...
diff --git a/archives/old-tech-blog/entries/page/2/index.html b/archives/old-tech-blog/entries/page/2/index.html index 8f2a3a63c..70ba49bb2 100644 --- a/archives/old-tech-blog/entries/page/2/index.html +++ b/archives/old-tech-blog/entries/page/2/index.html @@ -500,7 +500,7 @@

cwebber on 2011-07-05
- _Libre Graphics Magazine 1.1 cover_ / CC BY-SA 3.0 + _Libre Graphics Magazine 1.1 cover_ / CC BY-SA 3.0
diff --git a/blog/authors/dhruvi16/index.html b/blog/authors/dhruvi16/index.html index 3641610e0..c06e924b9 100644 --- a/blog/authors/dhruvi16/index.html +++ b/blog/authors/dhruvi16/index.html @@ -353,7 +353,7 @@

Dhruvi Butti on 2020-05-22
- "Sky at night" by Rychu92 is licensed under CC BY-SA 2.0 + "Sky at night" by Rychu92 is licensed under CC BY-SA 2.0
@@ -371,7 +371,7 @@

Why by Dhruvi Butti on 2020-05-15
- why?why?why? (CC0 1.0) + why?why?why? (CC0 1.0)
diff --git a/blog/authors/zackkrida/index.html b/blog/authors/zackkrida/index.html index a47458726..a152cd953 100644 --- a/blog/authors/zackkrida/index.html +++ b/blog/authors/zackkrida/index.html @@ -282,7 +282,7 @@

Zack Krida on 2020-08-26
- Get started using GitHub bots and actions for community management and repository health. + Get started using GitHub bots and actions for community management and repository health.
diff --git a/blog/categories/cc-search/index.html b/blog/categories/cc-search/index.html index 4399517eb..ed9390a00 100644 --- a/blog/categories/cc-search/index.html +++ b/blog/categories/cc-search/index.html @@ -357,7 +357,7 @@

Zack Krida on 2020-08-26
- Get started using GitHub bots and actions for community management and repository health. + Get started using GitHub bots and actions for community management and repository health.
diff --git a/blog/categories/community/index.html b/blog/categories/community/index.html index 64f23a99b..dfce04250 100644 --- a/blog/categories/community/index.html +++ b/blog/categories/community/index.html @@ -749,7 +749,7 @@

Zack Krida on 2020-08-26
- Get started using GitHub bots and actions for community management and repository health. + Get started using GitHub bots and actions for community management and repository health.
diff --git a/blog/categories/open-source/index.html b/blog/categories/open-source/index.html index 290b7e9c6..c6d4cd432 100644 --- a/blog/categories/open-source/index.html +++ b/blog/categories/open-source/index.html @@ -777,7 +777,7 @@

Zack Krida on 2020-08-26
- Get started using GitHub bots and actions for community management and repository health. + Get started using GitHub bots and actions for community management and repository health.
@@ -1225,7 +1225,7 @@

Dhruvi Butti on 2020-05-22
- "Sky at night" by Rychu92 is licensed under CC BY-SA 2.0 + "Sky at night" by Rychu92 is licensed under CC BY-SA 2.0
@@ -1253,7 +1253,7 @@

Why by Dhruvi Butti on 2020-05-15
- why?why?why? (CC0 1.0) + why?why?why? (CC0 1.0)
diff --git a/blog/categories/outreachy-2020/index.html b/blog/categories/outreachy-2020/index.html index 87826319e..1b129f904 100644 --- a/blog/categories/outreachy-2020/index.html +++ b/blog/categories/outreachy-2020/index.html @@ -469,7 +469,7 @@

Dhruvi Butti on 2020-05-22
- "Sky at night" by Rychu92 is licensed under CC BY-SA 2.0 + "Sky at night" by Rychu92 is licensed under CC BY-SA 2.0
@@ -497,7 +497,7 @@

Why by Dhruvi Butti on 2020-05-15
- why?why?why? (CC0 1.0) + why?why?why? (CC0 1.0)
diff --git a/blog/categories/outreachy/index.html b/blog/categories/outreachy/index.html index 3907b876c..c993926f0 100644 --- a/blog/categories/outreachy/index.html +++ b/blog/categories/outreachy/index.html @@ -609,7 +609,7 @@

Dhruvi Butti on 2020-05-22
- "Sky at night" by Rychu92 is licensed under CC BY-SA 2.0 + "Sky at night" by Rychu92 is licensed under CC BY-SA 2.0
@@ -665,7 +665,7 @@

Why by Dhruvi Butti on 2020-05-15
- why?why?why? (CC0 1.0) + why?why?why? (CC0 1.0)
diff --git a/blog/categories/tech/index.html b/blog/categories/tech/index.html index 7c765e34b..9df1fdc5b 100644 --- a/blog/categories/tech/index.html +++ b/blog/categories/tech/index.html @@ -385,7 +385,7 @@

Dhruvi Butti on 2020-05-22
- "Sky at night" by Rychu92 is licensed under CC BY-SA 2.0 + "Sky at night" by Rychu92 is licensed under CC BY-SA 2.0
@@ -413,7 +413,7 @@

Why by Dhruvi Butti on 2020-05-15
- why?why?why? (CC0 1.0) + why?why?why? (CC0 1.0)
diff --git a/blog/entries/page/3/index.html b/blog/entries/page/3/index.html index 25947511a..29fe25398 100644 --- a/blog/entries/page/3/index.html +++ b/blog/entries/page/3/index.html @@ -475,7 +475,7 @@

Zack Krida on 2020-08-26
- Get started using GitHub bots and actions for community management and repository health. + Get started using GitHub bots and actions for community management and repository health.
diff --git a/blog/entries/page/5/index.html b/blog/entries/page/5/index.html index 35e4a26be..6d466427e 100644 --- a/blog/entries/page/5/index.html +++ b/blog/entries/page/5/index.html @@ -559,7 +559,7 @@

Dhruvi Butti on 2020-05-22
- "Sky at night" by Rychu92 is licensed under CC BY-SA 2.0 + "Sky at night" by Rychu92 is licensed under CC BY-SA 2.0
diff --git a/blog/entries/page/6/index.html b/blog/entries/page/6/index.html index 8db3c1661..0f74079f8 100644 --- a/blog/entries/page/6/index.html +++ b/blog/entries/page/6/index.html @@ -279,7 +279,7 @@

Why by Dhruvi Butti on 2020-05-15
- why?why?why? (CC0 1.0) + why?why?why? (CC0 1.0)
diff --git a/blog/feed.xml b/blog/feed.xml index 9ecf5635f..560a8a62f 100644 --- a/blog/feed.xml +++ b/blog/feed.xml @@ -2020,67 +2020,6 @@ Godey</a>, have been very supportive.</p> <p>The Major pull requests: <a href="https://github.com/creativecommons/ccsearch-browser-extension/pull/249">#249</a>, <a href="https://github.com/creativecommons/ccsearch-browser-extension/pull/255">#255</a>, <a href="https://github.com/creativecommons/ccsearch-browser-extension/pull/268">#268</a>, <a href="https://github.com/creativecommons/ccsearch-browser-extension/pull/270">#270</a>, <a href="https://github.com/creativecommons/ccsearch-browser-extension/pull/271">#271</a>, <a href="https://github.com/creativecommons/ccsearch-browser-extension/pull/272">#272</a>, <a href="https://github.com/creativecommons/ccsearch-browser-extension/pull/275">#275</a>, <a href="https://github.com/creativecommons/ccsearch-browser-extension/pull/276">#276</a></p> <p>Also, during this period, 5 updates of the extension were pushed to the extension stores. You can check out the <a href="https://github.com/creativecommons/ccsearch-browser-extension/releases">releases page</a>.</p> <h2 id="acknowledgements">Acknowledgements</h2><p>I would like to thank <a href="https://creativecommons.org/author/aldencreativecommons-org/">Alden</a> and <a href="https://creativecommons.org/author/kriticreativecommons-org/">Kriti</a> for their valuable guidance during this journey. Special thanks to <a href="https://github.com/panchovm">Fransisco</a>, for designing the mockups of the extension, and to the wonderful contributors of CC Vocabulary.</p> -Overview of the GSoC 2020 Project2020-08-26T00:00:00Z['charini']urn:uuid:4cdfc111-c714-33e1-b521-390d487d46da<p>This is my final blog post under the <a href="/blog/entries/overview-of-the-gsoc-2020-project/#series">GSoC 2020: CC catalog</a> series, where I will highlight and -summarize my contributions to Creative Commons (CC) as part of my GSoC project. The CC Catalog project collects and -stores CC licensed images scattered across the internet, such that they can be made accessible to the general public via -the <a href="https://ccsearch.creativecommons.org/">CC Search</a> and <a href="https://api.creativecommons.engineering/v1/">CC Catalog API</a> tools. I got the opportunity to work on different aspects of the -CC Catalog repository which ultimately enhances the user experience of the CC Search and CC Catalog API tools. My -primary contributions in the duration of GSoC, and the related pull requests (PR) are as follows.</p> -<ol> -<li><p><strong>Sub-provider retrieval</strong>: The first task I completed as part of my GSoC project was the retrieval of sub-providers -(also known as <em>source</em>) such that images could be categorised under these sources, ensuring an enhanced search -experience for the users. I completed the implementation of sub-provider retrieval for three providers; Flickr, -Europeana, and Smithsonian. If you are interested in learning how the retrieval logic works, please check my -<a href="/blog/entries/flickr-sub-provider-retrieval/">initial blog post</a> of this series. The PRs related to this task are as follows.</p> -<ul> -<li>PR #<a href="https://github.com/cc-archive/cccatalog/pull/420">420</a>: Retrieve sub-providers within Flickr</li> -<li>PR #<a href="https://github.com/cc-archive/cccatalog/pull/442">442</a>: Retrieve sub-providers within Europeana</li> -<li>PR #<a href="https://github.com/cc-archive/cccatalog/pull/455">455</a>: Retrieve sub-providers within Smithsonian</li> -<li>PR #<a href="https://github.com/cc-archive/cccatalog/pull/461">461</a>: Add new source as a sub-provider of Flickr</li> -</ul> -</li> -<li><p><strong>Alert updates to Smithsonian unit codes</strong>: For the Smithsonian provider, we rely on the field known as <em>unit code</em> -to determine the sub-provider (for Smithsonian it is often a museum) each image belongs to. However, it is possible for -the <em>unit code</em> values to change over time at the upstream, and if CC is unaware of these changes, it could hinder the -successful categorisation of Smithsonian images under unique sub-provider values. I have therefore introduced a -mechanism of alerting the CC code maintainers of potential changes to <em>unit code</em> values at the upstream. More -information is provided in my <a href="/blog/entries/smithsonian-unit-code-update/">second blog post</a> of this series. The PR related to this task -is #<a href="https://github.com/cc-archive/cccatalog/pull/465">465</a>.</p> -</li> -<li><p><strong>Improvements to the Smithsonian provider API script</strong>: Smithsonian is an important provider which aggregates images -from 19 museums. However, due to the fact that the different museums have different data models and the resultant -incompatibility of the JSON responses returned from requests to the Smithsonian API, it is difficult to know which -fields to rely on to obtain the information necessary for CC. This results in CC missing out on certain important -information. As part of my GSoC project, I improved the completeness of <em>creator</em> and <em>description</em> information, by -identifying previously unknown fields from which these details could be retrieved. Even though my improvements did not -result in the identification of a comprehensive list of fields, the completeness of data was considerably improved for -some Smithsonian museums compared to how it was before. For more context about this issue please refer to the ticket -#<a href="https://github.com/cc-archive/cccatalog/issues/397">397</a>. Apart from improving information of Smithsonian data, I was also able to identify issues with certain -Smithsonian API responses which did not contain mandatory information for some of the museums. We have informed the -Smithsonian technical team of these issues and they are highlighted in ticket #<a href="https://github.com/cc-archive/cccatalog/issues/397">397</a> as well. The PRs related -to this task are as follows.</p> -<ul> -<li>PR #<a href="https://github.com/cc-archive/cccatalog/pull/474">474</a>: Improve the creator and description information of the Smithsonian source <em>National Museum of -Natural History</em> (NMNH). This is the largest museum (source) under the Smithsonian provider.</li> -<li>PR #<a href="https://github.com/cc-archive/cccatalog/pull/476">476</a>: Improve the <em>creator</em> and <em>description</em> information of other sources coming under the Smithsonian -provider.</li> -</ul> -</li> -<li><p><strong>Expiration of outdated images</strong>: The final task I completed as part of my GSoC project was implementing a strategy -for expiring outdated images in the CC database. CC has a mechanism for keeping the images they have retrieved from -providers up-to-date, based on how old an image is. This is called the <a href="/blog/entries/date-partitioned-data-reingestion/">re-ingestion strategy</a>, -where newer images are updated more frequently compared to older images. However, this re-ingestion strategy does not -detect images which have been deleted at the upstream. Thus, it is possible that some of the images stored in the CC -database are obsolete, which could result in broken links being presented via the <a href="https://ccsearch.creativecommons.org/">CC Search</a> tool. As a -solution, I have implemented a mechanism of identifying whether images in the CC database are obsolete by looking at the -<em>updated_on</em> column value of the CC image table. Depending on the re-ingestion strategy per provider, we can know what -the oldest <em>updated_on</em> value, an image can assume. If the <em>updated_on</em> value is older than the oldest valid value, we -flag the corresponding image record as obsolete. The PR related to this task is #<a href="https://github.com/cc-archive/cccatalog/pull/483">483</a>.</p> -</li> -</ol> -<p>I will continue to take the responsibility for maintaining my code in the CC Catalog repository, and I hope to continue -contributing to the CC codebase. It has been a wonderful GSoC journey for me and special thanks goes to my supervisor -Brent for his guidance.</p> Automate GitHub for more than CI/CD2020-08-26T00:00:00Z['zackkrida']urn:uuid:1f2b4dad-de07-33ab-b1c7-394778548e55<blockquote><p><em>Get started using GitHub bots and actions for community management and repository health.</em></p> </blockquote> <p>In late 2018, in the midst of being acquired by Microsoft, GitHub <a href="https://github.blog/2018-10-16-future-of-software/">launched Github Actions</a> into public beta, allowing users to run code on the popular development platform for the first time. With a straightforward <code>YAML</code> configuration syntax and the power of Microsoft's Azure cloud, GitHub Actions quickly rose to compete with existing Continuous Integration (CI) and Continuous Deployment (CD) platforms like <strong>Circle CI</strong> and <strong>Travis CI</strong>. GitHub Actions made it easier than ever for developers to test and deploy software in the cloud, but from the beginning GitHub had bigger plans for the service.</p> @@ -2176,6 +2115,67 @@ Brent for his guidance.</p> </ul> <p>These examples are a small sample of the non-CI/CD capabilities of GitHub Actions. You can peek in the <code>.github/</code> directory of any of our open source repositories to see the actions we're using, and feel free to make an issue on any project if you have an idea for an automation of your own. As we increase the number and quality of integrations in our open source repositories, we may update this article or create follow-up posts with more examples.</p> <p>If you're interested in learning more about GitHub Actions, GitHub has a wonderful <a href="https://github.com/marketplace?type=actions">marketplace</a> of avaliable actions you can explore, and the <a href="https://docs.github.com/actions">documentation for actions</a> is avaliable in several languages.</p> +Overview of the GSoC 2020 Project2020-08-26T00:00:00Z['charini']urn:uuid:4cdfc111-c714-33e1-b521-390d487d46da<p>This is my final blog post under the <a href="/blog/entries/overview-of-the-gsoc-2020-project/#series">GSoC 2020: CC catalog</a> series, where I will highlight and +summarize my contributions to Creative Commons (CC) as part of my GSoC project. The CC Catalog project collects and +stores CC licensed images scattered across the internet, such that they can be made accessible to the general public via +the <a href="https://ccsearch.creativecommons.org/">CC Search</a> and <a href="https://api.creativecommons.engineering/v1/">CC Catalog API</a> tools. I got the opportunity to work on different aspects of the +CC Catalog repository which ultimately enhances the user experience of the CC Search and CC Catalog API tools. My +primary contributions in the duration of GSoC, and the related pull requests (PR) are as follows.</p> +<ol> +<li><p><strong>Sub-provider retrieval</strong>: The first task I completed as part of my GSoC project was the retrieval of sub-providers +(also known as <em>source</em>) such that images could be categorised under these sources, ensuring an enhanced search +experience for the users. I completed the implementation of sub-provider retrieval for three providers; Flickr, +Europeana, and Smithsonian. If you are interested in learning how the retrieval logic works, please check my +<a href="/blog/entries/flickr-sub-provider-retrieval/">initial blog post</a> of this series. The PRs related to this task are as follows.</p> +<ul> +<li>PR #<a href="https://github.com/cc-archive/cccatalog/pull/420">420</a>: Retrieve sub-providers within Flickr</li> +<li>PR #<a href="https://github.com/cc-archive/cccatalog/pull/442">442</a>: Retrieve sub-providers within Europeana</li> +<li>PR #<a href="https://github.com/cc-archive/cccatalog/pull/455">455</a>: Retrieve sub-providers within Smithsonian</li> +<li>PR #<a href="https://github.com/cc-archive/cccatalog/pull/461">461</a>: Add new source as a sub-provider of Flickr</li> +</ul> +</li> +<li><p><strong>Alert updates to Smithsonian unit codes</strong>: For the Smithsonian provider, we rely on the field known as <em>unit code</em> +to determine the sub-provider (for Smithsonian it is often a museum) each image belongs to. However, it is possible for +the <em>unit code</em> values to change over time at the upstream, and if CC is unaware of these changes, it could hinder the +successful categorisation of Smithsonian images under unique sub-provider values. I have therefore introduced a +mechanism of alerting the CC code maintainers of potential changes to <em>unit code</em> values at the upstream. More +information is provided in my <a href="/blog/entries/smithsonian-unit-code-update/">second blog post</a> of this series. The PR related to this task +is #<a href="https://github.com/cc-archive/cccatalog/pull/465">465</a>.</p> +</li> +<li><p><strong>Improvements to the Smithsonian provider API script</strong>: Smithsonian is an important provider which aggregates images +from 19 museums. However, due to the fact that the different museums have different data models and the resultant +incompatibility of the JSON responses returned from requests to the Smithsonian API, it is difficult to know which +fields to rely on to obtain the information necessary for CC. This results in CC missing out on certain important +information. As part of my GSoC project, I improved the completeness of <em>creator</em> and <em>description</em> information, by +identifying previously unknown fields from which these details could be retrieved. Even though my improvements did not +result in the identification of a comprehensive list of fields, the completeness of data was considerably improved for +some Smithsonian museums compared to how it was before. For more context about this issue please refer to the ticket +#<a href="https://github.com/cc-archive/cccatalog/issues/397">397</a>. Apart from improving information of Smithsonian data, I was also able to identify issues with certain +Smithsonian API responses which did not contain mandatory information for some of the museums. We have informed the +Smithsonian technical team of these issues and they are highlighted in ticket #<a href="https://github.com/cc-archive/cccatalog/issues/397">397</a> as well. The PRs related +to this task are as follows.</p> +<ul> +<li>PR #<a href="https://github.com/cc-archive/cccatalog/pull/474">474</a>: Improve the creator and description information of the Smithsonian source <em>National Museum of +Natural History</em> (NMNH). This is the largest museum (source) under the Smithsonian provider.</li> +<li>PR #<a href="https://github.com/cc-archive/cccatalog/pull/476">476</a>: Improve the <em>creator</em> and <em>description</em> information of other sources coming under the Smithsonian +provider.</li> +</ul> +</li> +<li><p><strong>Expiration of outdated images</strong>: The final task I completed as part of my GSoC project was implementing a strategy +for expiring outdated images in the CC database. CC has a mechanism for keeping the images they have retrieved from +providers up-to-date, based on how old an image is. This is called the <a href="/blog/entries/date-partitioned-data-reingestion/">re-ingestion strategy</a>, +where newer images are updated more frequently compared to older images. However, this re-ingestion strategy does not +detect images which have been deleted at the upstream. Thus, it is possible that some of the images stored in the CC +database are obsolete, which could result in broken links being presented via the <a href="https://ccsearch.creativecommons.org/">CC Search</a> tool. As a +solution, I have implemented a mechanism of identifying whether images in the CC database are obsolete by looking at the +<em>updated_on</em> column value of the CC image table. Depending on the re-ingestion strategy per provider, we can know what +the oldest <em>updated_on</em> value, an image can assume. If the <em>updated_on</em> value is older than the oldest valid value, we +flag the corresponding image record as obsolete. The PR related to this task is #<a href="https://github.com/cc-archive/cccatalog/pull/483">483</a>.</p> +</li> +</ol> +<p>I will continue to take the responsibility for maintaining my code in the CC Catalog repository, and I hope to continue +contributing to the CC codebase. It has been a wonderful GSoC journey for me and special thanks goes to my supervisor +Brent for his guidance.</p> CC Catalog: wrapping up GSoC202020-08-25T00:00:00Z['srinidhi']urn:uuid:ba947438-0d00-32ec-8ba7-acf6f5f15eb5<p>With the summer of code coming to an end, this blog post summarises the work done during the last three months. The project I have been working on is to add more provider API scripts to the CC Catalog. The CC Catalog project is responsible for collecting CC licensed images hosted across the web.</p> <p>The internship journey has been great , and I was glad to get the opportunity to understand more about the working of the data pipeline. My work during the internship mainly involved researching new API providers and checking if they meet the necessary conditions, then we decided on a strategy to crawl the API. The strategy varies according to different APIs: some can be partitioned based on date, others have to be paginated . Script is written for the API according to the strategy. During the later phase of the internship, I had worked on the reingestion strategy for europeana and a script to merge Common Crawl tags and metadata to the corresponding image in the image table.</p> @@ -3217,14 +3217,6 @@ options = { <p>The progress of the project can be tracked on <a href="https://github.com/cc-archive/cccatalog-frontend">cc-search</a></p> <p>CC Search Accessiblity is my GSoC 2020 project under the guidance of <a href="https://creativecommons.org/author/zackcreativecommons-org/">Zack Krida</a> and <a href="/blog/authors/akmadian/">Ari Madian</a>, who is the primary mentor for this project, <a href="https://creativecommons.org/author/annacreativecommons-org/">Anna Tumadóttir</a> for helping all along and engineering director <a href="https://creativecommons.org/author/kriticreativecommons-org/">Kriti Godey</a>, have been very supportive.</p> -Integration of Vocabulary with CCOS.2020-07-08T00:00:00Z['dhruvi16']urn:uuid:220be94d-1b9f-3d0a-8f65-fe0449aa3848<p>This blog demonstrates the project I am working on during the course of my Outreachy internship. My project involves redesigning and reimplementing one of the web products of the CC network using our new cohesive design library — <a href="https://cc-vocabulary.netlify.app/?path=/docs/vocabulary-introduction--page">Vocabulary</a>. After my internship is completed, the <a href="/">Creative Commons Open Source</a> website will have a complete revamped interface that will extensively use Vocabulary components.</p> -<h2 id="the-problem">The Problem -</h2><p>There exists a large variety of web products across the Creative Commons network. These products serve different purposes for the network and so do they vary in the way of presenting the existing content. So, to conquer the inconsistency across the different products we have our coherent design system called Vocabulary.</p> -<p>If we come to the current CC Open Source website, it is quite off-track considering our new design system Vocabulary. The styles and components of the website are not well aligned with the components of the Vocabulary. And thus it lacks harmony and consistency concerning the brand.</p> -<p>The purpose of a design system gets dissolved if it is not well incorporated with the products and we do have this problem with the CC Open Source website. Hence, there was a need for a redesign of CCOS as per the new Design Library. This project aims to rectify the problems and inconsistencies of the CCOS website and build a completely new website (as per Vocabulary).</p> -<h2 id="the-solution">The Solution -</h2><p>I started with trying out different mock-ups for the new website in Figma. You can see what I tried to make <a href="https://www.figma.com/file/ka3zs1iYnqJvyLnvAV3cW7/Home-proposals">here</a>. And then with the help of our UX designer Francisco, we created all the mock-ups and finalized how the website will look in a couple of weeks, here is the <a href="https://www.figma.com/file/mttcugI1UxvCJRKE5sdpbO/Mockups?node-id=759%3A516">link</a> for that.</p> -<p>I started my internship with going through the website’s tech stack, the website is made using <a href="https://www.getlektor.com/">Lektor</a>, with which I was not very familiar. I read the official docs, went through projects, tried making demo projects, and took help from mentors wherever I got stuck.</p> -<p>To keep the project clean I added a theme that only has templates for the project and alters no content (as per aim). While updating templates, some components were not available in the Vocabulary yet, so I worked on adding those components to the library. And then used them in my new templates.</p> -<p>I have thoroughly enjoyed contributing to this project as I got to learn so much. And I am excited for what’s next to come in the upcoming weeks.</p> CC Legal Database: Coding and Mid-term status2020-07-08T00:00:00Z['krysal']urn:uuid:0283bfb3-3e0e-3c6a-a70b-02df13f31235<p>We are already in the second half of the time stipulated for the project and it is time to pause for review the initial plan, celebrate the objectives achieved and think about what remains to be done.</p> <h2 id="initial-plan">Initial plan</h2><p>Initially, two weeks were allocated to do the redesign for the new site. I thought there would be plenty of time here, <em>is just design</em> I said to myself, despite not having done any serious project in Figma before beyond a few sketches. Later we will see I was wrong here. This included creating new Vocabulary components if necessary. Between the second and third weeks, I would create the data models (for Django and therefore for the database as well) and from the fourth week onwards it would start to implement all this in code: make the Homepage, listing, details pages and the others.</p> <h2 id="issues-in-the-way">Issues in the way</h2><p>One task that took longer than expected was to finish the designs, a key point because the other tasks depended on this. Though the initial scheme was ready on time, as it was discussed with the stakeholders new requirements became evident, so more modifications had to be made. For example, on the <a href="https://labs.creativecommons.org/caselaw/">current site</a>, the way to explore cases and scholarship is by country, and in principle, this would stay the same way and I designed with that in mind, but talking to our internal user (which acts as a <em>product owner</em> here) was better to change this scheme to one for labels or categories that are more related with both entities. Highlighting the case of the Scholarship model, in which the attribute of the country was eliminated because it is not so relevant, and although it seemed somewhat a small thing, this also caused changes in the design of the home page, the listings and how the content of the database will be explored in general. Design for a good user experience is not so easy as a non-designer may think. There were times when there was a lack of ideas but the important thing is to make decisions and move forward, in later iterations it will be improved.</p> @@ -3240,4 +3232,12 @@ Godey</a>, have been very supportive.</p> <h2 id="plan-for-the-second-half-of-the-timeline">Plan for the second half of the timeline</h2><p>There are some tasks due from past weeks, such as build forms for Case and Scholarship submissions, but I am confident that now that the project has reached a stable state I can do it quickly in the next days. Other tasks were moved for later: searching records and filtering by tags moved after forms are created, so I can finish the visual parts of the site first and focus on functional work without shifting between types of tasks.</p> <p>The tasks and they order have changed, like I mentioned earlier, requirements were modified (a bit) so some tasks I planned for last weeks are not necessary anymore or are done already out-of-box with Django admin (benefits of choosing a batteries included framework!). In general, I don't think the initial plan was wrong, we just went through the natural evolution of a product software. Mentors have also been very helpful in keeping a reasonable scope and adjusting priorities.</p> <p>After main functionalities are done we can start making improvements, as we already identified some nice to have features but not so important at the moment. Stay tuned for more to come.</p> +Integration of Vocabulary with CCOS.2020-07-08T00:00:00Z['dhruvi16']urn:uuid:220be94d-1b9f-3d0a-8f65-fe0449aa3848<p>This blog demonstrates the project I am working on during the course of my Outreachy internship. My project involves redesigning and reimplementing one of the web products of the CC network using our new cohesive design library — <a href="https://cc-vocabulary.netlify.app/?path=/docs/vocabulary-introduction--page">Vocabulary</a>. After my internship is completed, the <a href="/">Creative Commons Open Source</a> website will have a complete revamped interface that will extensively use Vocabulary components.</p> +<h2 id="the-problem">The Problem -</h2><p>There exists a large variety of web products across the Creative Commons network. These products serve different purposes for the network and so do they vary in the way of presenting the existing content. So, to conquer the inconsistency across the different products we have our coherent design system called Vocabulary.</p> +<p>If we come to the current CC Open Source website, it is quite off-track considering our new design system Vocabulary. The styles and components of the website are not well aligned with the components of the Vocabulary. And thus it lacks harmony and consistency concerning the brand.</p> +<p>The purpose of a design system gets dissolved if it is not well incorporated with the products and we do have this problem with the CC Open Source website. Hence, there was a need for a redesign of CCOS as per the new Design Library. This project aims to rectify the problems and inconsistencies of the CCOS website and build a completely new website (as per Vocabulary).</p> +<h2 id="the-solution">The Solution -</h2><p>I started with trying out different mock-ups for the new website in Figma. You can see what I tried to make <a href="https://www.figma.com/file/ka3zs1iYnqJvyLnvAV3cW7/Home-proposals">here</a>. And then with the help of our UX designer Francisco, we created all the mock-ups and finalized how the website will look in a couple of weeks, here is the <a href="https://www.figma.com/file/mttcugI1UxvCJRKE5sdpbO/Mockups?node-id=759%3A516">link</a> for that.</p> +<p>I started my internship with going through the website’s tech stack, the website is made using <a href="https://www.getlektor.com/">Lektor</a>, with which I was not very familiar. I read the official docs, went through projects, tried making demo projects, and took help from mentors wherever I got stuck.</p> +<p>To keep the project clean I added a theme that only has templates for the project and alters no content (as per aim). While updating templates, some components were not available in the Vocabulary yet, so I worked on adding those components to the library. And then used them in my new templates.</p> +<p>I have thoroughly enjoyed contributing to this project as I got to learn so much. And I am excited for what’s next to come in the upcoming weeks.</p> \ No newline at end of file