-
Notifications
You must be signed in to change notification settings - Fork 38
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
Move2lite #86
Move2lite #86
Conversation
…s and slim down download
@darribas I am in the process of reviewing this PR at the moment, building locally, etc. Steps 1, 2, and 4 of the Build Process run without issue but with the If we are considering doing the merge without addressing the cell failures, then I would say this PR is good to go, with one minor addition: Can we include the new version of the PySAL logo? Either the logo with text in the root, the logo with text outside the mindmap (1 line), or the logo with text outside the mindmap (2 lines). Also, how about including the new version of the favicon?
all
Plus many more... |
See pysal/pysal.github.io#145 and pysal/pysal.github.io#146 after adding the new logo here. |
Fantastic @jGaboardi, excellent idea, I'll add the new logos to this PR I think it makes sense. As for the running, my view is let's merge this, which improves on the current state that's live on the notebooks website, and then let's fix those. Several of those will probably need to be changed not in this repo but in the original sources (ie. each package) which will probably take a bit longer. I think there's value in having the book up to date online in the meantime. |
@darribas This sounds reasonable. Once the new logo/favicon are in the PR, let's merge. EDIT 1: I propose we use the logo with text outside the mindmap (2 lines) since the PySAL acronym is not defined anywhere in the EDIT 2: I just noticed the following comment regarding the logo in
So I will push up the "traditional" mindmap logo with "PySAL" inside. |
@darribas I was having trouble pushing commits directly to this PR, so I opened a PR on this branch in your fork. |
OK, I worked out the issue I was having and was able to push my (updated) commits directly here.
|
probably something botched on my end, but its not pulling the docs folder so the build is failing for me |
I've pushed the new logo/favicon to the source, need to rebuild |
OK @jGaboardi this is good to go afaik! @knaaptime I've updated the |
@darribas I accidentally merged... Shall I revert or leave as is? |
That makes the new build live at: http://pysal.org/notebooks I think it looks good! There're things to improve on, but this is better than what we had, so I'd leave it? |
This brings updated code and a new build of the notebooks based on 2.2. I think it's ready to merge although it has features that need to be ironed out/further tested:
In any case, I recommend this is merged because it improves notably what's live now at pysal.org/notebooks