Minor Tweaks based on Issue 63

- Fixed open_Projects widget not linking to individual headings
- Renamed openings to Careers (careers.md page, URL/Permalink and Navigation menu)
- Added Candidate Guidelines to Careers page from https://github.com/vgvassilev/clad/wiki/GSoC-2024
- added a "jekyll-redirect-from" gem and plugin to setup URL redirection for deleted pages (should be supported by Github pages in production, will need to test after deployment)
- added to openings page:
 redirect_from:
  - /vacancies/

Author: QuillPusher

Gemfile

@@ -5,3 +5,4 @@ gem "webrick"
 gem "kramdown-parser-gfm"
 #gem "jekyll-github-metadata"
 #gem "jekyll-get-json"
+gem 'jekyll-redirect-from'

_config.yml

@@ -43,7 +43,8 @@ kramdown:
   enable_coderay: false
   parse_block_html: true # default for kramdown is false. This will enable using Markdown links
 
-#plugins:
+plugins:
+  - jekyll-redirect-from
 #  - "jekyll-github-metadata"
 #  - "jekyll-get-json"
 

_includes/header.html

@@ -33,7 +33,7 @@
       <li class="nav-item dropdown">
         <a href="#" class="nav-link dropdown-toggle" id="dropdown03" data-toggle="dropdown" role="button" aria-haspopup="true" aria-expanded="false">Join us</a>
         <ul class="dropdown-menu" aria-labelledby="dropdown03">
-          <li class="dropdown-item"> <a class="nav-link" href="/vacancies">Openings</a></li>
+          <li class="dropdown-item"> <a class="nav-link" href="/careers">Careers</a></li>
           <li class="dropdown-item"> <a class="nav-link" href="/meetings">Project Meetings</a></li>
           <li class="dropdown-item"> <a class="nav-link" href="/team_meetings">Team Meetings</a></li>
           <li class="dropdown-item"> <a class="nav-link" href="/open_projects">Open Projects</a></li>

_includes/open-projects.html

@@ -5,7 +5,7 @@ <h4><b>Open Projects</b></h4>
 
     {% assign top_articles = site.data.openprojectlist %}
     {% for article in top_articles limit:4 %}
-      <p><a href="{{ site.url }}{{ site.baseurl }}/open_projects/#{{ article.name | slugify }}">{{ article.name }}</a><br /></p>
+      <p><a href="{{ site.url }}{{ site.baseurl }}/open_projects#{{ article.name | slugify }}">{{ article.name }}</a><br /></p>
     {% endfor %}
 
 

_pages/careers.md

@@ -0,0 +1,53 @@
+---
+title: "Careers at Compiler Research Organization"
+layout: textlay
+excerpt: "Openings"
+sitemap: false
+permalink: /careers
+redirect_from:
+  - /vacancies/
+---
+
+# Open Positions
+
+We are always looking for new group members with passion, talent, and grit!
+
+# Student Opportinuties
+
+If you are interested in working with us for a fixed period of time, there are
+number of programs which offer scholarships:
+
+* [Google Summer of Code](https://summerofcode.withgoogle.com/how-it-works/)
+* [IRIS-HEP Fellow Program](https://iris-hep.org/fellows.html)
+* [CERN Students Programs](https://careers.cern/students)
+
+# Just looking for a cool spare time project?
+
+Please visit our [open projects](/open_projects) page.
+
+# Candidate Guidelines
+
+If you have interest in working on the project there is a list of things to do in order to maximize your chances to get selected:
+
+1. Contact the mentors and express interest in the project. Make sure you attach your CV;
+2. Download the source code of the project, build it and run the demos;
+3. Start familiarizing yourself with the codebase;
+4. If you have questions you can always contact a mentor.
+
+## Candidate Evaluation
+
+The mentors are interested in working with all candidates but unfortunately not everyone can be selected. There are a few tasks which give bonus points to candidate's application:
+
+- Submit a valid bug -- demonstrates that the candidate has completed step 2 and 3 from the previous section.
+- Fix a bug -- demonstrates the technical skills of the candidate and shows he/she can work independently on the project. The mentors can suggest looking into these good first issues. Fixing one issue may be enough to become a successful candidate.
+
+## What not to do and will give you negative points
+
+1. Contact the mentors with very generic requests such as "Please guide me through the X". You need to show that you have spent time on the problem. Such emails prove otherwise.
+2. Contact each mentor individually. You should use "reply-all" feature of your email and discuss openly with your prospective mentors the project.
+3. Send the same email to express interest on multiple projects. If you do not invest time to write separate emails for the different projects why the mentors should?
+4. Comment under opened issues with generic requests as described in 1. You need to show that you can work on bugs and use bug trackers. That shows the opposite.
+5. Use LLM-generated content. You should prove to yourself that project is appropriate for you otherwise we will hire the LLM instead of you.
+6. If any of the criteria is met to some degree mentors are free to tell you so or even not respond to your requests. We understand that may seem harsh, however, you should appreciate other's time at least as much as they appreciate yours!
+
+Good luck!