-
Notifications
You must be signed in to change notification settings - Fork 26
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
Splitting the tutorial #173
Conversation
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 excellent! It becomes much more digestible and you added a lot of good bridges between existing content.
I found a few typos that need correcting.
I would also prefer About (or similar content) to be more prominent. It's important that people understand quickly what MDAKits are.
If you need another page for "Other resources", perhaps make a separate Citations page. Then it's also clear how to cite.
(Not for this PR: We should change the title of the Registry page itself to simply Registry of MDAKits and not write out "MDAnalysis Toolkits" — explaining this is the job of the landing page/About page. For the registry title we should just use our "brand name".)
A `video walk-through <https://www.youtube.com/watch?v=viCPUHkgSxg>`_ | ||
of this tutorial is available on YouTube. |
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.
Is there a way to embed the video?
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.
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.
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.
Actually, there's an open issue #86 ... so this is not something that needs to be solved in this PR!
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've had a go at this, anyway (it didn't seem complicated, so might as well kill two birds with one stone)
*For a video demonstration of this section,* | ||
`click here <https://www.youtube.com/watch?v=viCPUHkgSxg&t=48s>`_. |
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 would avoid "click here" – see https://www.w3.org/QA/Tips/noClickHere .
Instead make the link say what it is.
******************************* | ||
|
||
*For a video demonstration of this section,* | ||
`click here <https://www.youtube.com/watch?v=viCPUHkgSxg&t=153s>`_. |
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.
Make the link say what it is.
******************** | ||
|
||
*For a video demonstration of this section,* | ||
`click here <https://www.youtube.com/watch?v=viCPUHkgSxg&t=72s>`_. |
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.
Make the link say what it is.
********************************* | ||
|
||
*For a video demonstration of this section,* | ||
`click here <https://www.youtube.com/watch?v=viCPUHkgSxg&t=247s>`_. |
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.
Make the link say what it is.
:alt: Import a project into RTD | ||
|
||
#. Find the Kit repository and click "+". Confirm that the name, URL, and | ||
default branch (likely be `main`) are correct. |
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.
"be" ?
docs/source/making-a-kit/hosting.rst
Outdated
through these services is highly encouraged. | ||
|
||
However, your code **does** need to be installable from source. You'll specify | ||
the commands for this in the ``scr_install`` field of your ``metadata.yaml`` |
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.
src_install
*For an example, see* :ref:`example-registration` *from the guided | ||
MDAKit cookiecutter example.* |
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.
Could use a .. SeeAlso::
.
docs/source/index.rst
Outdated
:maxdepth: 1 | ||
:caption: Other Resources | ||
|
||
about |
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 would leave About near the top of the list and also make sure it's linked from the intro text.
What do you need to see if someone sends you to mdakits.mdanalysis.org for "their code" and you don't really know what to with this? Or "just make a MDAKit out of your code".
docs/source/maintainingakit.rst
Outdated
********************* | ||
|
||
.. note:: | ||
This section is still under construction, and more information will be added |
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'd remove the ", and more information will be added soon!". Who knows when content will appear...
Perhaps encourage contributions or link to discussions, maybe we get enough discussions/solutions so that we can put it here?
Just to add: I'd really like to see your update live soon as it's a massive improvement in readability and it would make it so much easier to send people to specific pages for advice. |
3e8d85b
to
6230777
Compare
Thanks @orbeckst - hopefully I've addressed all your comments! |
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 looks good to me, thanks.
Looks great!!! |
Addressing #156 , though I may have got a little carried away in tidying up/adding some other stuff in the process.
The Making (and Registering) a Kit page is now split over multiple pages (and further split to numbered steps), and the pages have been slightly re-ordered. The basic tutorial content should be largely intact, but I reworded/added some things I felt would improve clarity and make it flow better now it's over multiple pages, particularly at the start of the adding documentation section, and there's a "requirements checklist" that gets updated at the end of each of the tutorial pages.