+ 3

When will you mark outdated information consistently?

I have noticed that you (and other sites) are presenting some information that is now outdated. Sometimes you point that out but, as with the use of appearance commands in HTML, you don't note anything. It would be valuable to know if something is really new (like only valid on ES6), newer (like valid on HTML 5 but not earlier), or old enough that we should know it but might never use it (like framesets from HTML4, which you pointed out aren't usable in HTML5), and so on. I realize that this will require some work on the part of your devs, but it is important. You could make it easier by having some sort of system that shows this sort of compatibility built into each tidbit you teach, so all you'd have to do is switch a flag's value or add new information. For example: var stillValid=false; var validInVersions=`ES6`; var supported="The <frame> tag is not supported in HTML5." And so on...

21st Dec 2017, 8:39 PM
Glenn McGrew II
Glenn McGrew II - avatar
1 ответ
+ 5
You have a point there, it is important to make a note about a lesson subject that is obsolete, non standard, or totally new, even a simple note would do just that. However, posting your suggestion here in the Q&A Discussion wouldn't be the best way to go, considering the number of new posts coming in every hour, it is easy for this suggestion to "drown" in the constant steady flow. Besides, I think they focus on app development rather than discussion, so you will have less chance to be "heard". You would be better to send them this feedback through the Feedback menu, or directly send them e-mail (info@sololearn.com) that way your suggestion have better chance. P.S. If you have sent them feedback or e-mail, then never mind this post, for next time remember to take that route instead of posting it here, direct contact is the better way : )
8th Jan 2018, 6:49 AM
Ipang