• Meta

  • Adding new content to wiki

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.

      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).

        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 🙂

          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
            4 days later

            Slacor There is an idea to create a new directory, something like Known Problems, make Common Solutions for Newcomers the main page there, and move problem lists there as subpages. Maybe also move there vision info, as it has known vision problems. What do you think about it?

              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

                Slacor Yes, just with one little difference: I think that directory itself should be called known problems, as we do not have solutions for every problem, unfortunately
                /known_problems/Common Solutions for Newcomers - main page
                /known_problems/problems_monitors_laptops

                This way we will have all problems and, where possible, solutions collected together

                    Mrak0020

                    I don't think that this would be a good idea. People generally don't look for problems, they look for solutions. Even if your idea is more "correct" I would say that in this context the benefit is higher the other way round just from a marketing perspective.

                        xelaos when people know what is their problem, how to test it, and how to detect it, they can simply avoid it. It is endlessly better than going through the discussion like 'Usable smartphones' or 'Apple products feedback', where there are lots of different people with different triggers. I compare it to 'A person with an allergy and a person with diabetes discuss a cupcake with peanut butter'.
                        I am also trying to find people who are affected with the same thing as me and detect what is that thing.
                        From my perspective, I would be more than happy to find any Problems list in wiki half of a year ago (whether they have solutions or not). I had to go through all the discussions in two languages and create it myself instead.
                        This is why I do not see downsides in naming it that way.
                        But I agree that name should be catchy.
                        Anyway, I don't actually care how the section is named as long as it is there, it is easy to find and everything is together. Keeping lists together is my main concern. Maybe there can be another good name for the directory.
                        Marketing perspective definitely matters for those who find Ledstrain Wiki through Google, but I don't remember links to Wiki. Google led me to the forum.

                          I set it up as described for now. Names, and structure, can be changed if needed

                          known-problems
├── _index.md
├── known_smartphone_problems.md
├── list_monitor_laptop.md
├── problems_monitors_laptops.md
└── vision-info.md

                          There's two problems with a deeper directory structure, it's harder for posts to be edited with the CMS, and the implementation for navigating to sub directories isn't great.

                            Slacor Thank you!

                            BTW, for some reason, when I press 'Edit the post', I am redirected to GitHub anyway, so I haven't tried editing posts through CMS.

                              Edit the post will always lead to where it is hosted and will always be available.

                              /contribute is manually configured by me to hopefully make changing pages a little easier.
                              It's a work in progress and can be outdated.

                                Slacor @Mrak0020

                                Thank you for your work.

                                I still think "known problems" is really bad and thought your "common solutions" idea was better.

                                However, I definitively see Mrak's point about "people know what their problem is" , but when I see "known problems" it don't want to click on it, since I know my problem, but Im here to find a solution. I think the initial "Common Solutions" idea was better and adding Mrak suggested structure under this heading would also be great.

                                Maybe this is only my point of view, so if more people think the problem => solution structure is better, it is fine I guess.

                                    xelaos You could think about a better name that has 'solutions' in it. I would only suggest avoiding 'common' (as unfortunately there is little in common between different triggers and it will mislead as a section name). Maybe "problems and solutions"?

                                    Also, a link to this section should be available through the forum because I doubt people will find it otherwise (as Google leads to the forum directly). Maybe a link to the Common Solutions page can be put somewhere where it is visible, and there is already navigation from that page to others.

                                    Here you can see stats for both forum and Wiki, and it seems no one other than me visited Wiki in the last 30 days (I bet most of those visits from Ukraine are mine).

                                        Mrak0020 Also, a link to this section should be available through the forum because I doubt people will find it otherwise (as Google leads to the forum directly). Maybe a link to the Common Solutions page can be put somewhere where it is visible, and there is already navigation from that page to others.

                                        Yes, this would be better.

                                        Mrak0020 You could think about a better name that has 'solutions' in it. I would only suggest avoiding 'common' (as unfortunately there is little in common between different triggers and it will mislead as a section name). Maybe "problems and solutions"?

                                        Your right, maybe potential solutions would be better.

                                            dev