Editorial workflow pull requests are rebased if the base has
changed to ensure that asset changes on the base branch are
reflected in the PR branch, but if an asset store is in use,
no rebasing is necessary because assets are stored outside
of the content repo.
When entries were loaded for the editorial workflow dashboard, they were
all assumed to be FrontMatter/MarkDown files. This PR allows them to be
any supported format.
* rebase editorial workflow pull requests when behind
* fix async/await transpilation
* add media library pagination
* switch media library to grid layout
* ensure that only cms branches can be force updated
Adds a `delete` flag to collections in `config.yml`; fixes
#593. Defaults to false. This is mostly for use with files to restrict
users from deleting settings files etc that available via the CMS.
If the backend was changed in the config, the user from the old backend
would be passed to the new backend, which could cause errors if the
format was different.
Before, if the CMS was loading user OAuth credentials from
`localStorage`, then user write access would not be checked again.
However, the `config.yml` repo could be changed, which would cause the
user to be still logged in even if they did not have write permissions.
Also, if the user had updated their metadata (avatar, etc.), the CMS
would not update that either.
When Netlify CMS uses the git-gateway backend, it will check for a
window.netlifyIdentity
object and use that to handle the whole auth flow.
This also sets defaults for the git-gateway endpoint, that means it
can be used in templates with zero configuration and fit with a
one-click deploy to Netlify approach.
Netlify Identity itself is based on our open-source GoTrue microservice,
and Netlify's Git Gateway project is completely open-source as well.
The git-gateway backend will work with Netlify without any setup, but can
also be configured to work with any selfhosted GoTrue and Git Gateway
instances.
For example purposes, its helpful to allow users to run the test
backend without creating a repo object with nested objects for
each folder. This fix creates empty objects wherever needed.
Full stops in slugs were preventing branch creation for unpublished
entries when using the editorial workflow, as `.` is not an allowed
character in branch names. This commit changes slug generation so
periods are replaced with `-` the same way other "non-sluggable"
characters are.
* Merge conflicts automatically. Closes#208
* removed unpublished entry route
All entries (either under editorial workflow or not) go through the same edit route.
* infer card title
* Infer entry body & image
* infer image
* Better terminology: EntryListing accept a single Collection
* remove log
* Refactored Collections VO into selectors
* use selectors when showning card
* fixed size cards
* Added 'bio' and 'biography' to collection description inference synonyms
* Removed unused card file
* throw error instance
* bugfix for file based collections
* lint
* moved components with css to own folder
* Search Bugfix: More than one collection might be returned
* Changed sidebar implementation. Closes#104 & #152
* Show spinning loading for unpublished entries
* Refactored Sidebar into a separate container
* Make preview widgets more robust
* Use collection label instead of name on the CollectionPage
* Added Avatar and logout menu item
* [feat](login) Added userpic with a logout action in the dropdown.
- Display logged in user in the AppHeader
- Implemented logout action and store + tests
- Better styles for GitHub sign in screen
Closes#100
* Better styles for the AppHeader
