Hey everyone! A new wiki is now available for use 🗒️ https://wiki.ledstrain.org/ How to contribute? If you have information you have collected, I definitely encourage contributing, as it will be organized, searchable, and available to be updated by anyone over time. Features: Uses markdown - Beginner Guide Automatically indexed and a table of contents is on every page Extendable, new features can be added if needed. The FAQ and the Tutorial have been migrated to it Layout: / └── /docs └──── /hardware └──── /category ├── #device_1 ├── #device_2 └── #device_3 /docs/hardware/phone/#device_1 --> https://wiki.ledstrain.org/docs/hardware/phone/#S10 if(window.hljsLoader && !document.currentScript.parentNode.hasAttribute('data-s9e-livepreview-onupdate')) { window.hljsLoader.highlightBlocks(document.currentScript.parentNode); }

Slacor I am a big fan of Hugo (and other static site generators), Less infrastructure that needs to be handled, less security concerns, etc. What I think the issue with previous attempts at a wiki for this site was (and might still be) is that properly organizing information requires a consensus on how to do it, and the process of organization has a lot of "overhead", which takes time. Something that people don't have a lot of when they're busy enough and have their eyes bothering them from screens.

JTL process of organization has a lot of "overhead" Absolutely, I've simplified the process for this reason. There is no need to organize further. For example, all phones go on one page. Just scroll to the spot and edit it. It is automatically indexed and permalinked For the first time a user makes a edit, github requires some extra steps however

@JTL Checkout https://wiki.ledstrain.org/contribute It's sort of a front end to github. Things that are submitted are automatically submitted as pull requests.

@Slacor Hi, when I discovered this forum a week ago, the first thing I thought is it needed some sort of organitzation, and now you create a wiki. I really want to help improving it, and for that the first thing I think it needs is a glosary of terms/concepts, because someone new needs a lot of hours to understand all details in the eyestrain illnes world. I tried to create the Glossary section but it wasnt possible with the edit button nor through the github page. Can you do it and I will fill it?

NotAlone I added a glossary page https://wiki.ledstrain.org/docs/glossary/ edited: What I would do is something like: ## Category ### Term Definition if(window.hljsLoader && !document.currentScript.parentNode.hasAttribute('data-s9e-livepreview-onupdate')) { window.hljsLoader.highlightBlocks(document.currentScript.parentNode); } Or, just a simple term and definition ## Term Definition if(window.hljsLoader && !document.currentScript.parentNode.hasAttribute('data-s9e-livepreview-onupdate')) { window.hljsLoader.highlightBlocks(document.currentScript.parentNode); }

I will add my dithering tests and methodology when I have time

Done. I think you have to approve it or something. My keyboard is a little bluetooth one, and lack of some characters. Also I am not a native english speaker, so maybe you would want to check it. Next week I will do another entry explaining the diferent kinds of screens (IPS, OLED, etc)

NotAlone I don't see it yet If you modified it at /contribute you may need to set it to "in review". (I'm still figuring out how it works) If at github, you'll need to compare and submit the pull request and then I can merge it in New feature: Embedded Posts This embeds a "live" version of a post. {{< forum-post "555" >}} {{< forum-post id="555" length="300" >}} {{< forum-post "https://ledstrain.org/d/795-community-wiki/10" >}} if(window.hljsLoader && !document.currentScript.parentNode.hasAttribute('data-s9e-livepreview-onupdate')) { window.hljsLoader.highlightBlocks(document.currentScript.parentNode); } You can get the post ID by hitting reply and it'll look like this: -> @Slacor#11754 {{< forum-post "11754" >}} An example of a embedded post: https://wiki.ledstrain.org/docs/guide/#diy-oscilloscope---pwm ## DIY Oscilloscope - PWM {{< forum-post "3658" >}} if(window.hljsLoader && !document.currentScript.parentNode.hasAttribute('data-s9e-livepreview-onupdate')) { window.hljsLoader.highlightBlocks(document.currentScript.parentNode); } Posts are styled now:

Community Wiki

Slacor

NotAlone I don't see it yet
If you modified it at /contribute you may need to set it to "in review". (I'm still figuring out how it works)

If at github, you'll need to compare and submit the pull request and then I can merge it in

New feature:

Embedded Posts

This embeds a "live" version of a post.

{{< forum-post "555" >}}
{{< forum-post id="555" length="300" >}}
{{< forum-post "https://ledstrain.org/d/795-community-wiki/10" >}}

You can get the post ID by hitting reply and it'll look like this:
-> @Slacor#11754
{{< forum-post "11754" >}}

An example of a embedded post:
https://wiki.ledstrain.org/docs/guide/#diy-oscilloscope---pwm

## DIY Oscilloscope - PWM                                                       
                                                                                
{{< forum-post "3658" >}}

Posts are styled now:

Slacor

The Wiki is transitioning from Netlify to Github Pages.
While DNS is propagating there might be some downtime

JTL

Slacor Why moving from Netlify to GitHub Pages?

Slacor

NotAlone Found it and merged it in 😃
https://wiki.ledstrain.org/docs/appendix/glossary/

Slacor

JTL I've been building other sites too, and I've been getting closer to the 300 minute build time quicker then expected.
Github Pages gives 2000 minutes, so I've been seeing how that is implemented.

JTL

Slacor Understood.

NotAlone

@Slacor Some days ago I posted an update for the wiki, and now I just did the same with two more sections, and still can't see the update from the other day. Probably you have to accept it and you didnt see it. Check it please 😉

Slacor

NotAlone How are you editing it? With the Front end at https://wiki.ledstrain.org/contribute?
This is the biggest case of them not showing up:

Note: be sure to set the status to In Review after saving. This causes a change request to be made.

NotAlone

Slacor I don't do it through the page you linked. I do it through the "edit page" button on the wiki page. This is also how I did it the last time.
So shall I do it again through the page you linked or did you find the edits I done?

Slacor

NotAlone

When you do it through github it'll probably show something like this

You’re editing a file in a project you don’t have write access to. We’ve created a fork of this project for you to commit your proposed changes to. Submitting a change to this file will write it to a new branch in your fork, so you can send a pull request.

What's strange is I just tested it and I could detect a fork being made but I don't see yours.
Can you link to where it shows your changes?

NotAlone

@Slacor Using the contributr link you passed to me it just shows the major branches of the wiki (Hardware, software, awareness, appendix) but when I click on any of them it appears nothing inside, just "No entries".

Doing it again (luckily I made a copy of everything I tried to edit) and passing you the link: https://github.com/ledstrain/wiki.ledstrain.org/compare/master...Pitoniso:patch-5?diff=unified

This time I did something I didnt the other times. You will tell me

Slacor

NotAlone Merged it in 👍️

NotAlone Using the contributr link you passed to me it just shows the major branches of the wiki (Hardware, software, awareness, appendix) but when I click on any of them it appears nothing inside, just "No entries".

I'll look at this

Slacor

NotAlone Using the contributr link you passed to me it just shows the major branches of the wiki (Hardware, software, awareness, appendix) but when I click on any of them it appears nothing inside, just "No entries".

I put out a fix, this should be working now

NotAlone

Slacor Now it seems to work, but I am not sure if the changes are saved. I click on the "Save" button, but can't see no change on the wiki. Maybe you still need to accept the changes.

I edited the Graphic cards and Windows section.

By the way, now on the Ereader section appears the changes I made before

Slacor

NotAlone
Yes, the way it works is anyone can propose changes changes, and then authorized users can accept those changes after looking at them, or comment on them.
As long as a pull request is made, you're good to go

I don't see any pull requests pending at this time, I'll look at your repo a little later.
I haven't tested this method too much, I may create a step by step guide for it as it requires a bit of understanding of how github and git works and to help avoid to avoid the pitfalls you're discovering.

NotAlone

Slacor As it seems it didnt worked with the contributor webpage you passed here, I did it again with the "edit page" button on the wiki, sending the "Pull request". Did it with Windows page and Graphic card page

Hope this times works.

« Previous Page