* Fix handling of displayURLs which are strings
* Add fromFetchArguments to unsentRequest
* Add parseLinkHeader to backendUtil
* Handle paginated endpoints in GitHub API
* Rename fork workflow to Open Authoring across the whole repo
* Fixes for bugs in GitHub API introduced by Open Authoring changes
* Fix getDeployPreview
* Fix incorrect auth header formatting GitHub implementation
cf. https://github.com/netlify/netlify-cms/pull/2456#discussion_r309633387
* Remove unused and broken method from GitHub API
cf. https://github.com/netlify/netlify-cms/pull/2456#discussion_r308687145
* Fix editorialWorkflowGit method in GitHub API
* Request published entry content from origin repo
* Better error when deleting a published post in Open Authoring
* Rename to Open Authoring in fork request message
Also adds a note to the fork request message that an existing fork of
the same repo will be used automatically.
* fix linting
* Make filterPromises resolve entries before filtering
* Add filterPromisesWith & onlySuccessfulPromises to utility library
* Memoize user method in GitHub API
* Make storeMetadata safe to call concurrently in GitHub API
* Fork workflow: startup and authentication
* Fork workflow: backend support
* Fork workflow: disable unused UI elements
* Fork workflow: docs
* Fork workflow: fix deploy previews
* Suggested edits for fork workflow doc
* Change future tense to present
* Fork workflow: add beta status to docs
* remove debug statement
* rename fork workflow to Open Authoring
* getting started with the contributor guide updates for Netlify CMS at WTD19PDX
* places to get involved header
* create/mimi-style-guide
initial commit
* added guide for new terms
* completed Documentation Formatting Standards
* starting headings and content for contributing guidelines
* added guide for inline code and commands
* added guide for object field names
* added guide for string and integer field values
* added guide for code snippet formatting
* added content best practices
* Updated contributor guide
* added guide for Patterns to avoid. Also added Note at the top
* Update contributor-guide.md
* Update and rename style-guide.md to writing-style-guide.md
* first draft
* minor fixes
* edits
* fixed some requested changes
* changed repo link to https
* added frontmatter section
* added note about folder structure
* fix thumbnail quality
* Revert "fix(git-gateway): fix previews for GitHub images not in Large Media (#2125)"
This reverts commit d17f896f479292db06d3a4b39f2e51b6c41101bd.
* wip
* Stop using thunks to load media display URLs
* Revert changes to dev-test
* Revert changes to large media docs
* fix lint error
* Update docs to point to the upcoming version with non-broken media
As brought up in #1711 , just using upkg lead to an issue and the documentation did not give desired result for a new user when unpkg.com had an outage. And added a comment the code mentioning that jsdelivr is also an option in case this happens again.
<!--
Thanks for submitting a pull request!
Please make sure you've read and understood our contributing guidelines;
https://github.com/netlify/netlify-cms/blob/master/CONTRIBUTING.md
If this is a bug fix, make sure your description includes "fixes #xxxx", or
"closes #xxxx", where #xxxx is the issue number.
Please provide enough information so that others can review your pull request.
The first three fields are mandatory:
-->
**- Summary**
<!--
Explain the **motivation** for making this change.
What existing problem does the pull request solve?
-->
Was going through the quick-start and noticed 404 to links
**- Test plan**
<!--
Demonstrate the code is solid.
Example: The exact commands you ran and their output, screenshots / videos if the pull request changes UI.
-->
Just simple link changes.
**- Description for the changelog**
<!--
Write a short (one line) summary that describes the changes in this
pull request for inclusion in the changelog:
-->
e.g Changed (https://netlifycms.org/docs/hello) to (/docs/hello)
**- A picture of a cute animal (not mandatory but encouraged)**
* Add hint to example admin config
* Add hint and hint position boolean above/below widget
* Style hint for both above and below widget
* Add hint and hint_above options to docs
* Remove hint above and make hint plaintext
Prettier formatting our markdown files is causing bugs because of the
differences between Gatsby's parser and Prettier's. Also, Prettier
formats the inline code-blocks containing example CMS configs, but the
formatting it uses doesn't really make much sense or match the suggested
CMS config style.
It doesn't actually make much sense to format the docs anyway, since we
use the CMS itself to edit/generate them.
* docs(add-to-your-site): include verbose document links
- add extra references to config.yml
* docs(collection-types): provide consistent examples
- include link to configuration doc
- describe admin UI behaviour when accessing files
* docs(add-to-your-site): make authentication phrasing less biased
- add note regarding core behaviour fetching remote files
* docs(collection-types): add note about configurable branches
* docs(website): add more descriptive language to configuration notes
- include deep links to documentation where applicable
* docs(website): change link titles to match their target content
When loading Netlify CMS via script tag from a CDN, the file was named
`cms.js` until 2.0, when it was renamed to `netlify-cms.js` in alignment
with all packages outputting files that match the package name. To avoid
a lot of broken sites and confusion, this commit outputs both filenames
and prints a deprecation warning to the console in `cms.js` only.
