-
Notifications
You must be signed in to change notification settings - Fork 5
Add website #134
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
Add website #134
Conversation
Ready for Review |
Looking nice, thanks @richarddushime |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is looking good, thanks @richarddushime. I've left some comments, but at this stage a few high-level comments:
- Could you use the same theme and tooling etc as that is inside the cookiecutter template? One of the main aims of this documentation site is to show potential users what their own docs would look like.
- Could you use markdown rather than rst? In all our other websites we use md, so this will help maintainance considerably
A few small things:
- Could you remove the "give us a star" button?
- On my browser at least, the search bar looks a bit weird, like a box in a box in a box!
- There seems to be links to an unrelated datascience cookiecutter project
I am Sorry , I actually made a confusion with the cookier-cutter datascience In my mind I thought it was the same as this and I had to link back to it I will fix this ASAP |
Co-authored-by: Adam Tyson <code@adamltyson.com>
Co-authored-by: Adam Tyson <code@adamltyson.com>
Hi @adamltyson |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is looking nice, thanks @richarddushime. I've left a couple of suggestions.
Currently it's still a linear list of information, I wonder if there are ways to make it easier to navigate and maybe look nice too? The movement website is a nice example:
https://movement.neuroinformatics.dev/
Hi @adamltyson I worked on the layout based on the requested changes you made, Note> The navbar can also be removed if there is not much things to put there For the link back to the main site, I included a logo in the footer section I also did not add the version to the navbar with the project title, like it is done on the Movement website Thanks Attached is the screenshot |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @richarddushime, this is looking much better. I've left quite a few comments, but they're mostly very minor. I haven't checked all the content, but that's on us to keep up to date.
One more thing, would you be able to reduce the readme to the bear minimum? Idealy we would only maintain the docs in one place (which will soon become this website).
Co-authored-by: Adam Tyson <code@adamltyson.com>
Co-authored-by: Adam Tyson <code@adamltyson.com>
Co-authored-by: Adam Tyson <code@adamltyson.com>
Co-authored-by: Adam Tyson <code@adamltyson.com>
Co-authored-by: Adam Tyson <code@adamltyson.com>
Co-authored-by: Adam Tyson <code@adamltyson.com>
Co-authored-by: Adam Tyson <code@adamltyson.com>
for more information, see https://pre-commit.ci
Co-authored-by: Adam Tyson <code@adamltyson.com>
Co-authored-by: Adam Tyson <code@adamltyson.com>
Co-authored-by: Adam Tyson <code@adamltyson.com>
Co-authored-by: Adam Tyson <code@adamltyson.com>
Thanks Additionnaly |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is basically done now. I've suggested a few small changes, but we will go through the content ourselves later on and edit.
Re the navbar, ideally the logo would stay. I only say this because there are lots of cookiecutter templats for Python. This isn't intended to be the main one. It's eseentially an internal template that we share with others.
To simplify the navbar, we could probably just get rid of the version number. We don't version this template properly anyway.
Lastly, could you look into why the CI is failing?
Co-authored-by: Adam Tyson <code@adamltyson.com>
Co-authored-by: Adam Tyson <code@adamltyson.com>
Co-authored-by: Adam Tyson <code@adamltyson.com>
Co-authored-by: Adam Tyson <code@adamltyson.com>
Thank you very Much Hope this time it will pass About Pre-commit , Locally its passing well , not sure why its now refusing to pass |
Thanks @richarddushime. I will take a look as soon as I can. I've updated the PR title again, would you mind not changing it back? |
Hi @richarddushime it looks like the CI is still not passing. One of the issues is with the linkcheck. You may need to double check the links, and any that are still reporting issues (even though you've manually verified them), may need to be ignored For an example, see the BrainGlobe docs: |
Sure, I actually had not realised that you renamed it and I thought I was in a wrong PR |
I think there was an issue with a change in main failing the linting. Have updated. |
Finaly I was now going line per line and viewing even the NIU actions repo 👍 Thank you |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks again @richarddushime!
The actions seem to be running properly, but they aren't creating the gh-pages branch as they should, and so the website isn't deployed. |
let me look into this |
Don't worry, I sorted it on our side. Website is live 🎉 https://python-cookiecutter.neuroinformatics.dev/ |
Amazing |
Before submitting a pull request (PR), please read the contributing guide.
Please fill out as much of this template as you can, but if you have any problems or questions, just leave a comment and we will help out :)
Description
What is this PR
Improving the documentation of cookie-cutter using sphnix
Why is this PR needed?
What does this PR do?
References
#58
How has this PR been tested?
I tested this by Running locally and made sure all is working as Expected.
Is this a breaking change?
No
If this PR breaks any existing functionality, please explain how and why.
Does this PR require an update to the documentation?
yes
If any features have changed, or have been added. Please explain how the
documentation has been updated.
Inprogresss
Checklist: