Applications page rework

[cbielow]

as discussed:

• add links to common workloads, like LFQ and TMT workflows for KNIME, Galaxy, TOPPAS etc
• split by OMICS type (PTX, MTX, etc)

[matteopilz]

An ideal solution could look something like this:
https://hub.knime.com/search?tag=OpenMS&sort=maxKudos&type=workflow

Hi @cbielow and @matteopilz , I'm a developer with experience in web design and frontend frameworks. I saw the proposal for the Applications page rework. I'd love to help restructure this using the KNIME Hub style you mentioned. Do you have a preferred CSS framework or a staging branch I should work from?

[matteopilz]

Hey @Tanush576, we would be happy if you gave this a shot. There is an old draft that I created quite some time ago: #204

The issue that we had was to merge all the relevant information together from our nf-core, KNIME, Galaxy and TOPPAS workflows, including our new webapps. The idea has been to include a meaningful search and filtering system that looks good as well and can be updated easily if the workflows change.

Thank you for the guidance, @matteopilz! I’m diving into the draft in #204 right away to understand the previous architecture and what blockers were encountered.

My focus will be on creating a maintainable data structure (likely using Hugo data files or Frontmatter) so that your team can easily update workflow links for nf-core, KNIME, etc., without touching the complex UI code. I'll also start looking into a lightweight filtering system (like a JS-based isotope or search filter) to match that KNIME Hub experience.

I'll explore the current repo structure and share a brief plan/mockup here soon before I start the heavy lifting. Looking forward to making this happen!