openms / openms-docs Goto Github PK
View Code? Open in Web Editor NEWOpenMS Documentation.
Home Page: https://openms.readthedocs.io
License: BSD 3-Clause "New" or "Revised" License
OpenMS Documentation.
Home Page: https://openms.readthedocs.io
License: BSD 3-Clause "New" or "Revised" License
No. Enhance UX and information for readers.
Add more screenshots in display-modes-and-view-options.md file.
NA.
NA.
At the moment, the glossary term links are difficult to distinguish. By adding an image or changing the text colour, this will help them stand out.
We should change the default branch to develop
from staging
in sync with OpenMS/OpenMS.
User facing URLs:
URLs having redirects:
Internal development URLs
Internal trial URLs
Here are some examples containing the correct style for drop-down menu navigation:
The following needs to be changed to the style shown above (in this file):
No, maintenance automation.
Add automated link/URL check for broken or dead links.
This looks like a good GitHub action: https://github.com/marketplace/actions/markdown-link-check.
Would you be interested in adding this GitHub action? @greengypsy
You can format keyboard strokes like so:
DEL
This should be added to the documentation.
This was discussed here.
For example:
Could be: A sequence of tools run on input data such as an mzML file which produces an output. There are over 185 TOPP tools to choose from.
No. UX.
Make the pages friendlier, especially beginner-friendly to make OpenMS more generic.
Icons: https://pradyunsg.me/furo/kitchen-sink/sphinx-design/#icons
Example: https://github.com/pradyunsg/furo/blob/main/docs/kitchen-sink/sphinx-design.md
To check code read the example page in RAW mode.
None.
No. UI/UX enhancement.
Add a Twitter icon on the footer before RTD and GitHub icon:
How to do it in Furo: https://pradyunsg.me/furo/customisation/footer/.
None.
As you can see, the bash lexer is not creating a token/span class separately for the command git:
We may need to modify the bash lexer using the instruction at the pygments website, in particular the "Modifying Token Streams" section.
I don't think this will be difficult to do, but I'm guessing is not high priority.
@jpfeuffer @tapaswenipathak would be good to hear your thoughts.
This issue tracks:
Introduction should have a different, more detailed text.
Would be nice if we used fixed version numbers in the docs, such that older docs still point to older releases in the install instructions.
This is only maintainable with variables. I bet this is easily possible with sphinx.
No, UX.
Use more keyboard keys for navigation.
Set the following to true:
navigation_with_keys
NA.
I have checked the following places for the error:
I have created the bug report in OpenMS for any pipeline errors.
Not all Glossary terms are assigned a term
role.
If it is an .rst
file. use :term:
, otherwise use
{term}`glossary-term`
around the glossary term. All glossary terms are available here.
A few examples are below:
All glossary terms should be linked to glossary definition.
NA.
Plus points if this can be automated w/o false positives.
The following screenshot is from the user-interface.md file.
I think this text should go within a warning admonition. For more information on admonitions, see this link.
This is how I think the documentation could be structured:
Introduction
Getting Started
Quick Start Guides
TOPP
KNIME
TOPPAS
Tutorials
Developer Resources
Additional Resources
Downloads
Quick Reference
@tapaswenipathak @jpfeuffer would be great to hear your thoughts.
There are many places in the documentation, where back ticks are missing. Libraries, files and anything code related needs to be between back ticks. For example at this link:
This issue can be used as a tracker to close the point raised in the review of PR #65.
No, UX.
#cccccc
Connect OpenMS documentation with OpenMS API reference.
In the user quick start guide I think our definition of UTILS is a bit outdated. By now, we include experimental, little tested tools there as well.
Ref #65 (comment).
Check all occurrences of MacOS. Should be macOS imho
The current style of Notes etc does not look nice. There must be a wrong use of admonitions. Please check how to do this correctly.
I have checked the following places for the error:
I have created the bug report in OpenMS for any pipeline errors.
No, cleanup.
Right now, the lines are of varying lengths. Red vertical line is at 120 characters.
There should be some GitHub action, plugin, or something to automate this; if not, do it manually for consistency.
I think OpenMS readthedocs requires a resync GitHub incoming webhook integration, I don't have the auth.
(tasks gets lost in discord, will use issues from now on)
It would be nice to add tooltips to glossary terms, so that people don't have to navigate away from the page to find a definition.
Resources include:
For more info here is a link: https://www.w3schools.com/tags/tag_meta.asp
Basically it is for Search Engine Optimisation purposes. So I think we should have it.
But don't know how to implement it in markdown. We might need to write some sort of script. I'll keep digging if you think it's a good idea.
I have checked the following places for the error:
I have created the bug report in OpenMS for any pipeline errors.
Glossary contents are not sorted, rn.
Sorted list.
You can easily install openms via bioconda now on Linux and macOS.
Add that option.
Either to both subpages, or create an own page for it.
We should probably think about the order of the doc sections. I just looked at the headings in the Sidebar and I felt like the order is not always optimal. E.g. TOPP tools are explained after the TOPP Tutorial. And Scripting with TOPP might be better suited in the TOPP section.
I have checked the following places for the error:
I have created the bug report in OpenMS for any pipeline errors.
The images on the this page aren't rendering properly.
The following extensions need to be tested:
Find more information here.
I think we should reorder. Not sure how stable our debian packages are. They should be moved down.
Docker instructions need update.
If you think it helps for UIX.
No. UI/UX + automated user feedback for OpenMS Documentation.
Ask user if read page was helpful with yes or no.
How to Inject JS code documentation:
cc @greengypsy for suggesting the enhancement.
https://pygments.org/docs/lexers/#lexers-for-various-shells
currently the highlighting is off
We would like to create tutorials for TOPP shell and TOPPView.
The TOPP shell tutorial will explain how to set an input and manipulate the input data.
The TOPPView tutorial will explain how to visualise the data.
In order to do this we need:
@tapaswenipathak feel free to add to this.
All URLs should be links. Or be given a named link. E.g. pkgs.org on Linux installation instructions
changes to be done: c4c8128.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.