Skip to content
Last updated
Danger

Training exercise.

Experience review

What made you smile?

We've finished training smoothly. We remembered about sidebars.yaml file so it wasn't a problem to configure it. We've also worked with remote content before so configuring it wasn't hard.

What did you find confusing?

  • When added new remote content under Kitchen API it took a while to refresh editor and show new remote content folder. It would be great to have some loader/indicator that shows user that remote content is being added/synchronized.
  • After remote content has been added and once we've added sidebars.yaml file, WYSIWYG was not showing anything in Kitchen API for us. Navigating there would show empty pages. We've had to commit changes, go to preview page and then navigate back to editor to get it working. (On Preview everything was fine)
  • When making deployment for main branch and going to deployment build details page (with build logs), publish step was in infinite loading state, while project was actually published.
  • PR for remote content should be already Ready for review
  • We're not sure why it's possible to edit remote content files. Since they will be overwritten on next sync anyway and changes are not being propagated to upstream repository.