Closed csobier closed 8 years ago
I thought we decided not to show any version specific links, as they are subject to change? That is why i used the more generic link. However, I just changed back to the version specific link, as instructed.
I've no issues with the introduction, but lines 72 to 90 should be removed because:
The rest is OK
Okay @fdansv , sounds good. But since this the only resource for Torque.js content, I've reworded some steps and kept the links for more advanced resource information.
Let me know if this is Okay?
@fdansv , I think I updated the tilejson example link correctly for you, please confirm. What do you want to do about the Nürburgring track map not showing any features? Shall I remove it for now?
ping @fdansv ! Can we discuss so that we can agree merge these changes?
I'm sorry but it's not that those steps are optional, they're incorrect. I'm happy to merge improvements to the guide that's already in master
, but not adding bits of the previously rejected guide that either don't add any useful information to it, make it more confusing to use the library, or are just wrong.
Okay, so what do you suggest (specifically) to be removed from this branch and what other resources are you referring to? See latest commits, I took my best guess.
I specifically suggest to keep getting_started.md
as it is in the master branch.
As per @fdansv , rejected. No additional information is required. Closing issue.
For Docs issue#644
@fdansv & @rochoa , I know you edited the Torque Getting Started section before it was published, as you didn't think the overview details and workflow needed to be defined for the Developer audience. However, the first comment in regards to the live Torque.js content was that the Getting Started was missing the required library information. I think it's valuable to include these details back into the overview section (as it is not available anywhere else in the docs). See the propose changes.