IEEE.org     |     IEEE Xplore Digital Library     |     IEEE Standards     |     IEEE Spectrum     |     More Sites

Commit a1d5c2ae authored by Amy Rose's avatar Amy Rose
Browse files

deprecate and remove summit pages, remove and rework front matter templating...

deprecate and remove summit pages, remove and rework front matter templating for compatibility with GitHub Pages
parent 95c3a4ca
Pipeline #843 passed with stage
in 3 minutes and 22 seconds
......@@ -15,6 +15,3 @@
- name: Contribute
path: /contribute
- name: Summit
path: /summit
{% comment %}
Dynamically assign the page title, using the following order of preference:
1. Explicitly defined layout or page title
2. Currently active subnav section
3. First breadcrumb
4. Loud debug screaming to fix the title
1. Project name
2. Explicitly defined layout or page title
3. Currently active subnav section
4. First breadcrumb
5. Loud debug screaming to fix the title
{% endcomment %}
{% assign title = layout.title | default: page.title | flatify %}
{% assign title = page.project | default: layout.title | default: page.title %}
{% unless title %}
{% for section in page.subnav %}
{% if section.active == true %}
......
......@@ -17,23 +17,23 @@ TODO: documentation
/>
</div>
<div id="projects-container">
{% for project in site.projects %}
<div id="{{ project.slug }}" class="project">
<h2>{{ project.name }}</h2>
<p>{{ project.tldr }}</p>
<p>{{ project.owner }}</p>
<a href="{{ project.url | relative_url }}">View more</a>
{% for project-page in site.projects %}
<div id="{{ project-page.slug }}" class="project">
<h2>{{ project-page.project }}</h2>
<p>{{ project-page.tldr }}</p>
<p>{{ project-page.owner }}</p>
<a href="{{ project-page.url | relative_url }}">View more</a>
</div>
{% endfor %}
</div>
</div>
<script>
const PROJECTS_DATA = {
{% for project in site.projects %}
"{{ project.slug }}": {
"name": "{{ project.name }}",
"tldr": "{{ project.tldr }}",
"owner": "{{ project.owner }}",
{% for project-page in site.projects %}
"{{ project-page.slug }}": {
"name": "{{ project-page.project }}",
"tldr": "{{ project-page.tldr }}",
"owner": "{{ project-page.owner }}",
},
{% endfor %}
}
......
......@@ -68,9 +68,18 @@ layout: default
<div id="breadcrumbs">
<a href="{{ '/' | relative_url }}"> <b>Open@RIT</b> </a>
{% for crumb in breadcrumbs %}
{% comment %}
TODO: navigation rework, better allow dynamic breadcrumbs
{% endcomment %}
{% if crumb.name == "TEMP_REWORK_TODO_NAME" %}
{% assign crumb_name = title %}
{% endif %}
{% if crumb.path == "TEMP_REWORK_TODO_URL" %}
{% assign crumb_path = page.url %}
{% endif %}
/
<a href="{{ crumb.path | flatify | relative_url }}">
{{ crumb.name | flatify }}
<a href="{{ crumb_path | default: crumb.path | relative_url }}">
{{ crumb_name | default: crumb.name }}
</a>
{% endfor %}
</div>
......
......@@ -24,7 +24,7 @@
{% endfor %}
</head>
<body {% if layout.body-style %} style="{{layout.body-style | flatify}}" {% endif %}>
<body>
{{ content }}
{% include footer.html %}
</body>
......
---
layout: default
body-style: |
overflow-x: hidden;
padding: 0; margin: 0;
background-color: black;
background-image: url({{ page.banner | relative_url }});
background-size: contain;
background-repeat: no-repeat;
background-position: top;
---
<div class="event-head">
<div class="event-container">
<div class="event-banner">
{% assign newline = "%0A" | url_decode %}
<div>
{{ page.what | replace: "\n", "<br/>" }}
<h2> {{ page.when | replace: "\n", "<br/>" }} </h2>
<h3> {{ page.where | replace: "\n", "<br/>" }} </h3>
</div>
<div class="event-c2">
<img class="event-truchet" src="{{'/assets/images/ui/event-vector.svg' | relative_url }}"/>
<button class="event-save-button" style="cursor:initial !important">
Save the date
</button>
<span style="display:inline-flex;margin-top:12px !important;">
<a class="event-save" href="{{ '/assets/events/OpenWorkInAcademia.ics' | relative_url }}">
<img src="https://img.icons8.com/bubbles/48/000000/ical.png"/>
</a>
<a class="event-save" href="{{ page.event_link }}">
<img src="https://img.icons8.com/color/48/000000/google-calendar--v2.png"/>
</a>
</span>
</div>
</div>
</div>
</div>
<!-- The Actual Content -->
<main class="event-content" style="color:white">
<div class="event-container">
{{ content | replace: "\n", "<br/>" }}
</div>
</main>
---
layout: base
title: "{{ page.name }}"
load_scripts:
- /assets/js/project.js
......@@ -9,8 +8,8 @@ breadcrumbs:
path: /our-work/
- name: Our Fellows' Projects
path: /our-work/fellows-projects
- name: "{{ page.name }}"
path: "{{ page.url }}"
- name: TEMP_REWORK_TODO_NAME
path: TEMP_REWORK_TODO_URL
subnav:
- name: Our Work and Projects
......
---
layout: default
body-style: |
overflow-x: hidden;
padding: 0; margin: 0;
background-color: black;
---
<!-- The Actual Content -->
<main class="event-content" style="color:white">
<div class="event-container">
{{ content | replace: "\n", "<br/>" }}
</div>
</main>
# credit: http://acegik.net/blog/ruby/jekyll/plugins/howto-nest-liquid-template-variables-inside-yaml-front-matter-block.html
# modified to ignore non-templated content
module Jekyll
module ExpandNestedVariableFilter
def flatify(input)
text = input.to_s
if text.match?(/\{\{(.*?)\}\}/)
return Liquid::Template.parse(input).render(@context)
end
return text
end
end
end
Liquid::Template.register_filter(Jekyll::ExpandNestedVariableFilter)
---
layout: project
name: Sound Voltex
project: Sound Voltex
tldr: A 6-key + 2-knob game about applying effects to music
owner: dj TAKA
slug: test1
......
---
layout: project
name: beatmania IIDX
project: beatmania IIDX
tldr: The genre-defining 7-key + turntable game
owner: L.E.D.
slug: test2
......
---
layout: project
name: pop'n music
project: pop'n music
tldr: The deceptively difficult 9-button color burger-smashing game
owner: wac
slug: test3
......
---
layout: project
name: Dance Dance Revolution
project: Dance Dance Revolution
tldr: The ubiquitous 4-panel dance game that swept the world
owner: NAOKI
slug: test4
......
---
layout: project
name: jubeat
project: jubeat
tldr: A 16-button musical whack-a-mole game on life support
owner: S-C-U
slug: test5
......
---
layout: project
name: GuitarFreaks & DrumMania
project: GuitarFreaks & DrumMania
tldr: The games that Guitar Hero ripped off
owner: Yoshihiko Koezuka
slug: test5
slug: test6
---
## List of Services
......
---
layout: event
root: summit
banner: /assets/images/banners/open-truchet.png
title: open work in academia
what: <h2>A summit regarding</h2><h1>open work \n in academia</h1>
when: september 7-9, 2022
where: hyatt regency rochester \n 125 east main street,\n rochester, ny, 14604, us
event_link: https://calendar.google.com/event?action=TEMPLATE&tmeid=MzMwNHByamY4c3RhaGVsbzVsZnBucTQxc2kgY19iZmRqN2UyYXVhcGY3cWplZTFwcjk1cmllNEBn&tmsrc=c_bfdj7e2auapf7qjee1pr95rie4%40group.calendar.google.com
---
## Why Now?
The time is ripe to look at [Open Work](https://fossrit.github.io/open-work-definition/) across communities to compare, contrast, \nand cross-pollinate best practices.
- **The National Science Foundation** is soliciting proposals for funding to support “Open Source Ecosystems” to improve sustainability, impact, and translation of “open source research products.”
- **The National Institutes of Health** has released new policy to improve and refine the sharing of, and collaboration around, research data.
- **The National Academies of Science, Engineering, and Medicine (NASEM)** have issued a tool kit to improve and encourage university support of Open Scholarship.
- **Across the European Union**, the creation of national policies on Open Science and Open Source Program Offices (OSPOs) for Government is accelerating.
- **OSPOs have been created by a few universites** to utilize techniques pioneered in private industry to better facilitate academic Open Work.
## Join Us
[Open@RIT](https://openr.it) invites professionals from the Academic, Research and Open Source\n communities for a two and a half day gathering to explore topics such as:
- Measures of value, impact and translation of Open Work
- Policies around support and promotion for success in that work
- Building, sustaining and promoting Open Communities and Ecosystems
- Managing information overload and ferment in the field
- Existing practices and resources provided by academia to support Open Scholarship and industry
## Interested in Learning More?
<a class="event-save" href="./subscribe/" target="_blank">
<button class="event-save-button">
Subscribe for updates
</button>
</a>
<br/>
**The Open Work in Academia Summit is an event created by Open@RIT, a Key Research Center of the University that serves as its Open Programs Office.**
**The Summit is sponsored, in part, by a generous grant from the Alfred P. Sloan Foundation.**
---
layout: subscribe
root: summit
---
<!-- Begin Mailchimp Signup Form -->
<link href="//cdn-images.mailchimp.com/embedcode/classic-10_7_dtp.css" rel="stylesheet" type="text/css">
<style type="text/css">
#mc_embed_signup{background:#fff; clear:left; font:14px Helvetica,Arial,sans-serif; width:600px;}
/* Add your own Mailchimp form style overrides in your site stylesheet or in this style block.
We recommend moving this block and the preceding CSS link to the HEAD of your HTML file. */
</style>
<div id="mc_embed_signup">
<form action="https://openr.us14.list-manage.com/subscribe/post?u=14fdfa799ffb9532bd81b4892&id=666dbd6d28" method="post" id="mc-embedded-subscribe-form" name="mc-embedded-subscribe-form" class="validate" target="_blank" novalidate>
<div id="mc_embed_signup_scroll">
<h2>Subscribe</h2>
<div class="indicates-required"><span class="asterisk">*</span> indicates required</div>
<div class="mc-field-group">
<label for="mce-EMAIL">Email Address <span class="asterisk">*</span>
</label>
<input type="email" value="" name="EMAIL" class="required email" id="mce-EMAIL">
</div>
<div class="mc-field-group">
<label for="mce-FNAME">First Name </label>
<input type="text" value="" name="FNAME" class="" id="mce-FNAME">
</div>
<div class="mc-field-group">
<label for="mce-LNAME">Last Name </label>
<input type="text" value="" name="LNAME" class="" id="mce-LNAME">
</div>
<div id="mce-responses" class="clear foot">
<div class="response" id="mce-error-response" style="display:none"></div>
<div class="response" id="mce-success-response" style="display:none"></div>
</div> <!-- real people should not fill this in and expect good things - do not remove this or risk form bot signups-->
<div style="position: absolute; left: -5000px;" aria-hidden="true"><input type="text" name="b_14fdfa799ffb9532bd81b4892_666dbd6d28" tabindex="-1" value=""></div>
<div class="optionalParent">
<div class="clear foot">
<input type="submit" value="Subscribe" name="subscribe" id="mc-embedded-subscribe" class="button">
<p class="brandingLogo"><a href="http://eepurl.com/hWv-Tv" title="Mailchimp - email marketing made easy and fun"><img src="https://eep.io/mc-cdn-images/template_images/branding_logo_text_dark_dtp.svg"></a></p>
</div>
</div>
</div>
</form>
</div>
<script type='text/javascript' src='//s3.amazonaws.com/downloads.mailchimp.com/js/mc-validate.js'></script><script type='text/javascript'>(function($) {window.fnames = new Array(); window.ftypes = new Array();fnames[0]='EMAIL';ftypes[0]='email';fnames[1]='FNAME';ftypes[1]='text';fnames[2]='LNAME';ftypes[2]='text';fnames[3]='ADDRESS';ftypes[3]='address';fnames[4]='PHONE';ftypes[4]='phone';fnames[5]='BIRTHDAY';ftypes[5]='birthday';}(jQuery));var $mcj = jQuery.noConflict(true);</script>
<!--End mc_embed_signup-->
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment