I there a way to apply a default class to an element?

Hello, first thank you for this amazing library. The question in the title is to solve a problem with bootstrap. I’d like to create a table that has already the class=“table” applyed from the start without having to add it manually from the style or property dialog. `

` this way the table is properly displayed in a bootstrap application without having to override direcly the style of table entity.

[anthonyjb]

Hi @Macs75,

Thanks for the kind words 👍 I’d recommend overriding the existing table tool to do this, for example:

class ContentTools.Tools.BootstrapTable extends ContentTools.Tools.Table

    # Insert/Update Bootstrap table

    ContentTools.ToolShelf.stow(@, 'table')

    @_createTable: (section, columns) ->
        table = ContentTools.Tools.Table._createTable(section, column)
        table.addCSSClass('table')
        return table

Another option would be to listen for the attach event and ensure the table has that class:

ContentEdit.Root.get().bind('attach', function(element) {

    // We're only interested in tables
    if (element.type() !== 'Table') {
        return;
    }

    // Add the table class to table
    element.addCSSClass('table')
});

Despite the above options I think supporting for a way to define defaults for elements when added could be very useful, so I’m going to tag this as an enhancement as well.

[anthonyjb]

@itsmelion specifically for the case in question if you wanted to rely on ContentTools to ensure rel="external,nofollow" is always in place then the simplest option would be to define your own link tool (based on the existing one but modifying the code here: https://github.com/GetmeUK/ContentTools/blob/master/src/scripts/tools.coffee#L364 to include element.a.ref = 'external,nofollow').

Links are a bit of a special case here because they’re not an ContentEdit element type they only exist as elements within the contents of a ContentEdit.Text element so there’s no simple way to set set a default for them - though I can see the need here and think this might be something to look at as a future feature.