Code samples should be stored in a repo

[rmloveland]

... and pulled into the site at build time.

This would allow us to make sure that the samples are tested via CI, so users always get working code.

There are probably many Jekyll plugins that allow for this type of functionality. I found a few with some lazy Googling:

• jekyll-code-example-tag - stores the code samples in local dirs, but we could write some magic to do a git clone and pop in some symlinks or something
• jekyll-github-sample - this appears to run client-side, which is (IMO) less ideal since now we'd have two problems. But it's an example of something that exists.

Filing this issue based on a convo just now with @BramGruneir

[jseldess]

Also just chatted with @BramGruneir about this a bit. I'm not sure it's necessary to store these in a separate repo. They're currently all separate include files, so we could already run them against proper docker images for each driver and ORM. For 2.2, let's definitely make it a docs project to automate the testing of our code samples, and as part of that, we can figure out if they should be a separate repo or not.

[jseldess]

Should be considered as part of #182.

[jseldess]

Part of #3943.

[jseldess]

This isn't going to happen in the 19.1 timeframe. Moving to 19.2 for prioritization.

[jseldess]

Moving this to 20.1 timeframe.

[jseldess]

Closing in favor of #7066.