Write a new vignette about teal_data

[gogonzo]

Since TealData is deprecated, we should no longer teach in the vignettes about this class. So we have (at least) two altnernative solutions:

• remove vignettes describing all (unwanted) ways of specifying data
• state in the old vignettes that their content is deprecated

There should be new vignettes:

• teal_data class and it's methods and idea behind @gogonzo
• Reproducibility check
• join_keys vignette #202
• using teal_data in teal application (this should be in teal)
• how to migrate from TealData to teal_data and from tdata to teal_data @vedhav

[chlebowa]

How about flag the old vignettes as archival and have a mention in the new one that other ways existed in the past?

[vedhav]

I'm leaning towards not showing vignettes about the old stuff. As a user, I will be overwhelmed with a lot of deprecated stuff in the vignettes. Alternatively, it will be nice to place all the depreciated vignettes in just one navigation selection, my worry is that this will still make it available for search and easily mislead someone.

[m7pr]

If we do support depracated functionality I would leave vignettes with a warning that they refer to the deprecated functionality. Once the functionality is removed I would opt for vignettes removal. The same way we keep manual pages for deprecated stuff.

[kartikeyakirar]

Keeping old vignettes might be helpful if someone migrating from old to new , currently, we still support some of the old functionality, so it might be beneficial to retain the old vignettes with a disclaimer or warning.

[gogonzo]

Keeping old vignettes might be helpful if someone migrating from old to new

So we need extra vignette - "Migrate from TealData to teal_data"

[m7pr]

So we need extra vignette - "Migrate from TealData to teal_data"

yeah, that would be the best!