Hey Gang! I know that this hasn't been updated recently. But here is my issue.

I'd like to create a tutorial (that could become a course) using the course-in-a-box. I figure I'd like to get it running locally.

When following the instructions for Local from the readme,
I run this code:

nsl@LAPTOP: ~/ad-ipsum/p2pu-LMS-site$ docker run -i -t --rm -u 1000:1000 -p 4000:4000 -v `pwd`:/opt/app -v `pwd`/.bundler/:/opt/bundler -e BUNDLE_PATH=~/opt/bundler -w /opt/app ruby:2.7 bash -c "bundle install && bundle exec jekyll serve --watch -H 0.0.0.0"

I get this error:
/ is not writable.
Bundler will use /tmp/bundler20231120-7-lprlp17' as your home directory temporarily. There was an error while trying to write to /home/nsl/opt/bundler/ruby/2.7.0`. It is likely that you need to grant write
permissions for that path.

Any help would be great!

• Add H2TAR and We Are AI to courses we love
• Update course creation guide to point to handbook

On the p2pu tutorial session;

Who is the course for & what will they learn?

Will they be building something during the course. Put this basic information on the front page of the course to give a short overview of what to expect. To update the info on the front page, go to the file:

https://github.com/ebonsi/course-in-a-box/blob/gh-pages/index.markdown

It is leading to:

404: Page not found

I tried to change the url following the previous url semantics but that did not help either.
https://github.com/ebonsi/course-in-a-box/edit/gh-pages/index.markdown

Could anyone that is following this development chime on this issue?

Is this page has been deleted?

Thanks!

Nav items added directly to /includes/navigation need to be styled in same way as modules

The instructions tells a user how to add a item to the top navigation menu, but if a user adds a page as part of the course (as apposed to the page being external) the topnav won't correctly display the styling for the page being active when a user visits the page.

A possible solution is to add a section for extra topnav items to _data/course.yml, eg.

topnav:
- url: /facilitate
  title: Facilitate

We would need to update both the instructions and the implementation for this.

would it be possible to add a feature for adding quizzes/ tests?

<link rel="apple-touch-icon" href="/img/apple-touch-icon.png">

Uses this image:

which seems like it comes from html5 bootstrap

An enhancement idea: supporting multilingual pages. Perhaps via a _posts.en and _posts.fr system or via encoding it in the post name somehow.

• Review google advice on changing domains and moz guide to ensure all the needed steps are here
• Drop TTL for howto.p2pu.org to 5 min and wait a day for DNS to propagate
• Update CNAME
• Create new DNS record for course-in-a-box.p2pu.org
• Update DNS record for howto.p2pu.org
• 301 redirect all pages on howto.p2pu.org/AAA to course-in-a-box.org/AAA - will need to host this on a server
• Update google analytics
• Submit a change of address in google search console
• Restore TTL to default value
• Verify site move success

The BioSchemas Training Material profile is an extension of Schema.Org markup to support annotating training material (in the life sciences). This enhances the FAIR-ness of training material by adding machine-readable markup to pages.

It is fairly straightforward to add this markup to Github pages sites. In my experiments adding

{% if page.bioschemas %}
<script type="application/ld+json">
     {{ page.bioschemas | jsonify }}
 </script>  
{% endif %}

to _layouts/course_page.html was enough. Before making a PR, I'd like to hear if this addition is on interested to the broader Course-In-A-Box community.

See https://support.google.com/webmasters/answer/183668

• Use latest theme css
• Update HTML to bootstrap 4

So... if i imagine people wanting to fork my course, before during or after the course, to control their own subcommunity of the same course... is there anyway to autogenerate a list of course-forks so that people could browse what other folks were doing with the course?

Currently modules are implied by the name of the folder they are in. That leads to problems with URLs or titles once the module name is more than a single word ie. "Getting Started".

To solve this, we can decouple the text used for display from the slug used for the URL for modules as done for the how to talk about race course. See the changeset for details.

See https://ogp.me/

https://p2pu.github.io/learning-about-learning-circles/

• Navbar: Deleted P2PU logo from navbar (it was buggy on small screens), left justified menu items
• Jumbotron: Changed image size, vertically centered text, constrained subtitle text to width of title, added text shadow and background color to make text more legible.
• Footer: Updated footer.
• Modules: Added styling to the default button and blockquote CSS.

https://course-in-a-box.p2pu.org/modules/content/markdown-and-media/

• Ability to set jumbotron_image behavior as cover/scale-to-fit or tile
• Ability to manually customize fill with hex color input (rather than a tinted transparent image)

Hey @ercchy wanted to file this heard a few folks say they didn't know how to get started from the splash page.

@dirkcuys should we put "start the course" button and flick people to "start here"?

I noticed that there are new versions of several of the gems listed in Gemfile.lock so I went through and updated the versions on a fork I created. If this is helpful (and I made the changes correctly), I'm happy to create a pull request.

I'm still pretty new to Jekyll and GitHub so I'm not sure the best way to do this – feel free to delete the issue if it isn't welcome or necessary.

A few issues related to submodule navigation at the bottom of each page:

1. At certain screen widths, the names of the submodules appear as a single string of text

2. As screen size expands, navigation buttons jump between two lines and one lines. In the following example, the nav jumps to 1 line at 713 pixels wide, goes back to 2 lines at 768, back to 1 line at 952, back to 2 lines at 1105, and then back to 1 at 1406.

3. On mobile, the navigation should probably always be left justified (previous module above next module), rather than using this indentation.