-
Notifications
You must be signed in to change notification settings - Fork 38
Local environment points to remote resources #85
Comments
Have a look here: interledger.github.io/_includes/head.html Lines 1 to 5 in 9724d83
Commenting out the first line solves the issue. Is this needed? |
It is for now but maybe we can come up with a better solution? The content of github.com/interledger/rfcs is rendered at https://interledger.org/rfcs and to make that work we need the URL base. If you can propose a change to the publish script in the rfcs repo that would publish into a folder of interledger.github.io instead that might solve the issue? |
@adrianhopebailie Would you be interested in seeing a new website layout (including refreshed stack, |
Sure, the website hasn't changed for a long time and we probably need to think about better information organisation now that we have so much to consume. We probably need a better "overview" page that visually puts the pieces together and links to the appropriate RFCs. This feels like quite a big project but if we have a willing group to work on it I'd be up for co-ordinating. I'm sure @emschwartz would be keen to help too. |
That's great! Along with the RFCs, I'm wondering if you guys have plan for developer docs, sort of like this: https://plaid.com/docs/#overview Also having official Sourcegraph support for all the repos in interledger-js would make things so much easier in terms of navigating code, how things connect, etc. |
I tried making a small change to the website in terms of styling to improve readability, but I noticed none of my CSS changes were showing up in the local jekyll staging. Culprit is that all the resources are basically remote pointing to Interledger.org. Any ideas why it's configured this way? Is there some base URL being applied somewhere that's messing with all the links?
The text was updated successfully, but these errors were encountered: