Configurable toolbar and formatting attributes

[javan]

• API for extending and customizing the toolbar
• Documentation

[existent-ltd]

Any idea when this is likely to be merged? Waiting for this feature is blocking us from switching to Trix from our existing editor.

[HLuthi]

Same as @existent-co-uk. Any word on this?

[hmaesta]

Is this ready to use?

[Anaphase]

What's the status of this PR? Would be a great addition to an already great tool.

[javan]

I still plan on seeing this through, but don't have an ETA. #263 and #268 will come first.

[wwwslinger]

@javan #263 is merged -- what's holding back #268? Would love to get this in and have an easier way to configure the toolbar (and get the config into the editor since I'm using this in a React component, thus not the global Trix).

[joeldrapper]

Hey @javan, is there anything blocking this PR, or #268, that we could help with?

[spruce]

As it seems only the docs are missing. Is that correct? I would like to see this feature be merge soonish into trix. How can I help?

[aerosol]

Any chance of getting that merged?

[abulrim]

For people coming across this like I was, the following solution worked for me: I basically overwrote Trick.config.toolbar as defined here as such:

let { makeFragment } = Trix;
let { lang } = Trix.config;

Trix.config.toolbar = {
  content: makeFragment(`
    <div class="button_groups">
      <span class="button_group text_tools">
        <button type="button" class="bold" data-attribute="bold" data-key="b" title="${lang.bold}">${lang.bold}</button>
        <button type="button" class="italic" data-attribute="italic" data-key="i" title="${lang.italic}">${lang.italic}</button>
        <button type="button" class="link" data-attribute="href" data-action="link" data-key="k" title="${lang.link}">${lang.link}</button>
      </span>
      [...custom html]
    </div>
  `)
};

this will also give you control over the naming of the css classes in case they conflict with your code.

[adrianoresende]

PR dead? =/

[frystpingvin]

Any updates on this?

[javan]

Hello, so sorry for letting this linger, and even more sorry to say that it's not going to be merged.

We do really want the toolbar to be more customizable, but we'd like to rethink how the toolbar integrates with the editor first.<trix-toolbar> and ToolbarController are too entwined with Trix currently, and we don't want to deepen that relationship by building more on top.

Our ideal toolbar would be a standalone component that works with Trix's Editor API and/or events. That's all we know for now.

[javan]

If you're interested, let's figure out what API Trix should expose to best allow you to build your own toolbar component. I'm pretty sure Trix will always ship with a default toolbar, but the ultimate path to customization is making it easy and straightforward to BYO.

[unikitty37]

Since this has been quiet for over a year now, can somebody tell me what I can do now to customise the toolbar? Specifically, to replace the <h1> button with <h4> and <h5> buttons, and delete the <pre> button?

[auscaster]

https://github.com/basecamp/trix/wiki/Configuration