Make individual pages for deprecations

[jenweber]

Closes #1256

Goal:
URLS like like https://deprecations.emberjs.com/id/some-deprecation bring you to a guide about an individual deprecation

Progress so far:

[netlify]

✅ Deploy Preview for ember-deprecations ready!

Name	Link
🔨 Latest commit	2274005
🔍 Latest deploy log	https://app.netlify.com/sites/ember-deprecations/deploys/647b2f42ac71ac0007640d1c
😎 Deploy Preview	https://deploy-preview-1261--ember-deprecations.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.

[jenweber]

@mansona this is ready for review. I updated the markup to account for having a single-deprecation page with one heading, and included a breadcrumb-style link. If this passes your click test, I think it is good to go.

I think we will need to give a little README guidance about how to figure out what the individual URL of a new deprecation will be. I would like to do that as a followup PR.

[jenweber]

cc @kategengler I think this is just about ready. URLs for individual deprecation pages will look something like http://localhost:4200/id/blueprint.add-bower-packages-to-project

[kategengler]

Excellent! 🥳

[mansona]

• remove ids from all markdowns
• make sure the filenames matched all ids that were there
• add a linter that prevents anyone adding id again

for example check filename v4/auto-location.md which has an ID of deprecate-auto-location

[kategengler]

Any chance this can merge?

[kategengler]

@jenweber Wondering if we can find someone to get this over the line? Hate for it to go stale.

[MinThaMie]

@kategengler we discussed this during today's learning core meeting. @jenweber and @mansona will try to work on it on Friday!

[jenweber]

@kategengler Here's some info on where we're at and how it intersects with ember.js. Chris & I worked on this the past 2 Fridays and are getting close! We renamed files to match their ids, sorted out a file naming clash, and next up we will work on a linter for this repo to enforce the new pattern.

From a UX perspective - the pages that are in prod today will have no changes - anchor links and all that will work exactly the same, and those urls will not change. New individual page URLs will be derived from the id specified in the frontmatter (and by extension, the id mentioned in ember source).

In ember.js, we would have a few options then for simplifying the experience. Here's one of them. We could write a private wrapper in ember source that generates the link based on the URL, and lint against including url in the deprecation options. That link would go to the individual deprecation page. These improvements do not block the launch of the deprecation app improvements, since everything is backwards compatible.

Let us know if you have any thoughts on how the url is done in emberjs.

[mansona]

@jenweber I think this is working now. I removed the scripts because they didn't seem useful to commit, but I preserved them in a new branch if we need to run them again https://github.com/ember-learn/deprecation-app/tree/jw-cm-script-for-fixing-content

[mansona]

woop woop!