-
Notifications
You must be signed in to change notification settings - Fork 20
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
Rendering suggestions #205
Conversation
Here is a draft blurb for the "Time Domain" page: Many fields in astronomy use the time variability to understand physical processes. Large datasets combined with time domain studies are becoming increasingly available to astronomers (ZTF, WISE, Rubin, etc.,). We show here two demo notebooks at the intersection of big data and time domain astronomy. The first notebook automatedly generates light curves from NASA and non-NASA archival sources in an efficient manner allowing this to be run on big data samples. The second takes that a light curve sample and runs machine learning classifiers on it. |
More suggestions:
I think that is it for the first round, really all cosmetic stuff. |
I'll keep this open as a placeholder until I go through your list of suggestions. |
I don't think it's customisable. For the epyc version I made the mistake of not updating the CSS theme to be the latest, I'm afraid the more structured way is the future. Good news that this is a very widely used CSS theme, so the one-too-many click is exactly the same as everywhere else.
not sure whether it's customisable, docs says download is for the currently viewed page, and it maybe a global configuration. Could we open a separate issue for this, so the idea is not lost (I may just need to look into more example or ping a jupyterbook contact, both of these would happen slower than I would like to get the other changes from your list merged.
OK, this is easy to do and I'll change it. Binder worked for me when I checked, but it's very much a hit and miss and very often doesn't work. Colab is interesting that doesn't work, it should, but I think some upstream fix is necessary for it to pick up the ipynb version rather than the markdown.
Done
Done
Github picks that up for the repo readme blurb, so ideally it has some generic info about the repo. But if its content doesn't make sense for the HTML pages (I expect it is a shortened version of some parts of the documentation anyway), we can jot not put it into the index page (right now it's included as is) |
The |
the PR is just a spelling change, but here are additional suggestions:
Can we change the headings under the Table of Contents to be:
"Photometry" (instead of "Multi-band forced photometry) and "Time Domain"
Then the "Photometry" heading doesn't need to be a link to a page with a link to the notebook. Since there is only one notebook in that heading, I think it is fine to not have the heading be a link. The notebook title under it will be the link.
Inside the rendered notebooks, I don't need the orange # that appears next to the headings when I hover over them and appears to move that section to the top. This is just a preference and not a strong opinion.
For the forced photometry rendered notebook, the section heading doesn't appear to have worked for section 2. I think "Use fornax cloud access API..." should be 2.1, etc. Sorry if this is a problem with the original notebook, and leet me know if you want me to change anything in the .md file
Issue edit intro readme file to be more useful #196 is already opened to edit the text blurbs in the intro readme file which will propagate to here.