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
Standardize footer of reports #4300
Comments
Does it make sense to extend it to all reports ? For the standalone HTML pages, I could see the need, but would you also add it e.g., to a jupyter cell output of a NiftiMasker report ? In the latter case, I don't think we'd want a footer. |
Can you tell me more about why you'd think it'd be an issue if the report in that cell output had a footer? |
The standalone HTML reports were designed to be distributed independently, but the within-jupyter calls will be distributed within a notebook (by definition) that will also contain the originating code. So, in the case of standalone pages, the footer will help to keep provenance --- which is great, I think ! But in the within-jupyter case, it's at best redundant and at worst distracting for those working in a notebook. |
OK I just checked a couple of reports in a notebook and there would some fixing to do (will open a separate issue) but I'd rather get to this once:
|
To check how reports look (as of #4295) I created this notebook. Apparently the images cannot be viewed in the github file browser so it needs to be downloaded to view them. For this discussion: More complicated but could maybe look on how to hide the footer in notebooks only but not sure how to best do this (maybe some css magic). |
Related to improving how reports looks in notebooks:
|
When I download the nb I can't see the report... |
Hum... I must have messed something. Will check tomorrow. |
No idea. These reports were probably a bit minimalist at the origin, hence a narrow layout would be OK. |
The GLM reports mention Nilearn and links to the repo.
This should be extended to all reports
The text was updated successfully, but these errors were encountered: