You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: blog/entries/outreachy-midpoint-progess-with-creative-commons/index.html
+17-17
Original file line number
Diff line number
Diff line change
@@ -282,26 +282,26 @@ <h1 id="outreachy-midpoint-blog-post">Outreachy Midpoint Blog Post</h1><p>Hi the
282
282
<h2id="project-overview">Project Overview</h2><p>The goal of my project is to implement the Vocabulary design system across several Creative Commons ancillary websites like the <ahref="https://opensource.creativecommons.org/">CC Open Source</a>, <ahref="https://legaldb.creativecommons.org/en/">CC Legal Database</a>, <ahref="https://search.creativecommons.org/">CC Search Portal</a>, and <ahref="https://resources.creativecommons.org/">CC Resource Archive</a>.</p>
283
283
<h2id="progress-so-far">Progress So Far</h2><h3id="phase-one-refactoring-markup-to-align-with-vocabulary">Phase One: Refactoring Markup to Align with Vocabulary</h3><p>In the first phase, I focused on refactoring the markup to align with Vocabulary’s components and context. Here are the pull requests (PRs) merged during this phase:</p>
284
284
<ul>
285
-
<li><ahref="https://github.com/creativecommons/creativecommons.github.io-source/pull/118">PR 118</a>: Refactored the recent blog post section on the homepage.</li>
286
-
<li><ahref="https://github.com/creativecommons/creativecommons.github.io-source/pull/856">PR 856</a>: Refactored the homepage markup to align with Vocabulary components.</li>
287
-
<li><ahref="https://github.com/creativecommons/creativecommons.github.io-source/pull/862">PR 862</a>: Updated <code>page-with-toc.html</code>, which serves as a template for many pages.</li>
288
-
<li><ahref="https://github.com/creativecommons/creativecommons.github.io-source/pull/863">PR 863</a>: Initially, I planned to refactor the markup to Vocabulary’s context, but after feedback from my mentor, I instead removed legacy class names while retaining the table structure.</li>
289
-
<li><ahref="https://github.com/creativecommons/creativecommons.github.io-source/pull/865">PR 865</a>: Refactored the blog’s author page to match Vocabulary’s “person” context.</li>
290
-
<li><ahref="https://github.com/creativecommons/creativecommons.github.io-source/pull/866">PR 866</a>: Updated the blog structure to follow Vocabulary markup.</li>
291
-
<li><ahref="https://github.com/creativecommons/creativecommons.github.io-source/pull/867">PR 867</a>: Refactored the Project List page, leaving the table markup intact but removing old styles.</li>
292
-
<li><ahref="https://github.com/creativecommons/creativecommons.github.io-source/pull/868">PR 868</a>: Refactored the Issue Finder tool, replacing Vue.js with plain JavaScript. Although removing Webpack will happen later, this PR set the stage for future improvements.</li>
293
-
<li><ahref="https://github.com/creativecommons/creativecommons.github.io-source/pull/870">PR 870</a>: Aligned the Authors page with Vocabulary’s team styling.</li>
294
-
<li><ahref="https://github.com/creativecommons/creativecommons.github.io-source/pull/871">PR 871</a>: Refactored the Project Ideas page, incorporating Vocabulary’s project markup and removing legacy styles.</li>
295
-
<li><ahref="https://github.com/creativecommons/creativecommons.github.io-source/pull/873">PR 873</a>: Dynamically updated the body tag’s class in <code>layout.html</code> and added a body-class field to the <code>blog.ini</code> model file for consistent styling.</li>
296
-
<li><ahref="https://github.com/creativecommons/creativecommons.github.io-source/pull/880">PR 880</a>: Refactored <code>page-with-title.html</code> (used by CC Tech Archives) to align with Vocabulary.</li>
297
-
<li><ahref="https://github.com/creativecommons/creativecommons.github.io-source/pull/886">PR 886</a>: Updated the header component markup and removed old class names.</li>
285
+
<li><ahref="https://github.com/creativecommons/ccos-website-source/pull/118">PR 118</a>: Refactored the recent blog post section on the homepage.</li>
286
+
<li><ahref="https://github.com/creativecommons/ccos-website-source/pull/856">PR 856</a>: Refactored the homepage markup to align with Vocabulary components.</li>
287
+
<li><ahref="https://github.com/creativecommons/ccos-website-source/pull/862">PR 862</a>: Updated <code>page-with-toc.html</code>, which serves as a template for many pages.</li>
288
+
<li><ahref="https://github.com/creativecommons/ccos-website-source/pull/863">PR 863</a>: Initially, I planned to refactor the markup to Vocabulary’s context, but after feedback from my mentor, I instead removed legacy class names while retaining the table structure.</li>
289
+
<li><ahref="https://github.com/creativecommons/ccos-website-source/pull/865">PR 865</a>: Refactored the blog’s author page to match Vocabulary’s “person” context.</li>
290
+
<li><ahref="https://github.com/creativecommons/ccos-website-source/pull/866">PR 866</a>: Updated the blog structure to follow Vocabulary markup.</li>
291
+
<li><ahref="https://github.com/creativecommons/ccos-website-source/pull/867">PR 867</a>: Refactored the Project List page, leaving the table markup intact but removing old styles.</li>
292
+
<li><ahref="https://github.com/creativecommons/ccos-website-source/pull/868">PR 868</a>: Refactored the Issue Finder tool, replacing Vue.js with plain JavaScript. Although removing Webpack will happen later, this PR set the stage for future improvements.</li>
293
+
<li><ahref="https://github.com/creativecommons/ccos-website-source/pull/870">PR 870</a>: Aligned the Authors page with Vocabulary’s team styling.</li>
294
+
<li><ahref="https://github.com/creativecommons/ccos-website-source/pull/871">PR 871</a>: Refactored the Project Ideas page, incorporating Vocabulary’s project markup and removing legacy styles.</li>
295
+
<li><ahref="https://github.com/creativecommons/ccos-website-source/pull/873">PR 873</a>: Dynamically updated the body tag’s class in <code>layout.html</code> and added a body-class field to the <code>blog.ini</code> model file for consistent styling.</li>
296
+
<li><ahref="https://github.com/creativecommons/ccos-website-source/pull/880">PR 880</a>: Refactored <code>page-with-title.html</code> (used by CC Tech Archives) to align with Vocabulary.</li>
297
+
<li><ahref="https://github.com/creativecommons/ccos-website-source/pull/886">PR 886</a>: Updated the header component markup and removed old class names.</li>
298
298
</ul>
299
299
<h3id="phase-2-adding-local-styles">Phase 2: Adding Local Styles</h3><p>After refactoring the markup, I moved on to styling sections that Vocabulary doesn’t cover. Here are some of the merged PRs so far;</p>
300
300
<ul>
301
-
<li><ahref="https://github.com/creativecommons/creativecommons.github.io-source/pull/888">PR 888</a>: Added local styles based on Creative Commons’ main website for the homepage and other sections, such as “Get Involved” and “Featured Projects.”</li>
302
-
<li><ahref="https://github.com/creativecommons/creativecommons.github.io-source/pull/891">PR 891</a>: Created a new <code>issue-finder.css</code> file to restyle the Issue Finder page while removing legacy styles but maintaining legacy design.</li>
303
-
<li><ahref="https://github.com/creativecommons/creativecommons.github.io-source/pull/898">PR 898</a>: Integrated Datatables and jQuery by adding them to a vendor folder. Styled the table and code blocks using existing website styles.</li>
304
-
<li><ahref="https://github.com/creativecommons/creativecommons.github.io-source/pull/990">PR 990</a>: Styled the CC Search archive table using Datatables.</li>
301
+
<li><ahref="https://github.com/creativecommons/ccos-website-source/pull/888">PR 888</a>: Added local styles based on Creative Commons’ main website for the homepage and other sections, such as “Get Involved” and “Featured Projects.”</li>
302
+
<li><ahref="https://github.com/creativecommons/ccos-website-source/pull/891">PR 891</a>: Created a new <code>issue-finder.css</code> file to restyle the Issue Finder page while removing legacy styles but maintaining legacy design.</li>
303
+
<li><ahref="https://github.com/creativecommons/ccos-website-source/pull/898">PR 898</a>: Integrated Datatables and jQuery by adding them to a vendor folder. Styled the table and code blocks using existing website styles.</li>
304
+
<li><ahref="https://github.com/creativecommons/ccos-website-source/pull/990">PR 990</a>: Styled the CC Search archive table using Datatables.</li>
305
305
</ul>
306
306
<h2id="current-status">Current Status</h2><p>I’m a little behind schedule—I had planned to start work on the Legal Database website by now. However, I’m wrapping up the CC Open Source website this week and will move on to the next phase soon.</p>
307
307
<h2id="lessons-learned">Lessons Learned</h2><p>This internship has been an incredible learning journey. Here are some key takeaways:</p>
</figure><h3id="improvements-in-the-lektor-project">Improvements in the Lektor project -</h3><p>I tried to write the perfect code that is cleaner and readable. I would try to demonstrate my effort using the home page code where I used <ahref="https://www.getlektor.com/docs/models/flow/">Lektor Flowblocks</a>. The new homepage design have four sections where each section communicated something and I realized they were all independent and building the whole page through one single template would become a bit messy and hard to handle. So I did some research and found a way where I could build sub-templates and use them all to develop a single page and Lektor’s flowblocks allowed me to do so. Here is one of the flowblock and if you want to check out the whole working you can go to — <ahref="https://github.com/creativecommons/creativecommons.github.io-source">CCOS Repository</a>.</p>
408
+
</figure><h3id="improvements-in-the-lektor-project">Improvements in the Lektor project -</h3><p>I tried to write the perfect code that is cleaner and readable. I would try to demonstrate my effort using the home page code where I used <ahref="https://www.getlektor.com/docs/models/flow/">Lektor Flowblocks</a>. The new homepage design have four sections where each section communicated something and I realized they were all independent and building the whole page through one single template would become a bit messy and hard to handle. So I did some research and found a way where I could build sub-templates and use them all to develop a single page and Lektor’s flowblocks allowed me to do so. Here is one of the flowblock and if you want to check out the whole working you can go to — <ahref="https://github.com/creativecommons/ccos-website-source">CCOS Repository</a>.</p>
409
409
<h4id="recent-blog-post-block">Recent Blog Post block -</h4><h5id="the-block-template">The block Template -</h5><pre><code>{% from "macros/author_name.html" import render_author_name %}
0 commit comments