Docs/finish migration from loopback.io

[shimks]

There are a couple of stray pages that haven't been migrated and updated over to the monorepo. The PR fixes this

• brings over commits made from Feb 23rd to Mar 15th, 2018.
  • docs(faq): add Crafting LB4 link loopback.io#634
  • docs(cli): add extension generator page loopback.io#636
  • docs(boot): Docs for @loopback/boot loopback.io#631
  • lb4: fix usage of Context#get to specify type loopback.io#637
  • Move RestServer config out of async start loopback.io#621
  • docs: fix links in Booting an Application loopback.io#640
  • docs: add extension generator on cli page loopback.io#642
  • Update Memory-connector.md loopback.io#638
  • Add best practices for bottom up approach loopback.io#624
  • Update Testing your application loopback.io#635
  • docs(boot): Move boot docs to top level loopback.io#644
  • loopbackio/loopback.io@2de9395
• first commit is the actual migration itself
• second one changes hyperlinks from .html to .md
• third commit migrates over the sidebar and the CLI tables

Checklist

• npm test passes on your machine
• New tests added or existing tests modified to cover all changes
• Code conforms with the style guide
• Related API Documentation was updated
• Affected artifact templates in packages/cli were updated
• Affected example projects in packages/example-* were updated

[b-admike]

This is great; Thanks for updating them @shimks! I was able to verify that you captured the new files that were added when deleting all the content in loopback.io (see loopbackio/loopback.io#643 (comment)) and using the script I've been working on to pull the changes from the monorepo as they are now.

[virkt25]

@b-admike what changes need to be made to the scripts (if any) that pull in LB4 if we are going to move the lb4_sidebar.yml into the docs folder here?

[b-admike]

@virkt25 it'll just be to move them to their appropriate place, so that references are not broken. Also, @shimks what do you think about moving https://github.com/strongloop/loopback.io/blob/gh-pages/pages/en/lb4/includes/CLI-std-options.md?

[shimks]

@b-admike I think I want to keep that where is; it's not a file that needs to be changed frequently, and if we do need to change it, we can deal with that when we need to. Speaking of, we may need to componentize or comment your code in update-lb4-docs.js so that it's easier to modify or add other specific files for anyone that may need to add to the script in the future.

[b-admike]

Fair enough. I've added comments to the script as you suggested, PTAL :-)

[shimks]

@raymondfeng Can I get you to sign off on this before I merge it? Thanks

[b-admike]

On second thought, I'd like us to keep all site related items inside docs/site (i.e. lb4_sidebar.yml and tables). That also means changing the include blocks in command-line-interface.md to

{% include_relative tables/lb4-artifact-commands.html %}

[bajtos]

I did a quick review and didn't find any obvious problems. As far as I am concerned, this patch LGTM.

Please address comments from other reviewers before landing.

[shimks]

@b-admike I agree. l'll make the change

[shimks]

Could I get a clarification as to why we need to make the change to include_relative? Is it even possible to parse this html stuff in github? If so, is this accounted for in your PR so that it changes it back to {% include content/lb4-project-commands.html %}?

[b-admike]

Oh it's because right now they are included from the top level of loopback.io and are inside _includes/content, but I want us to have the tables in pages/en/lb4/includes/tables and include them from there instead. I want to be consistent in where we keep LoopBack 4 related site stuff on loopback.io. What do you think?

[b-admike]

Once we hash out the details in this PR, I'll push up the changes to incorporate what we've done here.

[shimks]

That sounds good to me, I'll make the changes.