-
-
Notifications
You must be signed in to change notification settings - Fork 580
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
help wanted: move widget docs #605
Comments
Great! Yes, let's add the widgets to the Editor UI page of the wiki. I have added "Widgets" to the page table of contents and created the anchor and the section title. Please add the content here: https://github.com/silexlabs/Silex/wiki/Editor-UI#widgets |
Hi all |
Thx for helping @andreamussap !
You are right, you can just add a comment with a link to the widget and then I will close the issue |
Also you may be interested in this info: there is a new "component system" in silex, and this kind of "widget" should probably be ported (yet to be discussed for each widget) to the new system. This means to add 2 files for each widget, see these components for an example. If you are able to do this, please let me know :) |
@lexoyo I've updated section 'Widgets' with two widgets. Please let me know if this is what you and @jennparker have in mind, so I can continue from there. |
There's a typo in the description of Side menu widget for Silex: "A dropown menu or hamburger menu...". The word 'dropdown' is misspelled. As the page/issue is not editable I can't fix this. How should I proceed when I find tiny issues, typos, etc and the content is not editable? How do I inform this to ye? |
@andreamussap, that's what you have to do:
It is best to copy the text from the issue to the Editor UI page piece by piece as it is more accurate than copying the whole text and then trying to format it. You can use MarkdownPad. Copy the text from the original issue piece by piece and paste it into MarkdownPad. This will allow you to see in real time how the text will look like on the Wiki page. (Keep in mind that MarkdownPad and GitHub interpret some Markdown marks differently.) Then cut the text out of MarkdownPad and paste it into the corresponding section of the Editor UI page. |
After you have copied the text from the issue and pasted it on the Editor UI page, add the widget name to the table of contents. Then leave a comment in the original issue and lexoyo will close it. |
We have decided to move the issues with the label "widget" to a page named "widgets" in the wiki.
For each widget this is to do
The text was updated successfully, but these errors were encountered: