Synchronized build

lektor-bot · lektor-bot · commit 05327d5957fe · 2020-11-25T17:28:45.000Z
diff --git a/blog/authors/krysal/index.html b/blog/authors/krysal/index.html
@@ -260,7 +260,7 @@ <h2>
   Krystle Salazar
 </h2>
           
-            <div class="about"><p>Krystle is a Software Developer from Venezuela, working on <strong>Reimplement <a href="https://github.com/creativecommons/caselaw">CC’s Legal Database</a> using Django</strong> as part of Outreachy Summer round of 2020. You can find her as <code>@krysal</code> on the CC Slack.</p>
+            <div class="about"><p>Krystle is a Software Developer from Venezuela, working on <strong>Reimplement <a href="https://github.com/creativecommons/legaldb">CC’s Legal Database</a> using Django</strong> as part of Outreachy Summer round of 2020. You can find her as <code>@krysal</code> on the CC Slack.</p>
 </div>
           
           <a class="button small" href="/blog/authors/">See all authors</a>
diff --git a/blog/entries/legal-database-a-new-beginning/index.html b/blog/entries/legal-database-a-new-beginning/index.html
@@ -299,7 +299,7 @@ <h3 id="next-steps">Next steps</h3><p>It has only been a week so we're just star
 </ul>
 <h3 id="how-you-can-help">How you can help</h3><p>We are still discussing the new image before start coding so these are some options if you want to get involved:</p>
 <ul>
-<li>Suggest improvements to designs/UX or new features joining the discussion on the <a href="https://creativecommons.slack.com/channels/cc-dev-legal-database"><code>#cc-dev-legal-database</code></a> Slack channel or on the <a href="https://github.com/creativecommons/caselaw">github</a> project.</li>
+<li>Suggest improvements to designs/UX or new features joining the discussion on the <a href="https://creativecommons.slack.com/channels/cc-dev-legal-database"><code>#cc-dev-legal-database</code></a> Slack channel or on the <a href="https://github.com/creativecommons/legaldb">github</a> project.</li>
 <li>Contribute directly to the CC's Vocabulary design system on <a href="https://github.com/creativecommons/vocabulary">github</a>.</li>
 <li>Submit a case or a scholarship related to CC licenses on the <a href="https://labs.creativecommons.org/caselaw/contribute/">current site</a>.</li>
 </ul>
diff --git a/blog/entries/legal-database-features/index.html b/blog/entries/legal-database-features/index.html
@@ -287,7 +287,7 @@ <h3 id="automated-tests">Automated tests</h3><p>While developing the mentioned f
 <figure style="text-align: center;">
     <img src="404-page.png" alt="404 page" style="border:1px solid black; width:70%;">
     <figcaption>Example of page obtained when requesting a case detail that is not published or doesn't exist.</figcaption>
-</figure><p>In this process of adding automated tests I wanted them to run on every pull request created, so I learned how to write a GitHub Action with a PostgreSQL service, the DBMS used in this case. Previously, I had already created a job for linting, so I needed to add another one to run in parallel to save time. This service provided by GitHub is pretty cool and useful, it opens up a world of possibilities, from running third party services like <a href="https://github.com/GoogleChrome/lighthouse-ci">Lighthouse test</a> to even <a href="https://github.com/gr2m/twitter-together">send tweets</a>! If you want to see the GitHub Action file configurated for this project, check it out: <a href="https://github.com/creativecommons/caselaw/blob/31c3002a7860d78f3fdb464150c5c1b2f8bb86fc/.github/workflows/main.yml"><code>.github/workflows/main.yml</code></a>.</p>
+</figure><p>In this process of adding automated tests I wanted them to run on every pull request created, so I learned how to write a GitHub Action with a PostgreSQL service, the DBMS used in this case. Previously, I had already created a job for linting, so I needed to add another one to run in parallel to save time. This service provided by GitHub is pretty cool and useful, it opens up a world of possibilities, from running third party services like <a href="https://github.com/GoogleChrome/lighthouse-ci">Lighthouse test</a> to even <a href="https://github.com/gr2m/twitter-together">send tweets</a>! If you want to see the GitHub Action file configurated for this project, check it out: <a href="https://github.com/creativecommons/legaldb/blob/31c3002a7860d78f3fdb464150c5c1b2f8bb86fc/.github/workflows/main.yml"><code>.github/workflows/main.yml</code></a>.</p>
 <h3 id="accessibility">Accessibility</h3><p>To check if the site had shortcomings I did the Lighthouse test on the homepage, discovering that there were indeed some issues to tackle. In principle the results were these:</p>
 <figure style="text-align: center;">
     <img src="lighthouse-before.png" alt="" style="border:1px solid black; width:70%;">
diff --git a/blog/feed.xml b/blog/feed.xml
@@ -1655,7 +1655,7 @@ Godey&lt;/a&gt;, have been very supportive.&lt;/p&gt;
 &lt;figure style=&quot;text-align: center;&quot;&gt;
     &lt;img src=&quot;404-page.png&quot; alt=&quot;404 page&quot; style=&quot;border:1px solid black; width:70%;&quot;&gt;
     &lt;figcaption&gt;Example of page obtained when requesting a case detail that is not published or doesn't exist.&lt;/figcaption&gt;
-&lt;/figure&gt;&lt;p&gt;In this process of adding automated tests I wanted them to run on every pull request created, so I learned how to write a GitHub Action with a PostgreSQL service, the DBMS used in this case. Previously, I had already created a job for linting, so I needed to add another one to run in parallel to save time. This service provided by GitHub is pretty cool and useful, it opens up a world of possibilities, from running third party services like &lt;a href=&quot;https://github.com/GoogleChrome/lighthouse-ci&quot;&gt;Lighthouse test&lt;/a&gt; to even &lt;a href=&quot;https://github.com/gr2m/twitter-together&quot;&gt;send tweets&lt;/a&gt;! If you want to see the GitHub Action file configurated for this project, check it out: &lt;a href=&quot;https://github.com/creativecommons/caselaw/blob/31c3002a7860d78f3fdb464150c5c1b2f8bb86fc/.github/workflows/main.yml&quot;&gt;&lt;code&gt;.github/workflows/main.yml&lt;/code&gt;&lt;/a&gt;.&lt;/p&gt;
+&lt;/figure&gt;&lt;p&gt;In this process of adding automated tests I wanted them to run on every pull request created, so I learned how to write a GitHub Action with a PostgreSQL service, the DBMS used in this case. Previously, I had already created a job for linting, so I needed to add another one to run in parallel to save time. This service provided by GitHub is pretty cool and useful, it opens up a world of possibilities, from running third party services like &lt;a href=&quot;https://github.com/GoogleChrome/lighthouse-ci&quot;&gt;Lighthouse test&lt;/a&gt; to even &lt;a href=&quot;https://github.com/gr2m/twitter-together&quot;&gt;send tweets&lt;/a&gt;! If you want to see the GitHub Action file configurated for this project, check it out: &lt;a href=&quot;https://github.com/creativecommons/legaldb/blob/31c3002a7860d78f3fdb464150c5c1b2f8bb86fc/.github/workflows/main.yml&quot;&gt;&lt;code&gt;.github/workflows/main.yml&lt;/code&gt;&lt;/a&gt;.&lt;/p&gt;
 &lt;h3 id=&quot;accessibility&quot;&gt;Accessibility&lt;/h3&gt;&lt;p&gt;To check if the site had shortcomings I did the Lighthouse test on the homepage, discovering that there were indeed some issues to tackle. In principle the results were these:&lt;/p&gt;
 &lt;figure style=&quot;text-align: center;&quot;&gt;
     &lt;img src=&quot;lighthouse-before.png&quot; alt=&quot;&quot; style=&quot;border:1px solid black; width:70%;&quot;&gt;
@@ -2726,7 +2726,7 @@ images and their metadata, for each image data in multimedia, foreign id is in &
 &lt;/ul&gt;
 &lt;h3 id=&quot;how-you-can-help&quot;&gt;How you can help&lt;/h3&gt;&lt;p&gt;We are still discussing the new image before start coding so these are some options if you want to get involved:&lt;/p&gt;
 &lt;ul&gt;
-&lt;li&gt;Suggest improvements to designs/UX or new features joining the discussion on the &lt;a href=&quot;https://creativecommons.slack.com/channels/cc-dev-legal-database&quot;&gt;&lt;code&gt;#cc-dev-legal-database&lt;/code&gt;&lt;/a&gt; Slack channel or on the &lt;a href=&quot;https://github.com/creativecommons/caselaw&quot;&gt;github&lt;/a&gt; project.&lt;/li&gt;
+&lt;li&gt;Suggest improvements to designs/UX or new features joining the discussion on the &lt;a href=&quot;https://creativecommons.slack.com/channels/cc-dev-legal-database&quot;&gt;&lt;code&gt;#cc-dev-legal-database&lt;/code&gt;&lt;/a&gt; Slack channel or on the &lt;a href=&quot;https://github.com/creativecommons/legaldb&quot;&gt;github&lt;/a&gt; project.&lt;/li&gt;
 &lt;li&gt;Contribute directly to the CC's Vocabulary design system on &lt;a href=&quot;https://github.com/creativecommons/vocabulary&quot;&gt;github&lt;/a&gt;.&lt;/li&gt;
 &lt;li&gt;Submit a case or a scholarship related to CC licenses on the &lt;a href=&quot;https://labs.creativecommons.org/caselaw/contribute/&quot;&gt;current site&lt;/a&gt;.&lt;/li&gt;
 &lt;/ul&gt;
diff --git a/community/index.html b/community/index.html
@@ -300,8 +300,8 @@ <h2 id="slack">Slack</h2><p>Creative Commons has a large Slack community with su
       <td><a href="https://github.com/creativecommons/cccatalog-dataviz">CC Catalog visualizations.</a></td>
     </tr>
     <tr>
-      <td><code>#cc-dev-legal-database</code></td>
-      <td><a href="https://labs.creativecommons.org/caselaw/">CC Legal Database.</a></td>
+      <td><code>#cc-dev-legaldb</code></td>
+      <td><a href="https://github.com/creativecommons/legaldb">CC Legal Database.</a></td>
     </tr>
     <tr>
       <td><code>#cc-dev-license-chooser</code></td>
