DEVDOCS-6233 | Content Refresh - "About Our APIs"

[bc-Vince]

Rewrote article to more closely resemble its equivalent for BigCommerce APIs

DEVDOCS-6233

What changed?

• Available APIs and resources have more descriptive information
• The article provides basic authentication information with links to learn more
• The existing request header section now covers headers and structure for requests and responses, and also discusses GraphQL-specific considerations
• There is a Resources section with helpful articles and developer support channels

Release notes draft

• As part of our ongoing content refresh for B2B Edition developer documentation, we've fully refreshed the Storefront Quotes documentation. This includes:
  • A full list of B2B Edition APIs and available resources
  • Information on authenticating and structuring API requests
  • Tables for available request and response headers

Anything else?

ping @bc-terra

[bc-terra]

Less a suggestion and more a potential conversation.
Because we aren't under the constraints of the same system as KB, we can safely use relative links for anything that lives within developer.bc and anything that lives within a specific page.

A benefit of this is that links within dev-center can be shortened to exclude the domain. It doesn't hurt to include the domain, but it is implied by the lack of domain and protocol info.

This is doubly true for on-page anchors, which can be listed with just #anchor for example.

I'm willing to go either way on this, but we should make a decision and do what we can to be consistent about it.

[bc-Vince]

Less a suggestion and more a potential conversation. Because we aren't under the constraints of the same system as KB, we can safely use relative links for anything that lives within developer.bc and anything that lives within a specific page.

A benefit of this is that links within dev-center can be shortened to exclude the domain. It doesn't hurt to include the domain, but it is implied by the lack of domain and protocol info.

This is doubly true for on-page anchors, which can be listed with just #anchor for example.

I'm willing to go either way on this, but we should make a decision and do what we can to be consistent about it.

@bc-terra Relative links and anchors without the root domain make sense to me. I tried a new method for generating the markdown in this PR, and I missed the link formatting as a result. I'll update affected links in a new commit.