Textpattern CMS support forum

You are not logged in. Register | Login | Help

#71 2015-10-28 14:15:47

gaekwad
Admin
From: People's Republic of Cornwall
Registered: 2005-11-19
Posts: 2,633

Re: Improved Text Editor Capability

Destry wrote #296281:

DITA

Dang. That takes me back. I used to use that daily at my previous proper job – back when it was a pure IBM thing.

Offline

#72 2015-10-28 14:17:01

michaelkpate
Moderator
From: Avon Park, FL
Registered: 2004-02-24
Posts: 1,214
Website

Re: Improved Text Editor Capability

jakob wrote #296265:

Choosing a cms from the current A List Apart. I suspect, like a lot of CMSes, txp hits some buttons and misses others. The interesting bit in this context is the section on the author experience… (but made suddenly trendy by calling it AX)

I thought the first comment was interesting:

I have competely given up pushing Markdown to clients. It has, without exceptions, resulted in users finding the whole CMS experience un-intuitive. Even though I can make a very good technical argument for using it. Currently I avoid defining any wysiwyg-fields whenever possible. But when styling is needed I will allow a small set of WYSIWYG buttons (bold, italic, linking, headings). For example when an author wants to add an internal link to a body text it is hugely more reliable to provide a WYSIWYG tool with the ability to browse the site structure than first teach Markdown and then teach how to form internal links. – mscore

Offline

#73 2015-10-28 17:45:46

sacripant
Plugin Author
From: Rhône — France
Registered: 2008-06-01
Posts: 478
Website

Re: Improved Text Editor Capability

if you finally decide to implement a core solution (Textile button bar or anythink else) please considere :

  • The solution can be desactivate manually or by plugins (all : Html markup, Javascript etc.) for user don’t want that.
  • The solution can be activated for all text fields (custom fields).
  • The solution can be extended or modified by plugins and/or prefs (php and JS API).

And why not a official plugin, maintained by core team ? Nobody answered about it.

Last edited by sacripant (2015-10-28 17:46:58)

Offline

#74 2015-10-28 18:12:37

colak
Admin
From: Cyprus
Registered: 2004-11-20
Posts: 7,381
Website

Re: Improved Text Editor Capability

Sacripant has a good point but I also think that if a solution is implemented it could be added as a “new tab” in the “write tab”.

ie. We currently have the “edit article text”, “view html markup” and “preview article”. From them we – for many years now – can only use the “edit article text”.

For those who use plugins, the “edit article text” is changed so as to add the desired functionalities.

The feature idea here is to make them all editable so as to be able to move from one to the other when content is created. As such the “preview article” tab could become the WYSIWYG editor regardless of what script will be used to implement it. This feature could indeed be enabled or disabled in the preferences especially for those designers who might not want to give access to any direct html editing facilities to their clients.


Yiannis
——————————
neme.org | hblack.net | LABS | State Machines | Respbublika! | NeMe @ github

Offline

Board footer

Powered by FluxBB