-
Notifications
You must be signed in to change notification settings - Fork 0
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 osgi.enroute.site files into this working repo #1
Comments
First matter is structure. It's clear Peter wanted a |
|
Finding pathing problems. Using {{ site.baseurl }} is the remedy or could remove leading slashes. Things seem to work ok by just removing the leading slashes. If things go loopy on migration, we can add the variable. Edit: No no. GitHub needs {{ site.baseurl }} for their build. |
commenting out unused footer links until they have a purpose |
Ok. Most pathing issues are addressed |
Well, I think the migration is complete. Whether or not it will be used is in question. Either way. |
Rough migration is indeed complete. Issues for the migration should be opened individually. |
The desire is to have the site build being handled by GitHub instead of Travis. Maybe the result will be a cloneable repo. Alternatively, maybe all we will get is enough understanding of the configuration problem to fix the original. Hard to tell from here.
The text was updated successfully, but these errors were encountered: