First of all, I really like this idea to encourage people to contribute to open source.

I saw that it was mentioned to make this site a Jekyll site.

So I thought I could create a small pull request that does this.

It could probably split up the files even more, but at least it's a start :)

• Move the outer tags to default.html-layout.
• Move the footer content to a included file.
• Add some variables to _config.yml.

If something is unclear I can explain more :)

I've just put together http-crawler, a simple library for crawling websites with Python. It does enough to meet my own immediate needs, but there are a handful of enhancements that could make it more useful. I've listed these on the issue tracker.

I'd be delighted if somebody who was new to Open Source would like to take these on, and I'd be happy to provide any mentoring or support required.

This is not high priority, our CSS is unlikely to be big. This is just an opportunity for someone to try and get css minification working :)

1. Investigate and learn about CSS minification
2. Incorporate CSS minification through the use of a build script (such as through the use of NPM)

This might be a bit over thinking it but here it goes.

At the moment we can't just publish a list of github issues with labels since they might not have great instructions so I was thinking we could automate the review.

1. Have a format that can be parsed that contains the ingredients needed for a good first issue
2. Build a service (think Travis etc) that can watch a repo's issues
3. Expose first timer issues in one place.

Let's get a logo! Branding! Magic! For use on Twitter and other websites using a display picture (like GitHub)

I do not expect high quality, vectored, rastered, magical creations. Just have fun. If you are able to incorporate this colour into it, that'd be magical! #9266CC (purple).

Any time is appreciated, you are wonderful.

I've created the blog list page and the blog posts page.

The styling on the individual posts could use some love.

My first ever PR on Your First PR, so meta.

Replace all occurrences of 'allowence' with 'allowance'. Fantastic easy for 1st pull request. Valentina is written in C++ and uses Qt 5.7+ as the development environment. Qt makes building, testing, & debugging easy. We have supportive developers and community for all of your questions. Join our forum and introduce yourself! http://forum.valentina-project.org The repo is in Bitbucket and uses Mercurial (hg). Issue #616: https://bitbucket.org/dismine/valentina/issues/616/code-typo-allow-e-nce-instead-of-allow-a

yourfirstpr.github.io

Thank you so much for opening a pull request! :smiley:

Please provide the following information where possible to help the pull request reviewer merge your PR quicker!

Relevant Project Issue Numbers :hash:

Add any related issue numbers from the GitHub project. Append the # symbol before issue numbers.

none

Involved Project Members :bust_in_silhouette:

Tag any GitHub usernames involved or directly responsible for reviewing the proposed changes. Append the @ symbol before usernames.

@robjloranger

An Explanation of Your Changes :speech_balloon:

Include blog directory in post URLs to get permalinks in the form of yourfirstpr.github.io/blog/new-blog.html.

Any Screenshots of Your Changes :camera:

Hi,

I've forked the repo and made a few commits revising the landing page and visuals. This is a brilliant initiative, great that the Code of Conduct and blog are set up too :)

Hope these edits are okay!

• Pulled navigation out of individual pages, into _includes/header.html
• 'active' element ID for navigation is set dynamically by page path
• - maybe this should be a class?
• Page titles are pulled from page front matter
• - title: page specific title
• - the Showcasing good starter issues portion has been added to the index front matter so it is present on the home page
• Meta tag for description is set via _config.yml and pulled into the header of each page

• Pulled navigation out of individual pages, into _includes/header.html
• 'active' element ID for navigation is set dynamically by page path
• - maybe this should be a class?
• Page titles are pulled from page front matter
• - title: page specific title
• - the Showcasing good starter issues portion has been added to the index front matter so it is present on the home page
• Meta tag for description is set via _config.yml and pulled into the header of each page

yourfirstpr.github.io

Thank you so much for opening a pull request! :smiley:

Please provide the following information where possible to help the pull request reviewer merge your PR quicker!

Relevant Project Issue Numbers :hash:

Add any related issue numbers from the GitHub project. Append the # symbol before issue numbers.

e.g. #58

Involved Project Members :bust_in_silhouette:

Tag any GitHub usernames involved or directly responsible for reviewing the proposed changes. Append the @ symbol before usernames.

e.g @varjmes

An Explanation of Your Changes :speech_balloon:

Your explanation goes here!

Any Screenshots of Your Changes :camera:

Your screenshots go here! Use Markdown Syntax to embed images.

yourfirstpr.github.io

Thank you so much for opening a pull request! :smiley:

Please provide the following information where possible to help the pull request reviewer merge your PR quicker!

Relevant Project Issue Numbers :hash:

Add any related issue numbers from the GitHub project. Append the # symbol before issue numbers.

e.g. #58

Involved Project Members :bust_in_silhouette:

Tag any GitHub usernames involved or directly responsible for reviewing the proposed changes. Append the @ symbol before usernames.

e.g @varjmes

An Explanation of Your Changes :speech_balloon:

Your explanation goes here!

Any Screenshots of Your Changes :camera:

Your screenshots go here! Use Markdown Syntax to embed images.

yourfirstpr.github.io

Thank you so much for opening a pull request! :smiley:

Please provide the following information where possible to help the pull request reviewer merge your PR quicker!

Relevant Project Issue Numbers :hash:

Add any related issue numbers from the GitHub project. Append the # symbol before issue numbers.

e.g. #58

Involved Project Members :bust_in_silhouette:

Tag any GitHub usernames involved or directly responsible for reviewing the proposed changes. Append the @ symbol before usernames.

e.g @varjmes

An Explanation of Your Changes :speech_balloon:

Your explanation goes here!

Any Screenshots of Your Changes :camera:

Your screenshots go here! Use Markdown Syntax to embed images.