pifafu’s tiny site

Example

2022-07-11T00:00:00+00:00

Cool. You’ll find this post in your _posts directory. Go ahead and edit it and re-build the site to see your changes. You can rebuild the site in many different ways, but the most common way is to run jekyll serve, which launches a web server and auto-regenerates your site when a file is updated.

Jekyll requires blog post files to be named according to the following format:

YEAR-MONTH-DAY-title.MARKUP

Where YEAR is a four-digit number, MONTH and DAY are both two-digit numbers, and MARKUP is the file extension representing the format used in the file. After that, include the necessary front matter. Take a look at the source for this post to get an idea about how it works.

Jekyll also offers powerful support for code snippets:

def print_hi(name)
  puts "Hi, #{name}"
end
print_hi('Tom')
#=> prints 'Hi, Tom' to STDOUT.

Check out the Jekyll docs for more info on how to get the most out of Jekyll. File all bugs/feature requests at Jekyll’s GitHub repo. If you have questions, you can ask them on Jekyll Talk.

Identity

2022-06-21T03:14:59+00:00

Cool.

You’ll find this post in your _posts directory. Go ahead and edit it and re-build the site to see your changes. You can rebuild the site in many different ways, but the most common way is to run jekyll serve, which launches a web server and auto-regenerates your site when a file is updated.

Jekyll requires blog post files to be named according to the following format:

YEAR-MONTH-DAY-title.MARKUP

Jekyll also offers powerful support for code snippets:

def print_hi(name)
  puts "Hi, #{name}"
end
print_hi('Tom')
#=> prints 'Hi, Tom' to STDOUT.

Check out the Jekyll docs for more info on how to get the most out of Jekyll. File all bugs/feature requests at Jekyll’s GitHub repo. If you have questions, you can ask them on Jekyll Talk.

Profile Readme

2022-06-21T03:14:59+00:00

READMEs provide a canvas for developers to curate their developer identity.

Before this ship, user profiles were largely structured around high level elements like pinned repositories and low level metrics like daily contributions or summaries of activity by month. Profile READMEs provide GitHub users expansive flexibility in representing themselves and their work.

Before this ship, GitHub user profiles were largely structured by elements that provided proof of contribution, such as pinned repositories and contribution graph. It was difficult for users to curate a more holistic view of their developer identity; the diversity and richness of developer work was thusly somewhat flattened by the profile.

Instead of introducing more modular components to the profile to surface different kinds of information, we explored adding READMEs to profiles. READMEs were a compelling addition due to their ubiquity on GitHub — in addition to providing a canvas for writing and expression, they would be a familiar pattern.

READMEs were already ubiquitous on repositories and provided a canvas where users got to decide what information was shared and how it was designed. Since READMEs already served as customizable cover page for repositories, they offered a reusable and extensible solution.

Profile READMEs will provide GitHub users more flexibility and space in sharing who they are on their profile page. It will allow users to fill in the gaps on their current GitHub profiles, which do help users elevate their popular repositories and contribution activity, but don’t help users share a narrative or allow for much creative expression. We’ve seen READMEs work very well for repositories, and we want to extend this capability to our users:

:thinking: What do our users think?

We first asked users what they wanted to share about themselves, and then saw an overwhelmingly positive response to @mikekavouras’s initial spike of this feature when it was shared out on Twitter (the tweet went viral almost immediately, having reached almost 1 million impressions so far).

On top of requesting to be added to the feature, many users thought that, with this README, their profile will get closer to being a résumé. We can interpret this to mean that many users feel that the current GitHub profile is not an adequate representation of their developer experience and history and would like it to be.