Conversation
|
Since it will likely stay a short text, could we add it more directly, without separate html? It's already quite a bunch of files to check and not always clear where content is actually located. We could have it in shape/tone of a subtitle ? "- Useful tools and techniques for researchers who code"? Or something like that? |
1 similar comment
|
Since it will likely stay a short text, could we add it more directly, without separate html? It's already quite a bunch of files to check and not always clear where content is actually located. We could have it in shape/tone of a subtitle ? "- Useful tools and techniques for researchers who code"? Or something like that? |
I don't know why the decision was made to have so many files. In
For sure! |
|
Yea, there is likely a reason for that. Let's leave as separate files. |
|
Any preference about the text? |
|
Could you add a screenshot on how your solution looks rendered, please? |
|
I did not put much thought into it, that's all, as I do not feel I should take decisions on what is written so close to the title of a CodeRefinery workshop, since I'm just kind of a CodeRefinery hitchhiker/freeloader :-). |
Useless digressionFrom the log of the index.html file on the template repo, I can see that it was mostly @bast adding more It's yet another instance of the flat vs nested, modular vs monolithic approach. |
Description should be adjusted - I have not put much thought into what to write there, I wanted just to explore how this is technically possible. For consistency, one could use the most appropriate of the already existing blobs of text.
Example: https://mmesiti.github.io/2026-03-17-workshop/