Closed scharlottej13 closed 2 years ago
Thank you!!
Yeah I like that plan to merge and iterate. The docs won't be rebuilt until the next release unless we specifically trigger them in readthedocs.
Sounds good @jsignell and @jacobtomlinson, thanks for taking a look!
~Since @jrbourbeau fixed the RTD build, if you (or others) have bandwidth to click through some of the docs pages, that would be great. Of course, I can also make more changes after "going live" on 6/6.~ Sorry, realized that doesn't actually make sense!
The docs won't be rebuilt until the next release unless we specifically trigger them in readthedocs.
@jsignell does this mean triggering a docs build separately for each project (e.g. dask-ml
, dask-distributed`, etc.)? And, if so, @jacobtomlinson does it make sense to merge these PRs today or tomorrow instead? I haven't triggered a rebuild in readthedocs before (I don't think I have permission to do so), but happy to do so if someone doesn't mind walking me through the steps.
cc @jrbourbeau
Id rather wait until the website is live on Monday.
We need to merge here, tag a release, potential update pinned versions in downstream projects and then rebuild the docs sites on each of those.
In most cases rebuilding the downstream docs sites involves merging a PR to main.
We need to merge here, tag a release, potential update pinned versions in downstream projects and then rebuild the docs sites on each of those.
I can open up PRs to update the pinned versions in downstream projects. From the release history looks like it will be 2.0.4
?
In most cases rebuilding the downstream docs sites involves merging a PR to main.
@jacobtomlinson would it be helpful for me to open placeholder PRs in downstream docs sites to make this easier? The downstream sites I have include (going down the list of repos):
Also, thanks for answering all my questions! Just trying to figure out what the steps are and how I can help.
That would be super helpful! Anything that's not marked as archived on GitHub will need updating.
I think given this is a major rebrand we should tag version 3.0.0
though.
That would be super helpful! Anything that's not marked as archived on GitHub will need updating.
I think given this is a major rebrand we should tag version
3.0.0
though.
Perfect! I'll open those PRs up today and will tag you two in them @jacobtomlinson and @jsignell
Update Dask docs design in line with rebranding efforts in https://github.com/dask/community/issues/220. Changes include updated Dask logo, color palettes, and fonts.
To do:
Here are a couple screenshots for comparison:
current docs
changes in this PR![Screen Shot 2022-05-31 at 10 49 45 PM](https://user-images.githubusercontent.com/8620816/171336595-cb7c5125-b6ff-4580-b49f-bbe9f15875a3.png)
cc @jacobtomlinson @AdiReske @jrbourbeau @jsignell