-
Notifications
You must be signed in to change notification settings - Fork 30
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
General updates to the website #337
Comments
We could add all the little things I listed in this (https://github.com/orgs/cyclus/projects/3) project since we're messing with the website anyway. |
Should Visualization and Analysis also include third-party tools? I'm specifically thinking about Bicyclus and Trailmap |
That's a good question. I'm leaning towards no to prevent having to update that list when new things are created. Maybe mention that third-party tools do exist? |
Do we want to keep a list of everyone that has contributed to the project? It's already outdated and while nice, maybe not as necessary now that the team is much larger
|
Maybe not? Maybe the best thing to do is just link to Cyclus contributors, and maybe Cycamore and Cymetric contributors |
That's really cool. let's do that. I'll change my comment to include this. |
Would this be handled by #316 ? or would an extension to it be needed. |
I would say it does. I approved and merged that PR, so we'll double check that next time we build |
The latest build says 2024 for the copyright, so I would say #316 took care of this one. |
Wasn't sure if I should add these to my own comment or to @abachma2 's. Here are the documentation issues I found while I was learning how to use Cyclus from the website. |
I removed some of the items about files not being in a toc tree. This is only shown when you build the website, and it doesn't prevent the site from being built and there are some good reasons to not have some of these items in toc trees. |
Should we close this out by creating separate issues for the lingering items? |
This issue is meant as a list to keep track of various changes on the website, such as updates, typos, redesigns, etc. We will do our best to make sure things get updated in a timely manner. Please be sure to name the exact file that should be changed, and ideally the line(s) of the file to be changed.
To add a new item, please edit this comment, using a checkbox for each item
Moving all subtasks into the description so that they are tracked in a single place (@gonuke )
From our initial discussion (@nsryan2 ):
Warnings/issues to handle (@abachma2 ):
source/python/lazy_asd.py
, module not foundsourcec/cep/cep27.rst
lines 32, 34,107, 113, 114, 123, 129, 137, 141, 151, 155, 156, 165, 171, 179, 183source/cep/cep3.rst
line 2source/cite/index.rst
line 47source/newsletters/oct2017.rst
line 111source/previous/index.rst
line 111source/user/server.rst
line 73source/user/tutorial/add_deploy.rst
line 37source/user/tutorial/add_fab.rst
line 4source/user/tutorial/add_reg_inst.rst
line 42, 58source/user/tutorial/data_explorer.rst
lines 121, 124, 192, 231, missing figuressource/user/tutorial/mod_rxtr.rst
lines 35, 45source/user/tutorial/run_cyclus_native.rst
line 2source/user/writing_input.rst
line 65source/arche/cmake.rst
line 104@abachma2 :
main
@nuclearkatie
Cyclus publications and meetings appears to have last been updated in 2015 #365
Contributors list has not been updated any time recently
Last news update was Spring 2018
mbmore links point to Meghan's personal repo, when they are now managed and updated using this cnerg repo
Projects Using Cyclus currently only lists CVT (which doesn't exist anymore)
Copyright on the bottom of the website lists 2012-2016 and the license file lists 2010-2016
Cyclus Funding and Support is probably out of date
If you click Next from the website home page, it takes you to a page called FY2016 NEUP Funding Opportunity with Cyclus. Not sure what else the next button should take you to, but this doesn't seem like the best choice now given how out of date it is
The website still lists a time and zoom link for Cyclus development calls
@abachma2 :
Do we want to keep a list of everyone that has contributed to the project? It's already outdated and while nice, maybe not as necessary now that the team is much larger
Fix link to Numpy contributing documentation to https://numpydoc.readthedocs.io/en/latest/format.html#docstring-standard in
source/numpydoc/numpydoc.py
line 15Fix broken https://github3py.readthedocs.io/en/master/ link in
source/cep/cep6.rst
line 87 to https://github3.readthedocs.io/en/latest/@dean-krueger 👍
The text was updated successfully, but these errors were encountered: