Update Library section

[josh-padnick]

This a collection of updates to the Library section.

It includes the following updates:

• Update intro page to include more concrete concepts
• Use common casing on sidebar so that all titles start with a capital and then use lowercase letters
• Use language that I've seen resonate with customers live when explaining modules
• Include an example of a module

This is ready for review, but not ready for merge. I need to give it one more passover.

[netlify]

✅ Deploy Preview for pensive-meitner-faaeee ready!

Name	Link
🔨 Latest commit	b147748
🔍 Latest deploy log	https://app.netlify.com/sites/pensive-meitner-faaeee/deploys/647f8de1f5ab010008d830a7
😎 Deploy Preview	https://deploy-preview-839--pensive-meitner-faaeee.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[eak12913]

Added one small comment but otherwise the changes make sense to me. Just let us know when you're ready for a final review.

[josh-padnick]

@eak12913 Thanks for the review! There are more changes I'd like to make, but I think we're ready to release this for now. I'm not sure how releases work here, so would you mind merging and releasing?

[ebeneliason]

@MoonMoon1919 @eak12913 Could you take a look at this and share thoughts on next steps? If everyone is on board with the changes we should get them in soon so this doesn't rot. There are some conflicts to address given the ongoing work in that section of the docs this sprint already.

[MoonMoon1919]

@ebeneliason I can take a look on Monday

[MoonMoon1919]

LGTM. Looks like you'll need to pull in latest from master -> regen the docs to get the conflicts resolved.

[josh-padnick]

Hm, I wasn't sure which hash to keep, so I kept the one on my branch. Is that the preferred behavior here? If so, this is ready to merge!

[oredavids]

@josh-padnick The hash is a computation based on the exact file content. Except you discarded all changes shown in that particular file's merge conflict; it would be best that you run yarn regenerate:local to compute the hash.

Update: I ran the command and pushed the change. @MoonMoon1919 can you please stamp again?

[josh-padnick]

@oredavids @MoonMoon1919 Thanks for the additional review. It sounds like all we need to do is merge this and deploy it. Could one of you run with that?