Describe the bug
There is a spelling error on the "Contributing Code" Page on the creative commons website (https://opensource.creativecommons.org/contributing-code/)

To Reproduce
Steps to reproduce the behavior:

1. Go to 'https://opensource.creativecommons.org'
2. Click on ' "Overview" under "Contributing code" in the top menu'
3. Scroll down to 'section titled "Proposing a new issue"'
4. See typing error on the second line "amd" as seen in the screenshot below with a red circle.

Expected behavior
I expect the word "amd" to be replaced with "and".

Screenshots

Desktop (please complete the following information):

• OS: Windows
• Browser Firefox
• Version 69.0.1

Is your feature request related to a problem? Please describe.
The current GitHub site gives the default 404 when one visits a non-existent page.

Describe the solution you'd like
Since GitHub Pages support custom 404 pages, we should probably have one.

Overview

It would be nice to show something like "This blog post is part of the series" for blog posts that are related.

Look and feel

Series can already be tracked via categories, but we would like a separate mechanism (like authors) to track them. Please include design mock-ups or screenshots with any proposals or pull requests.

Series Examples

• https://creativecommons.github.io/blog/entries/cc-catalog-leverage-open-data-1/ is part of a three part series about the CC Catalog
• All posts that a given student posts during Google Summer of Code could be part of a series (to add more context to each individual post)

Expected behavior

• Blog posts have a note associated with them that shows that the post is part of a series
• Each series has its own page that shows all the blog posts that are a part of that series
• In the backend, it should be implemented similar to how authors are implemented

Describe the bug

In the list of slack channels, on page
https://opensource.creativecommons.org/community/
there is a missing 'l' in toolkit in the link to 'CC Platform Tookit'

To Reproduce

1. Go to https://opensource.creativecommons.org/community/
2. Scroll down to the Slack channels table.
3. In the third entry from the bottom
4. The link to the #cc-outreachy-platform-toolkit that is in the right column is misspelled. An 'l' needs to be added to change 'tookit' to 'toolkit'

Screenshots

Desktop (please complete the following information)

• OS: macOS Mojave Version 10.14.6
• Safari
• Version 13.0.4

We'd like to move old information about CC's participation in Google Summer of Code from the public wiki to the Internships > History section of CC Open Source.

https://wiki.creativecommons.org/wiki/Summer_of_Code_2006
https://wiki.creativecommons.org/wiki/Summer_of_Code_2007
https://wiki.creativecommons.org/wiki/Summer_of_Code_2008
https://wiki.creativecommons.org/wiki/Summer_of_Code_Selection_Criteria

There may be other pages as well, this needs to be researched.

We shouldn't be copying this information blindly; part of this task involves figuring out which information is useful/interesting and how to organize it.

The site currently uses vanilla Bootstrap, please make it look better. Feel free to make any layout and presentation changes you like, I'm not attached to any particular way that I set it up.

Templates source for making style changes: https://github.com/creativecommons/creativecommons.github.io-source/tree/master/templates (edited)

CSS: https://github.com/creativecommons/creativecommons.github.io-source/tree/master/assets/static (I'm loading bootstrap from a CDN)

Problem Description / Context

Starting in 2019, Creative Commons began developing a design framework for use across CC web products. During Q1 of 2020, we expect to have the first complete version of the design library (known as Vocabulary), ready for use in future designs, and redesigns of existing products.

By the end of 2020, the goal of the Tech & Product team at Creative Commons is that all CC web products have a consistent design.

For the CC Open Source website, analytics indicate that there is a high bounce rate, and users spend a short time on specific pages, where ideally we are spurring action, such as the pages around contributing code and current projects. The information that currently exists on the site is in some cases presented in a confusing way.

Solution Description / Main Goal

The goal of this project is to redesign all pages of the current site, using existing content, to improve user experience. The redesign must use Vocabulary and the Design Library in Figma.
Please note that no content (i.e. written word) changes are part of this project, this involves only the redesign of existing content.

If there is a need for design components that are not currently defined in CC’s Design Library, the designer is encouraged to make suggestions for addition to the Design Library, to be reviewed by CC’s product team.

Workflow

The designer should not move between numbered steps without consultation with and sign-off by the CC product team. The designer must meet with the product team prior to tackling each subsequent step.

The project should be tackled in the following process:

1. Develop a wireframe of the homepage
2. This proposal should include changes to the content layout
3. Develop wireframes for other pages on the site
4. Create a high-fidelity mockup of the homepage, using the Figma Design Library
5. Create high-fidelity mockups of other pages on the site, using the Figma Design Library

Success & Deliverables

Success in this project is defined by mockups in Figma being approved by CC’s product team.

Resources & Supporting Links

The designer will have access to CC’s Figma account, as an editor.
Figma Design Library: https://www.figma.com/file/l4Mt3dn3Ndtrvrb4aLcwXI/Design-Library?node-id=0%3A1

Vocabulary Repo: https://github.com/creativecommons/vocabulary

Vocabulary Storybook: https://cc-vocabulary.netlify.com/storybook/?path=/story/vocabulary-welcome--welcome

Next Steps

Upon successful completion of the redesign, the user is invited to implement the design changes directly. If that work moves forward separate tickets will be created.

Describe the bug

Warning message:

npm WARN deprecated [email protected]: Deprecated.
         Please use https://github.com/webpack-contrib/mini-css-extract-plugin

Replacing extract-text-webpack-plugin with mini-css-extract-plugin is easy enough, but I don't know how to verify the change (I'm not a frontend developer):

1. npm remove extract-text-webpack-plugin
2. npm install --save-dev mini-css-extract-plugin
3. ...
4. Profit!

Someone with better familiarity needs to update the package used and verify that the site still builds as good or better than before.

Additional context

• https://github.com/webpack-contrib/mini-css-extract-plugin

Describe the bug

There is no information on webpack's dependencies in the README.

(Webpack is invoked via lektor/lektor-webpack-support)

Expected behavior

At a minimum, there should be information about what is required on macOS using Homebrew.

Information for GNU/Linux would be nice to have.

Describe the bug

There are a lot of archived blog entries with remote images. Any with a URL that starts with http://labs.creativecommons.org/ should be hosted from the same directory as the blog entry.

Related Links

• Archive: CC Technical Blog (2007-2014) — Creative Commons on GitHub

See #43 for context. This should be worked on after #49 since that PR adds categories.

Post categories are currently not being displayed in the UI, they should be displayed on the post page. The design is up to you.

Blog author pages currently look like this:

We should add fields for full name and bio URL and display them on the author page if they are available. Pulling in gravatar images would be nice.

We should also update blog posts to show the author's full name (if it exists) instead of their username.

At the top of the page (in the navigation bar) one of the tabs is called 'CC.org'. Unfortunately, if a user types that into their address bar rather than clicking the link, they will end up at the website of the Christian Coalition, which would not be what they expect. The tab should either read 'creativecommons.org', or perhaps just 'Creative Commons' to avoid confusion.

We'd like to publish an RSS feed for our blog so that people can subscribe it and we can also use it to set up automated notifications in other applications (such as Slack).

Is your feature request related to a problem? Please describe.
We currently use TravisCI. We'd like to use GitHub Actions instead.

Describe the solution you'd like
The project should build on GitHub Actions and the automatic build and deployment should work.

Is your feature request related to a problem? Please describe.
Category and author pages have to be added manually for new authors and categories despite having enough information to generate basic pages automatically. This makes the process of adding a new blog post take longer. See the instructions on https://opensource.creativecommons.org/community/write-a-blog-post/, we could reduce a couple of steps.

Describe the solution you'd like
Whenever Lektor builds its static files, it should create missing author or category files for new blog posts.

Describe alternatives you've considered
Keep doing it manually like we do now, but that's a pain.

Problem Description

Currently, there is no code syntax highlighting and code samples are harder to read. For example, look at the short GNU Bash snippet on NVMEe on Debian on AWS — Creative Commons on GitHub.

Solution Description

• Add lektor plugin: lektor/lektor-markdown-highlighter: support for syntax highlighting through Pygments to Lektor's markdown support (keep plugins sorted in .lektorproject)
• Document plugin in README.md#lektor-plugins
• Resolve any conflicts/issues and verify rendering

Two issues:

1. The footer should show up at the bottom of the viewport when the content doesn't go until the bottom but even for pages without much content, you need to scroll to see the footer.

Describe the bug

Back to top button is not working for the small screen(around 700px or less) once the user navigates to the footer of the page.

To Reproduce

Steps to reproduce the behaviour:

1. Visit any page which has Back to top button visible, scroll down to the footer of the page and try clicking on the Back to top button, it will get stuck.

Expected behavior

It must take back to top.

Screenshots

Desktop

• OS: Ubuntu Linux
• Browser : Firefox

Smartphone

• Device: One plus 7t
• OS: Android 10
• Browser : Google chrome

Additional context

After observing for a while whenever the text content of the footer gets in line with the Back to top button it stops working. And that is the reason it works smoothly on large screens as the text content of footer never comes in the way.

There are a lot of obvious style issues when the site is viewed on mobile. Please document and fix them.

Describe the bug

The project listed here has a broken link. Under sub-heading "The Problem", the third bullet point "It does not use Vocabulary, CC’s new web design system.", Vocabulary hyperlink gives error 404.

To Reproduce

Steps to reproduce the behavior:

1. Go to 'project ideas page'
2. Click on Vocabulary under sub-heading "The Problem", bullet point 3.
3. See error.

Expected behavior

The link should probably point to https://cc-vocabulary.netlify.com/?path=/story/vocabulary--welcome?

Desktop (please complete the following information)

• OS: Ubuntu 18.04
• Browser: Google Chrome
• Version 80.0.3987.122

The filter menu at project idea page mentions difficulty levels as Easy, Medium and Hard. On the other hand, the ideas mentioned are classified as having difficulty either Low, Medium or High. I am not sure if [Easy,Low] , [Hard, High] are to be treated separately. Otherwise, this might be a bug.

We show the author name in blog posts but there's no way to see all posts by an author. We should implement that feature and make the author's name clickable.

Describe the bug
Related to #63. I got started, and cloning the repo was successful, but the checkout failed. This are the errors:

error: unable to create file content/archives/old-tech-blog/ccrel-joining-man-and-machine-presenting-cute-dogs/2590707576_77cc7cf61e.jpg?v=0: Invalid argument
error: unable to create file content/archives/old-tech-blog/creative-commons-looks-out-at-copyright-20/2591423484_b9c00dc13f.jpg?v=0: Invalid argument
fatal: cannot create directory at 'content/archives/old-tech-blog/summer-of-code-converting-biomedical-text-mining-data-to-rdf-integrating-results-with-existing-neurocommons-rdf-data-generating-a-rdfa-based-web-interface-for-presentation`: Filename too long.
warning: Clone succeeded, but checkout failed.

The max file name length for NTFS is 260 characters.
To fix this, I will condense the file name to make it shorter, and submit a PR.

To Reproduce

1. Clone this repository
2. Attempt to git checkout -f HEAD
3. See error

Expected behavior
The checkout should be successful. The main thing preventing this is the fatal error concerning the file name being too long.

Desktop (please complete the following information):

• OS: Windows 10 1803; 17134.648
• GitHub Desktop v1.6.5 (Latest)

Additional context
Related to #63

We should add a donation entry point / link to Contributing Code — Creative Commons on GitHub.

Maybe we could match the nav styling of creativecommons.org?

Issue

Blog posts byline currently use US date format:

by Matt-Lee on Monday, December 15, 2014

Solution

The site should be updated to use use the same order as ISO date format:

by Matt-Lee on Monday, 2014 December 15

• Creative Commons likes standards
• Creative Commons has a global focus, not a USA focus

References

• dateformat | Documentation | Lektor Static Content Management System
• ISO 8601 - Wikipedia
• xkcd: ISO 8601

I'm submitting a...

• Feature request

Description:
There is some CSS in the /assets/ folder. We'd like to use modern best practices and move to the Sass extension language. We also want to build CSS from the Sass file(s) automatically during the Lektor build process.

Resources

• Sass documentation
• Lektor guide to using Webpack to build CSS from Sass

See #43 for context.

Pagination is currently unstyled and only shows the current page, this issue is to make the style blend in better and to show links to all pages on every page.

Is your feature request related to a problem? Please describe.
Recently in the cc-gsoc Slack channel, @kgodey provided some very useful information regarding mentor availability, and how n project ideas may be available, but there may only be enough mentors/ slots to support < n proposals. Additionally, she provided some information about proposal review criteria. She already added some of this information in #60, but I don't believe that what was added covers all of what could be useful to future participants.

Describe the solution you'd like
I believe that more available information is (in most cases) better, and I would have liked to have had this information when I started with GSoC. Because I believe that the addition of this information could help future GSoC participants, I would like to add more information regarding mentor/ slot availability to the Mentors section, and more information about the proposal review criteria to the Proposal review criteria section.

I would be happy to work with any maintainers to refine the language of the additions to be site-ready. Pending confirmation that this change is welcome, I will fork, and get to work!

Describe alternatives you've considered
I do not think there are any alternatives to just adding the information.

Additional context
Kriti's addition of proposal review criteria (PR #60)

These changes will be in ./content/gsoc-2019/contents.lr

Two recent threads in the cc-gsoc Slack channel: Thread 1 (started by Theo M.; "Does Google ultimately decide what proposals are accepted or is it entirely the organization's choice?"),
and Thread 2 (started by myself; a continutation of the replies in thread 1).

I'm submitting a...

• Bug

Description:
The styling for the active nav item looks fine when the nav is expanded (see blue box in screenshot)

When the nav is collapsed, the border beneath the active item occupies the entire width of the header.

Feel free to change the active link styling if desired. One way to fix it may be to use similar styling to the https://creativecommons.org website (see "Use & remix" nav styling in https://creativecommons.org/use-remix/).

Describe the bug

On vertical screens of a certain size, the text snaps to the left side of the screen and leaves a big margin on the right, making the text harder to read and the images much smaller.

To Reproduce

You can reproduce this by viewing the blog on a mobile phone or by changing the window size on your desktop.

Screenshots

Currently there's no easy way to get from CC Open Source to creativecommons.org, we should add a link to it in the main navigation.

Problem Description

On the GSoC project Ideas page, a visitor can select only one of the following seven categories to sort out project ideas of interest

• All Projects
• Difficulty: Easy
• Difficulty: Medium
• Difficulty: Hard
• Skill: JavaScript
• Skill: Python
• Skill: WordPress

https://opensource.creativecommons.org/gsoc-2019/project-ideas/difficulty-easy/

But Ideally, there are 2 categories there;

• Difficulty Level
• Skill/Tool of choice

Only the selection of one of them can be done at a time. A beginner in JavaScript can not select the Difficulty: Easy category and the Skill: JavaScript together.

Solution Description

A visitor to the page should be able to select 2 categories which should be a Difficulty Level and a Skill/Tool of choice so users can sort out project ideas with the technology of interest and appropriate difficulty level that matches the user's level of proficiency.

Currently, the authors page shows all authors associated with all blogs. Each blog should have its own authors list – the blog model was designed to support independent blogs so that we could also reuse it for a current CC tech blog. As part of this, we should also not hardcode the blog title in the author templates.

ruamel.yaml supports YAML 1.2 and its releases are less of a mess:

• Differences with PyYAML — Python YAML package documentation
• Rebase off ruamel? - many new valuable features · Issue #46 · yaml/pyyaml
• Releases · yaml/pyyaml

I don't know if dropping ruamel.yaml in is possible. It seems the only place 'yaml' occurs is in Pipfile.lock. Maybe it should be removed all together.

Describe the bug
Some link URLs to other blog posts are not linked to the correct URL.

To Reproduce
See https://creativecommons.github.io/tech-blog-archives/good-advice-for-gsoc-students/. The "already mentioned" link is redirecting to http://labs.creativecommons.org/2011/03/21/cc-gsoc-integration-is-the-word/ instead of /tech-blog-archives/cc-gsoc-integration-is-the-word/

Expected behavior
Links should point to the correct URL.

See #43 for context. This should be worked on after #49 since that PR adds the blog posts.

Assigning this to myself because I'm not sure which section is the best place yet.

Describe the bug

GitHub repository link for CC opensource website is not clickable on mobile devices and thus donot redirect to CC opensource website GitHub repo. And also the design can be changed a bit as it is almost unrecognisable as GitHub logo.

To Reproduce

Steps to reproduce the behavior:

1. Open the site in mobile.
2. Try clicking on the top left corner (github icon).
3. It doesn't responds to click.

Expected behavior

It must redirect to CC opensource website repository.

Screenshots

Smartphone (please complete the following information)

• Device: One plus 7T
• OS: Android 10
• Browser: Chrome
• Version (ex. 22)

Additional context

Design for small devices can be changed a bit as it is almost unrecognisable as GitHub logo.

Describe the bug
The text on some pages is not properly aligned when seen from mobile.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'community' tab on navbar
2. Click on 'any link' from dropdown
3. See the styling issue with 'jump to' list.

Expected behavior
Should be properly aligned with rest of page.

Screenshots

Smartphone (please complete the following information):

• Device: Vivo V9
• OS: Android 6
• Browser : Chrome

Description:
On clicking the back to top button, the user is directed to the first heading of the web page and not the footer, so if one has to choose another tab, they have to further scroll up manually.

Fix:
Change the back to top button to direct to the top of the web page and not the first heading.

Problem Description

Add the description content to be shown while sharing the link on Facebook and Twitter.

From the above image, you can see the description part is missing. Only the title and image are shown.

Solution Description

I have already added the image preview feature the only thing that is lacking is the description part that will be shown when any link will be shared.

Helping Hands

You can get the content part of a page/post and then first strip HTML tags to convert into plain text and then get the first 20 words or so to be used in the description part.
Some plugins that you can play with strip-html-tags and markdown-excerpt

Note

Please don't add new fields, use the one that are already implemented, read more about it here

Pagination design is not responsive in archive/old-tech-blog.

Can I work on this issue?

Hi -- just a suggestion: Blog post pages on the open source blog don't appear to be optimized well for Twitter and Facebook (etc.) to be able to fetch and display image and description previews. See attached screenshots

We (will once #51 is done) show categories belonging blog posts but there's no way to see all posts in a given category. We should implement that feature and make each category associated with a blog post clickable to see all posts in that category.