New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rename "Classic Text" to "Classic" #2956

Closed
jasmussen opened this Issue Oct 10, 2017 · 6 comments

Comments

Projects
None yet
4 participants
@jasmussen
Contributor

jasmussen commented Oct 10, 2017

Issue Overview

Whenever you load a post written before Gutenberg, or if you prefer this way of editing, you use the block currently called "Classic Text". This block is/aims to be the current WordPress editor, in block-form. It supports/should support everything the editor in WordPress today supports, but other blocks can live before and after it.

We previously called this "Freeform", it's also been nicknamed "Writer's Block" ;). "Classic Text" was given to ambiguate it from the Paragraph block which was previously called "Text".

With all the changes and the behavior of Gutenberg currently, calling it "Classic Text" seems like a disservice. Should we call it, just, "Classic"?

@iseulde

This comment has been minimized.

Show comment
Hide comment
@iseulde

iseulde Oct 11, 2017

Member

Yeah the text part seems strange as it's not just text.

Maybe even "Classic Editor" or "Classic Editor Block"?

Member

iseulde commented Oct 11, 2017

Yeah the text part seems strange as it's not just text.

Maybe even "Classic Editor" or "Classic Editor Block"?

@jasmussen

This comment has been minimized.

Show comment
Hide comment
@jasmussen

jasmussen Oct 12, 2017

Contributor

It's tricky, because although it's an Editor, it's an editor within an editor. We're also struggling with how to phrase the descriptive text as you can see in #2919.

"Classic" so far is perhaps not descriptive, but would it be more confusing to have an "Editor" be a block?

Contributor

jasmussen commented Oct 12, 2017

It's tricky, because although it's an Editor, it's an editor within an editor. We're also struggling with how to phrase the descriptive text as you can see in #2919.

"Classic" so far is perhaps not descriptive, but would it be more confusing to have an "Editor" be a block?

@androb

This comment has been minimized.

Show comment
Hide comment
@androb

androb Oct 12, 2017

Contributor

Rich Text?

Mulitparagraph?

TinyMCE?

There probably needs to be a discussion about whether It has utility beyond legacy compatibility. If so a name other than Classic would possibly help.

Contributor

androb commented Oct 12, 2017

Rich Text?

Mulitparagraph?

TinyMCE?

There probably needs to be a discussion about whether It has utility beyond legacy compatibility. If so a name other than Classic would possibly help.

@iseulde

This comment has been minimized.

Show comment
Hide comment
@iseulde

iseulde Oct 12, 2017

Member

Gutenberg is all of those too, so that doesn't make much sense? I think "Classic ..." captures it well. "Classic" sounds good to me, but I also don't see a problem with "Classic Editor" or "Classic Editor Block" as it is really an editor within an editor, and anything can be a block right? 😉 Don't see how it could be confusing, on the contrary, it illustrates the power of Gutenberg.

Member

iseulde commented Oct 12, 2017

Gutenberg is all of those too, so that doesn't make much sense? I think "Classic ..." captures it well. "Classic" sounds good to me, but I also don't see a problem with "Classic Editor" or "Classic Editor Block" as it is really an editor within an editor, and anything can be a block right? 😉 Don't see how it could be confusing, on the contrary, it illustrates the power of Gutenberg.

@androb

This comment has been minimized.

Show comment
Hide comment
@androb

androb Oct 12, 2017

Contributor

Classic is good with me if the vision for it is about backwards compatibility.

It's purpose has moved around a bit during the course of the project so if Classic still makes sense, all well and good.

Contributor

androb commented Oct 12, 2017

Classic is good with me if the vision for it is about backwards compatibility.

It's purpose has moved around a bit during the course of the project so if Classic still makes sense, all well and good.

@karmatosed

This comment has been minimized.

Show comment
Hide comment
@karmatosed

karmatosed Nov 14, 2017

Member

+1 for Classic.

Member

karmatosed commented Nov 14, 2017

+1 for Classic.

@jasmussen jasmussen added this to the Beta 1.8 milestone Nov 15, 2017

@iseulde iseulde modified the milestones: Beta 1.8, 2.0.0 Dec 13, 2017

jasmussen added a commit that referenced this issue Dec 20, 2017

Rename "Classic Text" to "Classic".
Fixes #2956.

This renames the "Classic Text" block to just "Classic", because it can do more than just text.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment