A few edits were made to the wiki after docs.ractivejs.org was set up; now that the wiki has been killed off, those changes have been nuked and need to be manually readded:

• https://github.com/RactiveJS/Ractive/wiki/_compare/1e6f995b8a101d9cfb794ca56c8a99724e39c0df...7ae38088c8f123642e148738914db72777e07303
• https://github.com/RactiveJS/Ractive/wiki/_compare/faa3eb11cfad6badb3a815065f797c1892c7559e...1e6f995b8a101d9cfb794ca56c8a99724e39c0df
• https://github.com/RactiveJS/Ractive/wiki/_compare/cdbffaf9a2f06bb277f37da23fb90d8c562bf2c9...faa3eb11cfad6badb3a815065f797c1892c7559e

See this comment

See ractivejs/ractive#543

Do we just copy the 4.0 folder to a new 4.1 folder?

Do we freeze changes to 4.0 and just make them in 4.1?

left-nav class is only visible if the page is > 48em. This makes anything but the getting-started page inaccessible

ractivejs/ractive#670

On the GitHub wiki, it was possible to link to sections of a page by appending a hash - the relevant anchors were auto-generated. That's no longer the case

ractivejs/ractive#429

There's a registry of adaptors. But then you have to opt-in to using the adaptor with adapt?

Maybe because adaptors are highly invasive in that everything gets run through them?

None of the other registries works that way...

I read through all of the Ember.js Docs and liked how at the end there was in the in depth dive that explained all the internals. Would be cool to document the various portions of Ractive. The parser, renderer, the run loop, maybe a few other things.

see ractivejs/ractive#747

...or which need a bit of a general tidy up:

• Ractive.events
• Plugins
• Events
• API Reference
• Preparsing
• Ractive.toHTML()
• Using Ractive with Backbone

Also, some methods don't have documentation yet e.g. ractive.findComponent() and ractive.findAllComponents()

Do off have map also?

See ractivejs/ractive#731:

<input on-change-blur="event"/>

Missing documentation
"Pattern observers - observe e.g. items[*].status"
https://github.com/RactiveJS/Ractive/blob/master/CHANGELOG.md

Realized as of #583 on ractive repo that this isn't documented in partials.
Components need some love, maybe a simpler example to start and then the more in depth example that is currently there.

Are you opposed to the docs potentially having a completely new look. Things seem very dispersed all over. Was thinking about making an API section that would dive into all the functions for everything, much like the API.reference you have now. Then splitting it off into getting started/docs/concept stuff etc.This would all have some sort of left side based nav.

See ractivejs/ractive#540 - webpack compression causes issues with Ractive, as it lowercases tag names (which may in fact be mixed-case components)

http://docs.ractivejs.org/latest/events

'Standard events' no longer include 'set' or 'update'. I think that's probably for the best, but the whole thing needs a bit of an update and clarification. See ractivejs/ractive#423

The tips page (http://docs.ractivejs.org/latest/tips) says 'add stuff to the wiki' which won't exist for much longer

These correspond to the files in https://github.com/RactiveJS/Ractive/tree/master/src/Ractive/prototype:

• ractive.add()
• ractive.detach()
• ractive.insert()
• ractive.findComponent()
• ractive.findAllComponents()
• ractive.render()
• ractive.reset()
• ractive.subtract()
• ractive.toggle()

Lots of pages currently seem to be orphaned - as in, they can be visited, but nothing links to them. Examples include the "Tips" page and most of the "Using Ractive.js with..." pages.

From discussion in ractivejs/ractive#493.

Mention delimiters option somewhere and also that you probably shouldn't use it.

See ractivejs/ractive#712

See ractivejs/ractive#541

We should probably move over to doing {{#if foo}}...{{/if}} in examples rather than {{#foo}}...{{/foo}}, now that it's supported (ractivejs/ractive#770).

Link the Tips page in the main nav, probably Introduction. Make sure linked pages are up-to-date.

"Event plugins" page is effectively empty but linked to from "Events". Change links to be to "Writing event plugins" and flesh that page out (note TODO).

Also the "Plugin APIs" link on the "Plugins" page is a 404.

Still thinking about how to implement this, concept isn't hard but would like a consistent theme throughout the site. So probably going to pull code/style from examples page and run with that.

Ractive.adaptors, Ractive.easing, and Ractive.events are not linked from the main nav or any other page. @Rich-Harris or @martypdx, is there any reason this might be?

see ractivejs/ractive#653

see ractivejs/ractive#693

See ractivejs/ractive#659

from https://github.com/RactiveJS/docs.ractivejs.org/blob/master/docs/0.3.9/Ractive.transitions%20(global).md:

A few standard transition functions are included 'out of the box', such as fade. (Pull requests welcome!)

This is no longer true, all transitions live as separate plugins

Note existent but orphaned page Legacy builds, and PR #30

are out of date, see ractivejs/ractive#378. The data option can be an array.

http://docs.ractivejs.org/latest/initialisation-options

...inside functions that are referred to by expressions.

So, I added a way to preview edge docs online. Basically I set up an edge alias that points to 0.4.1 docs and templates.

Don't make edits in the 0.4.1 folders of master!. Edits happen in the 0.4.0 folders of the dev branch. Reason being that we can merge in master changes that happen in 0.4.0.

The process is to periodically make a copy of the 0.4.0 from the dev branch (I added a gitignored copy folder), switch to the master branch and copy that folder to 0.4.1 then push to github. Not exciting, but best I could come up with.

See ractivejs/ractive#364 (comment).

see http://stackoverflow.com/questions/23437039/why-does-my-component-not-get-its-parents-data-unless-specified-in-ractivejs/23438750#23438750

See ractivejs/ractive#418. All the links on http://docs.ractivejs.org/latest/using-ractive-with-backbone are broken

Then we could just have a live editor component...

see https://groups.google.com/forum/#!topic/ractive-js/ZFL1JKok6k0

and link are broken for
ractive.transitions
ractive.partials
Ractive.partials
Ractive.transitions
in http://docs.ractivejs.org/latest/api-reference

A tips is to connect google webmaster tools. It can tell what pages are broken after it have crawled the pages.

or see http://www.brokenlinkcheck.com/

same appears to be true of transitionsEnabled init option

See ractivejs/ractive#405