So *if* a distinction could be made between text and block editing mode and it wouldn't take anything away from Notion's existing functionality, and the switch could be done trivially (I'm suggesting simply holding an otherwise unused key, or flipping a toggle in the UI), then why *not* have a clearer separation between block and text edit mode, to better prioritize the unique needs of each?Īhoy Oshyan! Nay bad but me wasn't convinced. The need to intermingle with text editing mode also makes some block operations clunky btw. Notion is a very capable text editor, but its block functionality also has to share UI/UX space at present, so it makes some things clunky. Now, what if you could directly interact with those blocks *as* blocks just by going into 'block edit mode'? Argh! Ever had that happen? That's because of the hidden blocks. That's a hard determination to make sometimes, and mistakes happen.

Existing systems try to decide for the user what they intend with any given interaction. As others have pointed out, other systems (like Word itself) use 'blocks', but they present them completely transparently (most of the time) to the user. But to say that having blocks means 'all blocks, all the time' is a needlessly limited way of looking at it. ^^ĭid anything I said suggest I don't want block functionality *at all*? Of course I do, otherwise I wouldn't be using Notion. Sorry to be a bit sarcastic, but after 2 years of having to work around dozens of little problems with close to no amelioration, I'm starting to be tired of excuses. Every time I do this, i loose 5 minutes and this really isn't what a productivity tool is meant for. So I have to create a new page, add my columns inside this page, go back to the previous page, turn the page I just created into a toggle list and finally I can have my toggle with 2 columns. I'm frustrating because Notion is unable to give me some of the most basic features such as decent text editing and because this forces me to waste time looking for workarounds and applying them over and over again.Īn example : I often need to create multiple columns under a toggle, but Notion forbids me to do so. I'm not frustrated because I need to come up with original ideas to build my databases, link functions and tables in a way that would make my system work or anything requiring creativity to overcome. It's their job to innovate and to create a tool that we, users, pay for. That's something you should say to Notion's teams.

For more details on the usage of Placeholder Text, you can read the documentation at W3 on Placeholders.Hahaha. The placeholder is not a replacement for labels or description text, and it is less accessible for people using screen readers. This is the text that will show on the input field when it is empty to help guide content entry. The maximum length of text to allow (default: -1), you can set it to -1 to disable the limit. This will process any that you may have in the field value. Transforms less-beautiful text characters into stylized equivalents using wptexturize().Ĭonverts text into valid XHTML and Unicode using convert_chars().Ĭhanges double line-breaks in the text into HTML paragraphs using wpautop(). Leave empty to allow all HTML tags.Įmbed videos, images, tweets, and other content using Embeds. This will let you specify which HTML tags to allow (default: strong em a ul ol li b i), enter them without the tags and separated by space. This will allow HTML tags to be rendered normally. This will remove any extra spaces before or after the field value. Trim extra whitespace before/after contents.These options will change the way your field value will display. Click Save New Field (or Save Field if you’re updating an existing field) to save your field configuration.

Select Field Type: Plain Paragraph Text.

Fill out the Basic Field Settings (Label, Description, and Field Name).

Plain text editor with paragraph