Skip to content
This repository has been archived by the owner on Jan 3, 2018. It is now read-only.

Added a Next Workflow on the git section pages #850

Closed
wants to merge 1 commit into from
Closed

Added a Next Workflow on the git section pages #850

wants to merge 1 commit into from

Conversation

olafleur
Copy link

I figured that it would be easier for the instructors to navigate in the workshop content if there was a Next page link at the bottom of each page.

I just did it for the git section pages. If you tell me that it's useful, I'll do it for every section.

Also, I don't know much about Jekyll, but :

  1. Is there a way to right align this without HTML? (If not, I guess that I'll do it with HTML)
  2. Maybe it would be worth it to add a previous link also, what do you think?
  3. Finally, if there's a way to automatically generate the link from the neighboorhod pages, that would be cool (so that if the title of the page change, the link would change automatically). But I don't know if it's feasible.

Tell me what you think !

@rgaiacs
Copy link

rgaiacs commented Nov 10, 2014

@olafleur Thanks for this. We try to address this before (#214 and #384) but with the spit of bc repo (#759) and migrate from Jekyll to Pandoc we are starting to think about it again (#835).

I just did it for the git section pages. If you tell me that it's useful, I'll do it for every section.

Could you add your suggestion on #835?

  1. Is there a way to right align this without HTML? (If not, I guess that I'll do it with HTML)

No.

  1. Maybe it would be worth it to add a previous link also, what do you think?

#835

  1. Finally, if there's a way to automatically generate the link from the neighboorhod pages, that would be cool (so that if the title of the page change, the link would change automatically). But I don't know if it's feasible.

I didn't find one way to do it with Jekyll (see #384) neither with Pandoc. Since the name of each topic file at our lessons has the pattern [0-9]{2}-.*\.md we can use one script to get the file name and pass it to Pandoc as a variable.

@olafleur
Copy link
Author

I'm not sure of which suggestion you're talking about.

#835 seems fairly complete to me (didn't see it, sorry about that).

I guess I'll look into Pandoc to see how it works. ;-)

Should we close this issue, then?

@rgaiacs
Copy link

rgaiacs commented Nov 11, 2014

Should we close this issue, then?

+1

@olafleur olafleur closed this Nov 11, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants