In Chrome, the editable part of the editor gets outlined on focus. It looks like buggy because of it. Better to style it to be disabled.

At this moment there's no way to include past and current changelog entries, which is required since CKEditor v0.2.0.

It would be great if we could avoid zoom when the user taps inside the editor demo on iPhone.

There is a chance that, if we set font size in the editing are to 16px, it'll not zoom. Me may give it a try and see if it works and if it will still look good.

As far as I can see, this worked well for the demo in http://ckeditor.com.

The new features implemented in 0.3.0 should have their showcase in the sample.

Related to #16.

Because it gives 2x smaller builds than transpilation to ES5 and Uglify.

This is the home page now: http://ckeditor5.github.io/

And the documentation will be a part of this website. This means that:

1. You must be able to open docs from the home page and vice versa.
2. The both pieces should look like one website.
3. We need to integrate these pieces in terms of the building process.
4. We'll need a new skin for JSDocs (TODO).

Ad 1

This can also be derived from 2. – those pages should share the same (or similar) heading. Home page must link to docs and docs to the home page.

Ad 2

Not only should those pages share the menu, but also stylistics. @RyszardB proposed this for the home page:

The top menu is quite similar (of course colors are totally different, but the rest should be the same – size, fonts, margins, etc.).

To not complicate this too much for now (because we'll be reworking this in the future anyway), I'd propose that:

1. On the home page we have 4 links in the menu "Documentation" and the socials "GitHub", "Like Us", "Follow Us" (but I'd consider adding icons there).
2. On the documentation page we'll have "Home page" + "Samples" + "Guides" + ...

I'd prefer if we had exactly the same buttons in the menu in both cases, but the above should be easier to develop, because we won't need to think about grouping things.

Also, I'd like to have social buttons also in the documentation part of the website, so perhaps this means that we should convert them to icons without text (to squeeze more in one place).

Ad 3

This simply needs to be developed. Building, linking, pushing to this repo and also backuping the previous version under releases/ directory. The whole script should land in this repo.

Ad 4

This requires a separate ticket. We shouls approach this in two steps – first at least add a header to the existing JSDoc theme and later on work on a brand new theme. I'll report respective tickets.

I.e. to avoid wrapping "5" in CKEditor 5 to the new line, which looks odd.

https://en.wikipedia.org/wiki/Non-breaking_space

Things to consider:

• clipboard feature
• finally we can use unicode emojis
• autoformat feature

Following #2, the logo got messed up. IMHO it is way too big, but the really important point is that the "TM" mark is not aligned :/

Currently, it is pretty noticeable the delay on creating the editor in the website. You can even clearly see the ugly editor contents before it is replaced:

I'm not joking – it can be missed, because "Developer Preview" is much bigger.

Besides, I'd consider changing the line "Developer Preview" to "CKEditor 5 v0.1.0 – Developer Preview", although if the logo becomes bigger that may not be necessary any more.

Related to #16.

As the logo (TM) is getting messed up #2, we came to the idea to remove it at all and leave only the plain text headline. There is no final CKEditor 5 logo, so doesn't the TM really fit there before the 5.

Proposal:

The default font (used everywhere in the text, in the editor and in the footer) is so light that it's hard to read. It barely renders on low-dpi screens.

First alpha version 🎉🎉🎉
Find out more in the CKEditor 5 v1.0.0 first alpha blog post

links to https://ckeditor5.github.io/TODO which results in 404

can't wait to read it^^

congratulations to the first alpha!!! 🎉🎉🎉🎉🎉🎉🎉🎉🎉 👍 👍 🥇

Requires #8.

This is incomplete:

            try {
                ClassicEditor.create( document.querySelector( '#editor' ), {
                    toolbar: [ 'headings', 'bold', 'italic', 'undo', 'redo' ]
                } );
            } catch( e ) {
                _.showCompatibilityMessage();
            }

The code should also .catch(). The .create() method may only throw directly if Promise is not available (which will be true on IE11), so for safety we can use both – try-catch and promise catching.

BTW. to make some debugging easier (and we'll use this website for that maaany many times), it'd be good to publish the editor instance globally:

ClassicEditor.create( document.getElementById( 'editor' ), {
                toolbar: [ 'headings', 'bold', 'italic', 'undo', 'redo' ]
} )
.then( editor => {
    window.editor = editor;
} )
.catch( err => {
    console.error( err.stack );
} );

It links to ckeditor/ckeditor5-design#179 instead of ckeditor/ckeditor5-design#180.

Since https://github.com/ckeditor/ckeditor5-build-classic is ready we can use it directly.

https://github.com/ckeditor/ckeditor5-editor-inline/issues/1 brings another type of editor, and considering the history of CKEditor, it's a key feature that people would like to see and try.

Shouldn't we showcase it somehow? If yes, then how?

AFAICS, loading Google font is blocking rendering:

It's not a critical issue at the current stage, but this is a thing that we must keep in mind.

PS. I've noticed that because Google's CDN was lagging for me and I didn't see anything.

Described here: ckeditor/ckeditor5#460

This ticket is required for:

We should also add the entire docs directory to ignored paths in robots.txt because we don't want to have this documentation crawled. It will be available under a different URL once we go with the final release and it's not worth dealing with some redirects from GH pages.

Requires/follow–up of: ckeditor/ckeditor5-theme-lark#62

https://github.com/CKEditor5/ckeditor5.github.io/blob/master/docs/nightly/ckeditor5/latest/_snippets/samples/classic-editor/snippet.js

https://ckeditor5.github.io/docs/nightly/ckeditor5/latest/_snippets/samples/classic-editor/snippet.js gives 404.

I think we may be hitting some github.io limitation or something.

The new feature – image. Would be good to have one there, in the content, nicely styled, etc.

Other than that, no big changes.