GithubHelp home page GithubHelp logo

carpentries-incubator / jekyll-pages-novice Goto Github PK

View Code? Open in Web Editor NEW
16.0 7.0 21.0 30.39 MB

Building Websites with Jekyll & GitHub Pages.

Home Page: https://carpentries-incubator.github.io/jekyll-pages-novice/

License: Other

Ruby 0.52% Makefile 3.93% R 4.25% Shell 0.38% Python 36.38% HTML 42.22% SCSS 7.57% CSS 3.41% JavaScript 1.33%
lesson jekyll carpentries-incubator english github-pages beta

jekyll-pages-novice's Introduction

Building Websites with Jekyll and GitHub Pages

Gitpod ready-to-code DOI

This lesson teaches the basics of creating, configuring, and updating a static website with GitHub Pages and Jekyll. The lesson is aimed at researchers and research software engineers who understand what a variable is and are familiar with the GitHub web interface. Read more about the target audience and learning objectives on the lesson homepage.

Development Status

The lesson is currently in a beta state, meaning that it has been tested a few times at workshops and is ready to be taught by others. However, the lesson is not currently being developed nor is actively maintained.

Maintainer(s)

Past maintainers of this lesson are:

Citation

See CITATION.cff for citation information, including a list of authors. (Read more about the Citation File Format and how to use it.)

Contact

Please get in touch with the original maintainers of the lesson with any questions.

jekyll-pages-novice's People

Contributors

abbycabs avatar aleathwick avatar anenadic avatar bkamapantula avatar elshaek avatar emmyft avatar erinbecker avatar fmichonneau avatar gvwilson avatar joaorodrigues avatar jsta avatar juliankarlbauer avatar katrinleinweber avatar mawds avatar maxim-belkin avatar mr-c avatar neon-ninja avatar orchid00 avatar pbanaszkiewicz avatar raynamharris avatar rgaiacs avatar sparrow0hawk avatar sstevens2 avatar tkphd avatar tobyhodges avatar tracykteal avatar twitwi avatar unode avatar wclose avatar zkamvar avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

jekyll-pages-novice's Issues

Write learner profiles

the lesson needs some learner profiles, to describe its target audience. These should go into a new file at files/audience.md.

Instructions for local builds

We need an Extras page describing steps required to build and serve a site locally, for Windows (if possible?), MacOS, and Linux.

Use Title Case for Everything

We should be consistent on styling, and decided at the October lesson sprint to adopt Proper Title Casing for section/challenge/solution/callout/everything headings. At some stage, it would be great if someone could do a thorough sweep of all our lesson content to enforce consistency.

For all other style considerations, we defer to The Carpentries lesson style guide

Fix capitalisation on learning objectives in all episodes.

I still think of learning objectives as finishing the sentence "After following this episode, learners will be able to..." which is why I have the habit of writing them with the first word starting in lowercase. But this doesn't fit with the lesson template and #60 has forced me to face up to the reality that they should start with an uppercase letter to remain consistent with the Questions and Key Points ๐Ÿ˜‘ This needs to be fixed in all episodes.

Readme.md to index.md coordination?

In Review of #28, it came up that maybe we should have them learn Markdown by working in the README.md and then changing that to the index.md in the beginning of the github episode. Maybe something to discuss and coordinate at the next sprint?

plan material for GitHub Pages episode

We can use this Issue as a place for discussion around the GitHub Pages episode. Next steps might include:

  • draft concept map for the episode
  • review learning objective(s) & bullet point plan
  • design exercise(s) to fit the episode learning objective(s)

Create an end-of-the-lesson episode

To include, for example:

  • a short summary
  • a curated diagram of a real life jekyll website (see #78)
  • "where to go from here" pointers to further resources

Split up 05-starting-jekyll?

The Starting with Jekyll episode is probably going to be too long. What's the best point to split it? Perhaps put includes material into its own episode?

Expand README.md

"Lesson material" is not very descriptive! The README should be updated to include:

  • more information about the lesson
  • its high-level objectives
  • a link to the HackMD & Slack channel
  • the planned schedule for development and sprints

and anything else you think would be useful for potential contributors.

I'll take care of this soon (at the 6 October sprint at the latest) but, if anyone else wants to take on some/all of the above, please go ahead!

Exercise: themes

in 06-templates.md

need an exercise testing knowledge of finding/using pre-existing (remote?) themes. This is relevant to #11

Plan material for Jekyll basics episode

We can use this Issue as a place for discussion around the Starting with Jekyll episode. Next steps might include:

  • draft concept map for the episode
  • review learning objective(s) & bullet point plan
  • design exercise(s) to fit the episode learning objective(s)

Arrays & Collections episode

Here's my suggested outline for a final episode on arrays, loops, and collections:

  • arrays in Jekyll: using the team_members example from #29, add an array variable to _config.yml and use a loop to list team members on a (new) team.md page
  • use the where filter to pull out a team member with a particular job title. (Might need to combine this with another filter e.g. first - scrap this example if it gets too complicated...)
  • with motivation to list blog posts automatically, configure a posts collection in config.yml and relocate the blog posts to appear in that collection. Add a new blog.md page to list posts sorted by publication_date.

Notes reference

The notes for the sprints to work on these lessons can be found here.

When sprint is finished, maybe we should move some of the motivation and info to instructor notes?

Test the materials ahead of Pilot 1 by 9th November

People involved:

  • Anne
  • Julian
  • Renato

Things to do:

  • Review episodes from the beginning through the end of the Filters episode (do not worry about the last episode on Loops)
  • File issues you discover along the way (think SMART!)
  • Check you name off the above list once finished and make a comment on this issue

Plan material for templates episode

We can use this Issue as a place for discussion around the Page Templates episode. Next steps might include:

  • draft concept map for the episode
  • review learning objective(s) & bullet point plan
  • design exercise(s) to fit the episode learning objective(s)

Add the banner image to the example repository

Instead of loading the image from this repository, we should include the image in the example repository the learners are constructing as they work through the lesson. We can ask them to download it from this repo and upload it to theirs. Just need to add in some instructions for this at the start of the Includes episode...

Plan material for GitLab pages episode

We can use this Issue as a place for discussion around the GitLab Pages episode. Next steps might include:

  • draft concept map for the episode
  • review learning objective(s) & bullet point plan
  • design exercise(s) to fit the episode learning objective(s)

Note: if focusing on GitHub Pages for now, all other episodes should take precedence over this one...

Draft_02_markdown

This is a dummy issue mimicking an empty Gitlab-merge-request and serving as a place to talk.

Improve Screenshot Sizes or Level of Perception

Some screenshots and the font sizes they contain are very large compared to the font of the text of the instructions outside the images.

Adjusting the size of the screenshots may help to increase readability and balance the level of perception of instruction and screenshot. Putting a frame / box around screenshots may be an alternative way of dealing with this.

Example

Exercise: `include`

in 05-starting-jekyll.md

need an exercise to test knowledge of _includes and {% include ... %}

Change episode numbers

At the moment we are missing episode 04 - so once we settle on episodes we should change the numbers to reflect this.

Exercise: adjusting site config

in 05-starting-jekyll.md:

need an exercise to test understanding of how site config works from, _config.yml. This exercise (or another, separate one) should also include working with global variables (i.e. site.variable_name where variable_name was set in _config.yml).

Writing basic HTML TODO

A callout in the introduction with a TODO:

>>> Writing Basic HTML
TODO: brief overview of tags, including strong, heading, and link.
Fill-in-the-blanks exercise to write HTML to recreate some example text.

Plan material for Filters episode

We can use this Issue as a place for discussion around the Working with Filters episode. Next steps might include:

  • draft concept map for the episode
  • write learning objective(s)
  • review bullet point plan
  • design exercise(s) to fit the episode learning objective(s)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.