Clean up HTML comments and add how-to-apply guide#41
Clean up HTML comments and add how-to-apply guide#41jbanmol wants to merge 2 commits intohumanai-foundation:masterfrom
Conversation
|
Cleaned up HTML comments in multiple files and added GSoC how-to-apply guide |
There was a problem hiding this comment.
Pull request overview
This PR updates the HumanAI GSoC site content and presentation by adding a new “How to Apply” guide, modernizing styling for proposal listings, and cleaning up layout/navigation markup.
Changes:
- Added a new
gsoc/how-to-apply.mdapplication guide for GSoC 2026. - Refreshed site styling (
css/hsf.css) and changed proposal listings (_includes/gsoc_proposal.ext,_includes/gsoc_project.ext) to a grid/card layout. - Simplified/updated homepage layout (
_layouts/main.html), navbar (_includes/navbar.ext), and expanded/structured the student blogs page (_activities/studentblogs.md).
Reviewed changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 7 comments.
Show a summary per file
| File | Description |
|---|---|
gsoc/how-to-apply.md |
New step-by-step application guide content (includes tables/timeline). |
css/hsf.css |
New design tokens + card/grid/table styling + updated navbar/link styles. |
_layouts/main.html |
Removes large commented blocks; leaves the GSoC 2026 intro section. |
_includes/navbar.ext |
Replaces prior menu structure with a GSoC dropdown + quick links. |
_includes/gsoc_proposal.ext |
Proposal listing switched from bullet list to HTML card grid with metadata tags. |
_includes/gsoc_project.ext |
Project proposal listing switched from bullet list to HTML card grid with metadata tags. |
_activities/studentblogs.md |
Retitled and reformatted into structured tables + “Write your blog post” section. |
Comments suppressed due to low confidence (1)
_layouts/main.html:50
- There is an extra closing
</a>at the end of this paragraph (... participating as a project. </a>), which makes the HTML invalid. Remove the stray closing tag so the link markup is balanced.
<p class="lead">
The HumanAI open source umbrella organization plans to participate in the <a href="https://summerofcode.withgoogle.com/">2026 Google Summer of Code</a>. If you are a student interested in our <a href="/activities/gsoc2026.html">projects</a> please check our <a href="/gsoc/2026/summary.html">ideas page</a>.
HumanAI is an umbrella organization that welcomes other projects and organizations related to machine-learning in Arts and Humanities. Please contact the admins at <a href="mailto:human-ai@cern.ch">human-ai@cern.ch</a> if you are interested in participating as a project. </a>
</p>
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| float: right; | ||
| .blog-footer a { | ||
| color: var(--color-primary); | ||
| } |
There was a problem hiding this comment.
alignleft/alignright are still used (e.g. in _includes/fwd_back_link.ext) but their CSS rules were removed in this rewrite, so previous/next navigation will no longer float left/right. Reintroduce these class styles (or update the include to use Bootstrap equivalents like pull-left/pull-right) to avoid layout regression.
| } | |
| } | |
| /* Legacy float helpers used in navigation and content */ | |
| .alignleft { | |
| float: left; | |
| margin-right: 10px; | |
| } | |
| .alignright { | |
| float: right; | |
| margin-left: 10px; | |
| } |
| <!-- GSoC Menu --> | ||
| <li class="dropdown"> | ||
| <a class="dropdown-toggle" data-toggle="dropdown" href="#" id="gsoc_menu" aria-haspopup="true" aria-expanded="false"> | ||
| GSoC <span class="caret"></span> | ||
| </a> | ||
| <ul class="dropdown-menu" aria-labelledby="gsoc_menu"> | ||
| <li><a href="/activities/gsoc2026.html">Google Summer of Code 2026</a></li> | ||
| <li><a href="/gsoc/2026/summary.html">All 2026 Proposals</a></li> | ||
| <li role="separator" class="divider"></li> | ||
| <li><a href="/activities/gsoc2025.html">GSoC 2025</a></li> | ||
| <li><a href="/activities/gsoc2024.html">GSoC 2024</a></li> | ||
| </ul> |
There was a problem hiding this comment.
This PR adds gsoc/how-to-apply.md, but the new guide isn’t linked from the primary navigation. Consider adding a "How to Apply" item under the GSoC dropdown (e.g. pointing to /gsoc/how-to-apply.html) so users can discover it.
| <tr> | ||
| <td>Shashank Shekhar Singh</td> | ||
| <td>RenAIssance (OCR)</td> | ||
| <td><a href="https://medium.com/@shashankshekharsingh1205/from-idea-to-user-tool-continuing-my-journey-with-humanai-in-the-google-summer-of-code-2025-96243994fd4f" target="_blank">Tool for Historical Text Recognition using Weighted CRNN Model →</a></td> |
There was a problem hiding this comment.
Links that open in a new tab (target="_blank") should include rel="noopener noreferrer" to prevent reverse-tabnabbing and to avoid leaking window.opener. Please add rel to these external blog links (and any others on this page that use target="_blank").
| <td><a href="https://medium.com/@shashankshekharsingh1205/from-idea-to-user-tool-continuing-my-journey-with-humanai-in-the-google-summer-of-code-2025-96243994fd4f" target="_blank">Tool for Historical Text Recognition using Weighted CRNN Model →</a></td> | |
| <td><a href="https://medium.com/@shashankshekharsingh1205/from-idea-to-user-tool-continuing-my-journey-with-humanai-in-the-google-summer-of-code-2025-96243994fd4f" target="_blank" rel="noopener noreferrer">Tool for Historical Text Recognition using Weighted CRNN Model →</a></td> |
| <h4><a href="{{ proposal.url }}">{{ proposal.title }}</a></h4> | ||
| <div class="card-meta"> | ||
| {% if proposal.difficulty %} | ||
| <span class="tag tag-difficulty">{{ proposal.difficulty }}</span> | ||
| {% endif %} | ||
| {% for req in proposal.requirements limit:5 %} | ||
| <span class="tag">{{ req }}</span> | ||
| {% endfor %} | ||
| {% for tag in proposal.tags limit:5 %} | ||
| <span class="tag">{{ tag }}</span> | ||
| {% endfor %} | ||
| </div> | ||
| {% if proposal.duration %} | ||
| <p class="card-duration">⏱ {{ proposal.duration }}</p> | ||
| {% endif %} |
There was a problem hiding this comment.
The proposal cards reference proposal.difficulty, proposal.requirements, proposal.tags, and proposal.duration, but the existing proposal pages appear to express these as Markdown sections (e.g. ## Requirements, ## Duration) rather than front-matter fields. As a result, these loops will render empty for most/all proposals; either add these fields to proposal front matter (preferred for structured display) or adjust the card template to only render data that actually exists.
| <h4><a href="{{ proposal.url }}">{{ proposal.title }}</a></h4> | ||
| <div class="card-meta"> | ||
| {% if proposal.difficulty %} | ||
| <span class="tag tag-difficulty">{{ proposal.difficulty }}</span> | ||
| {% endif %} | ||
| {% for req in proposal.requirements limit:5 %} | ||
| <span class="tag">{{ req }}</span> | ||
| {% endfor %} | ||
| {% for tag in proposal.tags limit:5 %} | ||
| <span class="tag">{{ tag }}</span> | ||
| {% endfor %} | ||
| </div> | ||
| {% if proposal.duration %} | ||
| <p class="card-duration">⏱ {{ proposal.duration }}</p> | ||
| {% endif %} | ||
| </div> |
There was a problem hiding this comment.
Same as in gsoc_proposal.ext: this card layout expects structured fields like difficulty, requirements, tags, and duration on each proposal, but existing proposals typically don’t define them in front matter. This will cause most cards to show only the title; consider adding front-matter fields or simplifying the card until the data is available.
| | Section | What to Include | | ||
| |---|---| | ||
| | **Project summary** | What you will build, in 2–3 sentences | | ||
| | **Motivation** | Why this project, why you, why HumanAI | | ||
| | **Technical approach** | Specific methods, models, tools, datasets you plan to use | | ||
| | **Week-by-week timeline** | 12–14 week breakdown, one milestone per week | | ||
| | **Deliverables** | Concrete outputs — code, model, dataset, documentation | | ||
| | **About you** | Relevant skills, past projects, links to code (GitHub) | |
There was a problem hiding this comment.
These Markdown tables start rows with || ..., which creates an extra empty first column in standard Markdown table syntax. Use a single leading | (or no leading pipe) consistently so the table renders as 2 columns without a blank column.
| | Date | Milestone | | ||
| |---|---| | ||
| | Now → April 8 | **Application window open** — submit via GSoC portal | | ||
| | April 8 | ⚠️ **Proposal submission deadline** | | ||
| | May 1–26 | Community Bonding Period — meet your mentor, set up tools | | ||
| | May 27 – July 14 | Coding Period 1 | | ||
| | July 14 | Midterm evaluation | | ||
| | July 14 – September 1 | Coding Period 2 | | ||
| | September 1 | Final evaluation & code submission | |
There was a problem hiding this comment.
Same table-formatting issue here: the || at the start of each row will render an unintended empty first column. Adjust the rows/separator to standard Markdown table syntax so the timeline table displays correctly.
No description provided.