Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

move the "pages" guides back in to guides #323

Closed
5 tasks done
superbunker opened this issue May 20, 2021 · 5 comments
Closed
5 tasks done

move the "pages" guides back in to guides #323

superbunker opened this issue May 20, 2021 · 5 comments
Assignees
Labels
documentation Improvements or additions to documentation p-feature: guides role: back end

Comments

@superbunker
Copy link
Contributor

superbunker commented May 20, 2021

Overview

We're now only showing a few (4) guides on the home page, so we won't be double-linking the landing-page guides. So, take the guides currently in the "pages" directory and re-add them to the "guides" directory

Action Items

Resources/Instructions

  • creator_overview.md
  • start_building.md
  • start_contributing.md
  • submit_idea.md
  • using_an_automation.md — just placeholder text right now
@superbunker superbunker added documentation Improvements or additions to documentation role: back end p-feature: guides labels May 20, 2021
@superbunker superbunker self-assigned this May 20, 2021
@superbunker
Copy link
Contributor Author

The syntax for the links references them in numerical order by alphabetical filename:
{{ site.pages[4].url | relative_url }}

Is there a reason this would be preferable to linking the filename directly? It seems that if we add new guides to the directory, the numbered order would change

@superbunker
Copy link
Contributor Author

superbunker commented Jul 17, 2021

path for relative links across collections: /Website/guides/filename.html

NOTE: When making relative links in gh-pages, the links will be wrong in the md file (“blob/gh-pages”) because jekyll hasn’t processed them yet, so they're relative to the repo, not the site. Which means that as far as I can tell, relative links can’t be tested in the code — only on the live post-jekyll page.

Deleting all the rabbit-hole mapping it took for me to finally realize this

@superbunker
Copy link
Contributor Author

links on the home page and in the guides have been changed

@superbunker
Copy link
Contributor Author

Added big link to the actual guides as a last warning.
Give it anther week and the pages directory can go.

@superbunker
Copy link
Contributor Author

DONE

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation p-feature: guides role: back end
Development

No branches or pull requests

1 participant