Skip to content
This repository has been archived by the owner on Aug 28, 2020. It is now read-only.

Write a tutorial for the new RichDisplay and further reading tutorial for RichMenu #37

Closed
bdistin opened this issue Sep 28, 2017 · 0 comments · Fixed by #55
Closed

Write a tutorial for the new RichDisplay and further reading tutorial for RichMenu #37

bdistin opened this issue Sep 28, 2017 · 0 comments · Fixed by #55
Labels
Bug: Fixed Issues that report bugs and have been fixed.

Comments

@bdistin
Copy link
Contributor

bdistin commented Sep 28, 2017

By the time HactoberFest begins, RichDisplay and RichMenus should be merged into master. It would be great for someone to write tutorials for using them (like the other docs tutorials you can find in the ./tutorials folder).

The tutorials should include a general overview, basic implementation with explanation of parameters, and creative examples of use. The RichMenu should have it's own tutorial as a child of RichDisplay (RichMenu extends RichDisplay) highlighting the similarities and differences, and it's own examples of use.

Please be sure to create your pull request after the first of October so your pr counts for HactoberFest. More details about HactoberFest

Edit: The RichDisplay Tutorial has been completed, and merged. A RichMenu tutorial is still wanted.

@bdistin bdistin added the Event: Hacktoberfest Issues and PRs related to Hacktoberfest. label Sep 28, 2017
HellPie added a commit to HellPie/klasa that referenced this issue Oct 11, 2017
Fixes half of dirigeants#37

The tutorial's code should be well explained.
I tried to use really simple code without any fancy method, so everyone with a minimal knowledge of JavaScript should be able to understand it.
bdistin pushed a commit that referenced this issue Oct 12, 2017
* Add RichDisplay tutorial

Fixes half of #37

The tutorial's code should be well explained.
I tried to use really simple code without any fancy method, so everyone with a minimal knowledge of JavaScript should be able to understand it.

* Add links to docs when possible so the user

* Fixed eslint and tupos

* Fix more eslint and use https cuz it works

* Another one bites the dust...

* I declare you... done and dusted?

* Pudding, padding, idc... dulcis in fundo...

* I'm gonna go have a stroke now.

* Changed link format and fixed code again

* Fix name and add filter example and fix basic demo
HellPie added a commit to HellPie/klasa that referenced this issue Oct 14, 2017
With dirigeants#52 fixes dirigeants#37 completely.

The tutorial follows a similar flow and should be a bit better than the one initially pushed with dirigeants#52.
@bdistin bdistin removed the Event: Hacktoberfest Issues and PRs related to Hacktoberfest. label Dec 5, 2017
@bdistin bdistin added this to ToDo in v1.0.0 RoadMap via automation Dec 5, 2017
@bdistin bdistin removed this from ToDo in v1.0.0 RoadMap Dec 5, 2017
@bdistin bdistin closed this as completed Dec 5, 2017
bdistin pushed a commit that referenced this issue Dec 17, 2017
* Fix the other half of #37

With #52 fixes #37 completely.

The tutorial follows a similar flow and should be a bit better than the one initially pushed with #52.

* Added behavior managing text adapted from RichDisplay tutorial

* Fix broken code from when I was testing

* Make RichMenu child of RichDisplay

* Put the tutorial on a diet

* Better wording

* Move from a random, possibly unreliable or unsafe API to known images

The images are all mine, taken during my vacation to Norway in 2016, so there should be no issues with Copyright claims or any other kind of piracy/violation.

* RichMenu tutorial is now double the code with 0% RichMenu changes

You ask I deliver (eventually) but I still think it's useless.

* fixed inconsistent/non-compliant code
@kyranet kyranet added the Bug: Fixed Issues that report bugs and have been fixed. label Jan 2, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bug: Fixed Issues that report bugs and have been fixed.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants