docs: Add a page for diffpy.utils in the product page

[stevenhua0320]

As in title, we need to contain the installation guide, a short description of the package

[cadenmyers13]

diffpy/diffpy.utils#294

[stevenhua0320]

@cadenmyers13 We have done part of it, what we left over is to add the screenshot of the page like we did for the other product, and we after we have done that, we could add it into the product manuscript. The part of we have done is referenced here: #68

[cadenmyers13]

@stevenhua0320 Thanks for doing this. I would like to get utils out the door ASAP because it has a tool we are using for deprecation. My issue currently is that I dont see the utils.rst page when I build the docs. So, all the work you put into writing the docs isnt visible when docs are built (unless Im missing something). When you build docs locally, do you see it?

[stevenhua0320]

@cadenmyers13 we need to add it into https://github.com/diffpy/diffpy.github.io/blob/source/_templates/menu01.html so that it would be visible. I havn't done it so far because we don't have the corresponding screenshot. Of course you can find an appropriate one and replace it in the utils.rst that in the products. I think after you add it to the template it should be visible.

[cadenmyers13]

@stevenhua0320 what do you mean by screenshot? Like a diffpy.utils logo or something? That might not be needed here. We don't have one for the getx page.

[stevenhua0320]

@cadenmyers13 I mean a screenshot of the code at the background and a plot at the front. If we don't need that then adding it into the manuscript would be fine then.

[sbillinge]

utils is mostly an API package so I would say, initially, we don't need a screenshot. I appreciate @stevenhua0320 impulse to finish it up nicely (you have learned well how to make robust and high quality code!) but in this case I think it is not needed.

[cadenmyers13]

@stevenhua0320 yes, thank you for the good work! If one of the examples in diffpy.utils produces a figure that is representative of its capabilities you could try to use that as a logo. Otherwise, like @sbillinge said, i think we're good.

[sbillinge]

I don't think we need a logo for this. As default we use the diffpy C60 figure for the logo. The figure is just some eye-candy on the product page, but we maybe don't need that here for the time being. It is a good impulse to want it though. We can revisit this in the future.

Can this issue be closed (or will it close automatically when the page PR is merged)?