Fix global header display issue

.dockerignore

@@ -0,0 +1,25 @@
+**/.classpath
+**/.dockerignore
+**/.env
+**/.git
+**/.gitignore
+**/.project
+**/.settings
+**/.toolstarget
+**/.vs
+**/.vscode
+**/*.*proj.user
+**/*.dbmdl
+**/*.jfm
+**/bin
+**/charts
+**/docker-compose*
+**/compose*
+**/Dockerfile*
+**/node_modules
+**/npm-debug.log
+**/obj
+**/secrets.dev.yaml
+**/values.dev.yaml
+LICENSE
+README.md

.github/workflows/docker-image.yml

@@ -0,0 +1,18 @@
+name: Docker Image CI
+
+on:
+  push:
+    branches: [ "main" ]
+  pull_request:
+    branches: [ "main" ]
+
+jobs:
+
+  build:
+
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v3
+    - name: Build the Docker image
+      run: docker build . --file Dockerfile --tag my-image-name:$(date +%s)

CONTRIBUTING.md

@@ -3,30 +3,26 @@
 Thank you for your interest in contributing to CC Open Source! This document is
 a set of guidelines to help you contribute to this project.
 
-
 ## Code of Conduct
 
 By participating in this project, you are expected to uphold our [Code of
 Conduct][code_of_conduct].
 
 [code_of_conduct]: https://opensource.creativecommons.org/community/code-of-conduct/
 
-
 ## Project Documentation
 
 The `README` in the root of the repository should contain or link to project
 documentation. If you cannot find the documentation you're looking for, please
 file a GitHub issue with details of what you'd like to see documented.
 
-
 ## How to Contribute
 
 Please follow the processes in our general [Contributing Code][contributing]
 guidelines on the Creative Common Open Source website.
 
 [contributing]: https://opensource.creativecommons.org/contributing-code/
 
-
 ## Questions or Thoughts?
 
 Talk to us on [one of our community forums][community].

LICENSE

@@ -1,4 +1,4 @@
-MIT License
+# MIT License
 
 Copyright (c) 2019 Creative Commons
 

README.md

@@ -2,7 +2,6 @@
 
 Collection of resources on Creative Commons (CC) tools and other open topics
 
-
 ## Overview
 
 Welcome to the CC Resources Archive. The idea of this project is to have a
@@ -11,7 +10,6 @@ that people make about Creative Commons licenses and open content topics in
 general. The live site is at
 [resources.creativecommons.org](https://resources.creativecommons.org/).
 
-
 ## How it works
 
 The website is built using [Jekyll](http://jekyllrb.com/docs/home/), a simple
@@ -42,32 +40,29 @@ File: creative-commons-kiwi.textile
 permalink: /six-licenses-for-sharing-your-work/
 File: six-licenses-for-sharing-your-work.html
 
-
 ### Category URLs
 
 You can format the `resources.creativecommons.org/all?` URL to show any
 category or combination of categories you want. For example, videos available
 in English about licenses:
 
-http://resources.creativecommons.org/all/?&topic=licenses&medium=video&language=en
+<http://resources.creativecommons.org/all/?&topic=licenses&medium=video&language=en>
 
 You can use any category that's listed in one or more resources pages, not just
 the ones available in the menu on "all." For example, resources about music:
 
-http://resources.creativecommons.org/all/?&topic=music
+<http://resources.creativecommons.org/all/?&topic=music>
 
 It will also be trivial to create an RSS feed for any category or combination
 of categories - for example, to create a feed of all resources available in
 Spanish for embedding in an affiliate site. If you need one, submit an issue
 through GitHub.
 
-
 ### The index page
 
 The index page pulls up to 16 featured items. Each featured page has a
 "featured" variable. The number is the order in which they should appear.
 
-
 ### Menu categories
 
 The list of topics, media, and languages on the homepage is dictated by the
@@ -89,51 +84,52 @@ in the URLs and CSS classes. It's also what you use in the resource page itself
 to identify the category. So these should be relatively short, but still
 sensical.
 
-
 ## Local Development
 
 Local development can be previewed by installing Jekyll or by using Docker. We
 think the latter experience is easier to setup with more consistent behavior.
 
-
 ### Docker Compose setup
 
 1. [Install Docker Engine](https://docs.docker.com/engine/install/)
 2. In your terminal, change the directory to where you have cloned this repository
    (or a fork of it)
 3. **Run the container:**
+
    ```shell
    docker compose up
    ```
+
    - This should result in the container being built if it's the first time
    - The docker container may be slow :hourglass_flowing_sand::persevere: When
      it is ready you should see:
-     ```
-     jekyll-cc-resource-archive  |     Server address: http://0.0.0.0:4000
+
+**```**
+     jekyll-cc-resource-archive  |     Server address: <http://0.0.0.0:4000>
      jekyll-cc-resource-archive  |   Server running... press ctrl-c to stop.
-     ```
-   - Once running successfully, you can access the site in your browser at
+
+****```****
+
+- Once running successfully, you can access the site in your browser at
      [localhost:4000](http://localhost:4000/)
-6. **Stop the container:** To stop the app from running, simply open another
+**6. ****Stop the container:** To stop the app from running, simply open another
    instance of the terminal and type
+
    ```shell
    docker compose down
-   ```
+   `
    or you can simply revisit the existing terminal which is running the
    container and type `CTRL + C`
 
-
 ## License
 
-
 ### Code
 
 [`LICENSE`](LICENSE): the code within this repository is licensed under the
 Expat/[MIT][mit] license.
 
 [mit]: http://www.opensource.org/licenses/MIT "The MIT License | Open Source Initiative"
 
-
 ### Content/Text
 
 [![CC BY 4.0 license button][cc-by-png]][cc-by]

docs/cc-version-40-for-education.md

@@ -15,8 +15,8 @@ author: Jane Park
 license: CC BY 2.5
 ---
 
-In 2013, we launched version 4.0 of the CC license suite and it is ready for anyone to use now to apply to their educational resources or other creative works. 
+In 2013, we launched version 4.0 of the CC license suite and it is ready for anyone to use now to apply to their educational resources or other creative works.
 
-But what does that mean? What's new in 4.0 that wasn't there in 3.0? And just as importantly, what has stayed the same so that you don't have to worry about changes to licenses you weren't expecting? Lastly, I'll go over some examples of organizations and institutions who have already upgraded to the 4.0 version of whatever license they were using. 
+But what does that mean? What's new in 4.0 that wasn't there in 3.0? And just as importantly, what has stayed the same so that you don't have to worry about changes to licenses you weren't expecting? Lastly, I'll go over some examples of organizations and institutions who have already upgraded to the 4.0 version of whatever license they were using.
 
-Note: These slides are meant to be used as a resource by presenters --- please download the file and see the detailed notes accompanying each slide for the actual information. 
+Note: These slides are meant to be used as a resource by presenters --- please download the file and see the detailed notes accompanying each slide for the actual information.

docs/creative-commons-kiwi.md

@@ -18,4 +18,4 @@ author: Creative Commons Aotearoa New Zealand
 license: CC BY 3.0
 ---
 
-A quick video on the basics of Creative Commons. Downloadable from [Vimeo](//vimeo.com/26118296) and [Internet Archive](//archive.org/details/CreativecommonsKiwi).
+A quick video on the basics of Creative Commons. Downloadable from [Vimeo](//vimeo.com/26118296) and [Internet Archive](//archive.org/details/CreativecommonsKiwi).

docs/oer-whats-in-it-for-me.md

@@ -19,4 +19,3 @@ license: CC BY 4.0
 ---
 
 Created during a 2-day workshop meeting of open education enthusiasts in Porto, Portugal ([related blog post](http://web.archive.org/web/20160328190836/http://oerpolicy.eu/postcard-from-the-oer-workshop-in-porto/)).
-

docs/what-does-creative-commons-mean.md

@@ -18,4 +18,4 @@ downloadurl: http://www.bildersuche.org/en/creative-commons-infographic.php
 A fun infographic explaining the conditions on CC licenses.
 
 - [German](http://www.bildersuche.org/creative-commons-infografik.php)
-- [English](http://www.bildersuche.org/en/creative-commons-infographic.php)
+- [English](http://www.bildersuche.org/en/creative-commons-infographic.php)

docs/why-open-education-matters.md

@@ -1,7 +1,7 @@
 ---
 title: Why Open Education Matters
 published: true
-weight: 3
+weight: 4
 featured: 10
 layout: resource
 image-full: /images/why-open-education-matters-500.gif
@@ -19,4 +19,4 @@ license: CC BY-SA 3.0
 
 Fun, animated video about open educational resources. Winner of Creative Commons' [Why Open Education Matters video competition](http://creativecommons.org/weblog/entry/33343).
 
-[Also available on Vimeo.](http://vimeo.com/43401199)
+[Also available on Vimeo.](http://vimeo.com/43401199)

resourcetemplate.md

@@ -20,19 +20,19 @@ embed: <iframe src="https://archive.org/embed/2-brian-wannaworktogether" width="
 
 When you create your resource, delete any lines above that aren't applicable. Also delete all of the content below the front matter and replace it with whatever you'd like to appear on the resource page.
 
-**title**
+******title******
 
 Self-explanatory. 50 characters or less.
 
-**published**
+## published
 
 True tells Jekyll to display the file.
 
-**layout**
+## layout
 
 resource
 
-**weight**
+## weight
 
 The weight ranking determines the order in which resources should appear on the ["All" page](http://resources.creativecommons.org/all/). There are four options:
 
@@ -41,60 +41,59 @@ The weight ranking determines the order in which resources should appear on the
 3. Content that is designed for a specific use case. For example, something that only focuses on CC licenses as they relate to science or government.
 4. Content on issues that touch indirectly on CC, or is highly tailored to a specific audience.
 
-**featured**
+## featured
 
 [The homepage](http://resources.creativecommons.org/) can feature up to 16 resources. This is the highest quality stuff with the broadest audience. If you add a "featured" number to your resource, please change the numbers on the other featured resources accordingly. Or better yet, suggest the change as an [issue on Github](https://github.com/creativecommons/cc-resource-archive/issues) and we can discuss it there.
 
-**author**
+## author
 
 The creator of the work, however he/she/it wants to be credited.
 
-**license**
+## license
 
 The license the work is under. Format as follows:
+
 - CC0
 - CC BY 2.0
 - CC BY-NC 4.0
 - CC BY-SA 3.0 US
 - CC BY-ND 3.0 IT
 - etc.
 
-**image-full and image-thumb**
+## image-full and image-thumb
 
-Image-full should be 500px * 375px. Image-thumb should be 200*150. Put in the "images" folder. Use the full title as the filename, separated by hyphens.
+Image-full should be 500px *375px. Image-thumb should be 200*150. Put in the "images" folder. Use the full title as the filename, separated by hyphens.
 
-**topic**
+## topic
 
 The "string" for each relevant topic, separated by spaces. [Use the topics listed here](https://github.com/creativecommons/cc-resource-archive/blob/gh-pages/_data/topics.yml).
 
-**language**
+## language
 
 The two-letter abbreviation for each language, separated by spaces. [Here's the list of languages currently in use](https://github.com/creativecommons/cc-resource-archive/blob/gh-pages/_data/languages.yml).
 
-**medium**
+## medium
 
 The string for the medium the work is in. Current options are print, video, website, course, and slides.
 
-**permalink**
+## permalink
 
 The title, in lowercase, with hyphens between each word. See example formatting.
 
-**blurb**
+## blurb
 
 The text that will appear below the thumbnail in the listing. 140 characters or less.
 
-**repourl**
+## repourl
 
 If the source files for the resource are available online, put the URL where they can be found here.
 
-**downloadurl**
+## ownloadurl
 
 The URL where the resource can be accessed or downloaded. Use the most obvious URL. For example, if the project is hosted on Internet Archive, use the URL for the info page, not the direct download for the file.
 
-**embed**
+## embed
 
 If the resource is embeddable (for example, a video or slides), paste in the iframe code, with no returns.
 
-
-
-*Last updated April 25, 2014*
+***Last updated April 25, 2014*