Adding new content to wiki
- Edited
Moved from https://ledstrain.org/d/1404-eyestrain-triggers
How old is the post? I believe it's set to at least a couple weeks,
If you looking to have a lot of mostly static information that may be slowly updated over time I would recommend the wiki. The information in these posts above look like they would be good content for it
Slacor Yep, 15 days ago. If you scroll through this thread, I've made lists with known problems and solutions and the idea was that I would be updating them - but I can overwhelm the wiki with this info, there's a lot.
You can see here how the wiki could look like and I am pretty sure there will be more.
Yep, these posts also were created to be a basis for the wiki.
For right now, go to https://wiki.ledstrain.org/contribute/#/collections/links and create a new "link" page for each section of what you're writing about.
Then we can discuss about triaging or organizing it
I'll set post editing to infinite again for a few days
Moved this to its own thread but let me know if you have any questions about this. I'm not 100% sure what needs to be told so feel to ask
Ooops, didn't notice and replied there
Mrak0020 I am not sure where is the correct version of markdown. Rich text in the editor on the right shows a very different page compared to the preview window on the left. For now I formatted pages based on the editor.
I am not sure it should go under the links section.
Other sections that I wrote here are most definitely not for the links section.
Maybe we will work with @logixoul on wiki filling and will figure out where to place those pages or that info in the process.
You can see the markdown support here
https://www.markdownguide.org/tools/hugo/
https://spec.commonmark.org/0.30/ (in-depth)
Could you explain making the formatting look good?
It's styled with CSS, so to look different that would have to be adjusted
There's no reason to put it under links beyond it's easily accessible right now with the CMS (at wiki.ledstrain.org/constribute)
It might be worth discussing a tree structure to the wiki if enough people would like to put in some feedback.
- Edited
Slacor Could you explain making the formatting look good?
I meant that formatting looks ok in a rich text editor (left) and horrible in preview and then in actual Wiki, as it turned out.
On the left, there is a readable text, on the right all the links unexplainedly turned into a long single paragraph. I do not know how to fix it.
Thank you for markdown links, I suppose they can answer this question.
About the second and third question: what I meant is that I wrote in that thread some brief info about binocular vision with a few links and a simple PWM guide, but I doubt that I should place them under the links section in Wiki.
Yes, thank you, found what I needed in the links you gave and created two pull requests (or I hope so).
- Edited
Slacor I hoped that was the end but turned out it was not. Now formatting looks good in preview on contribute page, looks good on GitHub preview, but the resulting formatting in wiki hasn't changed at all
And now I definitely do not know how to fix it, as both previews show text correctly.
It seems that contributing to wiki requires some skills of a front end developer
- Edited
I went in and formatted it to maybe serve as an example
There is a quirk that may be causing the trouble.
Two spaces after the end of a line will enforce a newline
Two examples (highlight to see the difference)
This is one
line
This is two
lines
Fyi, I moved links -> New-Content
Hopefully, new files will be created based on the title as well now.
Common Solutions for Newcomers the main page there
For clarification, you mean /known-problems would have the content of the current "Common Solutions for Newcomers", and subpages would be the problem lists?
Eg, /common_solutions/problems_monitors_laptops