search

ractivejs / ractivejs.github.io

https://ractive.js.org
8 stars 33 forks source link

Fix broken link to the Parse Object documentation #66

Closed rockerest closed 7 years ago

rockerest commented 7 years ago

~I chose to use the syntax from just below this change (the ractive.reset() link), because I feel like absolute paths are more predictable than relative paths (e.g. the template link just above).~

~That said, I can change this as necessary.~

Should meet repo standards about relative paths. It was just a filename issue.

evs-chris commented 7 years ago

:+1: Thanks!

fskreuz commented 7 years ago

There's a bunch of broken links at the moment (and mkdocs does yell when it finds them), mostly because I've been renaming sections and moving pages around. I'll be addressing them in one big sweep as soon as I finish cleaning up a few more pages.

rockerest commented 7 years ago

Sounds good. For what it's worth - and I'm presenting these facts without judgment - these kinds of broken items are raised as real concerns when choosing a view library. My company recently chose to use Ractive for production going forward, and a concern raised during our conversations was broken / incomplete documentation.

I immensely appreciate the effort that is going into the docs / Ractive in general, but keep in mind the public optics of having a lag time between the file names changing and the links to those files updating.

Regardless, our company chose to use Ractive despite that, so it's obviously a good tool :)

(edit: Ractive beat React, the other choice proposed :open_mouth: :tada:)

fskreuz commented 7 years ago

Broken links are now fixed (or at least the ones mkdocs and broken-link-checker can find). Lemme know if you find more. 😄