Browse Source

Docs: Updated editor screenshots in the documentation. Closes #869.

Aleksander Nowodzinski 7 years ago
parent
commit
9680c5d688

BIN
.github/ckeditor 5 classic screeshot.png


BIN
docs/assets/img/builds-image-styles.png


BIN
docs/assets/img/editor-balloon.png


BIN
docs/assets/img/editor-classic.png


BIN
docs/assets/img/editor-inline.png


BIN
docs/assets/img/feature-link-editing.png


BIN
docs/assets/img/feature-link-preview.png


BIN
docs/assets/img/feature-link.png


BIN
docs/assets/img/feature-toolbar.png


BIN
docs/assets/img/framework-architecture-toolbar.png


BIN
docs/assets/img/framework-quick-start-classic-editor-with-image.png


BIN
docs/assets/img/framework-quick-start-classic-editor.png


+ 3 - 3
docs/builds/guides/overview.md

@@ -33,7 +33,7 @@ In CKEditor 5 the concept of the "boxed" editor was reinvented:
  * The editor content is now placed inline in the page (without the surrounding `<iframe>` element) &mdash; it is now much easier to style it.
  * By default the editor now grows automatically with the content.
 
-{@img assets/img/editor-classic.png 772 Screenshot of a classic editor.}
+{@img assets/img/editor-classic.png 778 Screenshot of a classic editor.}
 
 To try it out online, check the {@link examples/builds/classic-editor classic editor example}. Jump to {@link builds/guides/quick-start#classic-editor quick start} to start using it.
 
@@ -43,7 +43,7 @@ Inline editor comes with a floating toolbar that becomes visible when the editor
 
 A common scenario for using inline editor is offering users the possibility to edit content in its real location on a web page instead of doing it in a separate administration section.
 
-{@img assets/img/editor-inline.png 774 Screenshot of an inline editor.}
+{@img assets/img/editor-inline.png 776 Screenshot of an inline editor.}
 
 To try it out online, check the {@link examples/builds/inline-editor inline editor example}. Jump to {@link builds/guides/quick-start#inline-editor quick start} to start using it.
 
@@ -51,7 +51,7 @@ To try it out online, check the {@link examples/builds/inline-editor inline edit
 
 Balloon editor is very similar to inline editor. The difference between them is that the toolbar appears in a balloon next to the selection (when the selection is not empty):
 
-{@img assets/img/editor-balloon.png 779 Screenshot of a balloon toolbar editor.}
+{@img assets/img/editor-balloon.png 789 Screenshot of a balloon toolbar editor.}
 
 To try it out online, check the {@link examples/builds/balloon-editor balloon editor example}. Jump to {@link builds/guides/quick-start#balloon-editor quick start} to start using it.
 

+ 3 - 2
docs/builds/guides/whats-new.md

@@ -24,7 +24,7 @@ Inserting images into the content is now very intuitive, with all technical aspe
 
 The outdated concept of image alignment was dropped in favor of {@link features/image#image-styles image styles}:
 
-{@img assets/img/builds-image-styles.png 591 Image styles toolbar.}
+{@img assets/img/builds-image-styles.png 736 Image styles toolbar.}
 
 When integrated with {@link features/image-upload#easy-image Easy Image}, uploading, resizing and producing different image sizes for responsive design is all automated.
 
@@ -34,7 +34,8 @@ When integrated with {@link features/image-upload#easy-image Easy Image}, upload
 
 No more complex dialogs for links.
 
-{@img assets/img/feature-link.png 503 Simplified link dialog.}
+{@img assets/img/feature-link-preview.png 738 Simplified link preview popup.}
+{@img assets/img/feature-link-editing.png 738 Simplified link editing popup.}
 
 ### Autoformatting
 

+ 1 - 1
docs/framework/guides/architecture/ui-library.md

@@ -279,7 +279,7 @@ document.body.appendChild( toolbar.element );
 
 The result should look like this:
 
-{@img assets/img/framework-architecture-toolbar.png 442 A simple toolbar created using existing components.}
+{@img assets/img/framework-architecture-toolbar.png 636 A simple toolbar created using existing components.}
 
 The toolbar renders correctly but it does not do much. To execute an action when the button is clicked, a listener must be defined. To shorten the code and instead of two listeners define just one, the buttons can {@link module:utils/emittermixin~EmitterMixin#delegate delegate} the {@link module:ui/button/buttonview~ButtonView#execute `execute`} event to their parent:
 

+ 1 - 1
docs/framework/guides/quick-start.md

@@ -185,7 +185,7 @@ Finally, it is time to create an HTML page:
 
 Open this page in your browser and you should see the editor up and running. Make sure to check the browser console in case anything seems wrong.
 
-{@img assets/img/framework-quick-start-classic-editor.png 837 Screenshot of a classic editor with bold and italic features.}
+{@img assets/img/framework-quick-start-classic-editor.png 976 Screenshot of a classic editor with bold and italic features.}
 
 ## Creating a simple plugin