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
Update tutorials #598
Update tutorials #598
Conversation
This comment has been minimized.
This comment has been minimized.
Unrecognized words (3) cnica
Instrumentaci
ncia Correspond to:
which I added to |
Documentation preview deployed!Available at https://docs.egi.eu/documentation/598 |
This comment has been minimized.
This comment has been minimized.
Documentation preview deployed!Available at https://docs.egi.eu/documentation/598 |
This comment has been minimized.
This comment has been minimized.
Documentation preview deployed!Available at https://docs.egi.eu/documentation/598 |
This comment has been minimized.
This comment has been minimized.
Documentation preview deployed!Available at https://docs.egi.eu/documentation/598 |
This comment has been minimized.
This comment has been minimized.
Documentation preview deployed!Available at https://docs.egi.eu/documentation/598 |
Documentation preview deployed!Available at https://docs.egi.eu/documentation/598 |
Solving spelling issues brings up loads of markdown errors. Indeed I chose html since markdown tables are not appropriate for tables like this. I would appreciate input on the best way forward. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I find the proposed structure a bit confusing. The page itself looks good, but then child pages seem unrelated. Should we move them somewhere else? or mention them explicitly in the Overview?
Then, I find the information in the tables could be clearer, I think they miss a header row. Maybe tables could have Title, Target Audience, Abstract and Recording as columns? For sure the title should be easier to identify, now as italics it blurs among the rest of the text.
I find the page quite/too long to load, and hard to navigate. It also basically hides the other tutorials. Adding raw html code is always causing issues with the automated lint, I guess the solutions would be either to exclude the problematic checks for the HTML code, or to use some (custom) short codes and/or partial template (there is one for youtube in fact: https://gohugo.io/content-management/shortcodes/#youtube): For the spelling issue with accentuated later, it would need some research, in the meantime we can bypass this if needed, but it would be nice to have an issue opened for tracking this later. |
I agree that a quick "index" to identify things might look better.
|
Documentation preview deployed!Available at https://docs.egi.eu/documentation/598 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks good to me. Thx
Note: Using raw HTML was the only solution I found to work with big tables in an easier way. Unless there is a better alternative I would propose to exclude it from the linting. |
I've already mentioned other options, with the short codes and partial templates. https://docs.egi.eu/documentation/598/users/tutorials/ is now clearly easier to read, there is no mention of ad-hoc subsection, is it on purpose? |
It is Baptiste.
|
OK, so if it's on purpose it's fine with me, I'm happy to let you decide on the best way to manage this. :) Two related points:
|
Documentation preview deployed!Available at https://docs.egi.eu/documentation/598 |
Documentation preview deployed!Available at https://docs.egi.eu/documentation/598 |
Hi All, I discussed with @glarocca and we think this is ready to be merged. Does anybody have any other proposal? or can we go ahead? Best regards, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I think it looks better. My only comment would be to have some sort of index or similar. For example, in the "Intermediate" page I have to scroll quite a bit to navigate the contents, there is no TOC or similar element that can tell me in a single flash what sort of things I can expect. |
Thanks for the suggestion @EGI-ILM but I would appreciate help; does anybody know how to create a dynamic TOC from this HTML table? or should I manually create a static TOC instead? I don't think this helps? https://gohugo.io/content-management/toc/ |
Summary
As requested via: https://docs.google.com/document/d/1nN3vw0GasnnMlM711se62Shfc3LHLP90CNh82lPmqds/
Related issue :