Add first draft for info on extensions #196
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #191. Also closes #177 as this is the last sub-issue tracked by that issue.
I'm not happy about the wording yet, but wanted to suggest a first draft.
Extensions do more than what I explain in the body and in the key point at the end, but since that may change over time, I don't want to list all the potential functionalities that extensions could add or improve. @ostephens mentioned that the LC lesson has a section on extensions, but that feels too thin on information.
I summarised the discussion on adding info on extensions and alternate distributions in #177. It looks like alternate distributions are no longer featured on the OpenRefine website, so I would not bring them up.
I would love to hear from @marijane or @ostephens whether you think this is enough information. If so, I can rewrite it into easier to read text. (Or take your wording suggestions :))