Fix link to extending.md

[ryanclarke]

The ".md" filetype was missing from the link path.

[danielpost]

Thanks!

EDIT: Actually, just wondering. Should it be the full link (https://github.com/netlify/netlify-cms/blob/master/docs/extending.md), the way we currently have it in intro.md? Not sure if it makes a difference.

[erquhart]

A root relative path is better, actually, same way I did it in my latest PR. Not sure if we have a consistent approach across the docs.

[erquhart]

@ryanclarke thanks for this! I'm now wondering if there are other links where this is happening.

The problem here is that the repo docs are used to generate the docs site. The repo needs .md, but the docs site needs the extension left off. We'll need to determine the right approach. We're using Markdown Magic in the docs repo, maybe it's just a configuration thing.

Another option is to simply remove the extension from the files themselves, but we'll consider that a last resort.

[erquhart]

So here's what I'm seeing:

• The docs site is our primary documentation, so we should leave links without extension so they continue working there
• To fix links within the docs, we'll probably need to write a Markdown Magic plugin on the docs site repo to transform .md extension links.
• Once the plugin is in place, this PR will be eligible for merge. Any similar links should be updated at that point as well.

We may also consider other means for transforming source repo docs to html, but a quick search did not reveal anything promising.

[verythorough]

We can likely look to the docs implementation used by Serverless, primarily coded by @DavidWells, who also created Markdown Magic.

They keep docs in the repo, as in this page (note the link at the bottom points to an .md file)
https://github.com/serverless/serverless/blob/master/docs/providers/aws/guide/installation.md

Then use those files to generate the main site, as in this page (with no extension on the last link)
https://serverless.com/framework/docs/providers/aws/guide/installation/

I don't think they use Markdown Magic as a separate entity, but have it integrated into the code (before MM was broken out). Code for content importing and conversion can be found in here:
https://github.com/serverless/site/tree/master/scripts/docs

[erquhart]

@verythorough good find - the conversion happens here: https://github.com/serverless/site/blob/master/scripts/docs/update-doc-content.js#L55

[erquhart]

This will be properly fixed under #511. Closing.