Skip to content
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

Collect publications / blog posts / online information of this project #151

Open
paulzierep opened this issue Jul 10, 2024 · 10 comments
Open

Comments

@paulzierep
Copy link
Collaborator Author

Since the new workflow logic pushes results to the dedicated results branch, we also need to update all depending paths for the results.

@supernord
Copy link
Collaborator

@paulzierep / @bebatut - should we add this information to a dedicated page on the website for the CoDex? I can do this as part of the BioHackathon project this year. Using the ELIXIR toolkit theme.

@bebatut
Copy link
Member

bebatut commented Nov 4, 2024

It would be great, yes :)

@paulzierep
Copy link
Collaborator Author

@supernord
Copy link
Collaborator

See example here: https://supernord.github.io/galaxy_codex/project
What do you think? @bebatut and @paulzierep

@paulzierep
Copy link
Collaborator Author

This look great @supernord ; could we also work on the https://supernord.github.io/galaxy_codex/ tool list ? like showing all columns ?

@supernord
Copy link
Collaborator

yes 😄
working on this today

@paulzierep
Copy link
Collaborator Author

I am checking with Bert atm

@paulzierep
Copy link
Collaborator Author

Thanks to @bedroesb
we got https://paulzierep.github.io/galaxy_tool_extractor/ now !
So the query builder is part of elixir-toolkit-theme
You can pull the changes from https://github.com/paulzierep/galaxy_tool_extractor/tree/elixir-toolkit-theme if you want to continue @supernord

@paulzierep
Copy link
Collaborator Author

Since this looks really nice, and we assume it will be awesome with some minor changes, we thought we can replace the old html hack style way to create the tables that can be embedded in other places.
Therefore, it would be required to create sub-pages where each table (tools, workflows, trainings) is rendered individually as well -> better for embedding, ad this would be needed for each community as well. @supernord do you want to look into it ? I guess with the current progress, that should be doable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants