Skip to content

Conversation

@rossmounce
Copy link

Clicked on CFP link & got 404.
Changed to what is hopefully the correct(?) link

Clicked on CFP link & got 404.
Changed to what is hopefully the correct(?) link
@brocktopus
Copy link
Contributor

Just to be sure: the html link was broken? http://push.cwcon.org/cfp.html ?

@rossmounce
Copy link
Author

The link is fine when this is all implemented on http://push.cwcon.org but, I (and perhaps many others) currently first arrive to the github rather than http://push.cwcon.org . On the github (specifically, https://github.com/cwcon/push/blob/master/index.md ) the link to CFP 404's.

I think I understand the issue now, and perhaps I'm wrong but is there perhaps a way to make the link both resolve on github & in the real implementation perhaps?

@sellout
Copy link

sellout commented Mar 24, 2013

One option would be to use an absolute URL. A better one (that might not work without poking the Github devs a bit) is to use a Wiki-style link, [[CFP]], and have the translator expand it to .html or .md as appropriate.

@karlstolley
Copy link
Collaborator

The .md link is definitely out, because that would in turn break on the actual site.

Here are two other possibilities:

  1. Changing the default branch shown on GitHub from master to gh-pages, so that the compiled HTML source (rather than the GitHub-rendered Markdown) is shown at https://github.com/cwcon/push/ (what's currently at https://github.com/cwcon/push/tree/gh-pages would display instead, probably with some more welcoming edits to the current README.md found there).
  2. Add a line to the YAML of each and every Markdown source file that points to the live site and advises people not to follow links. That's a wonkier solution, and the YAML is rendered as Markdown on GitHub anyway. But I'm posting this idea in hopes that it might trigger others into other, more useful lines of thinking.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants