Discourse Preset Topic Composer

[grubba (Gabriel Grubba)]

	Summary	Add presets to your new topic button
	Repository Link	GitHub - discourse/discourse-preset-topic-composer: preset composer
	Install Guide	How to install plugins in Discourse

Features

It adds presets to new topic button.

Here are a few images of the plugin in action:

The new topic button has two presets in this example: new question and new event

I’ve selected new question for this example; it has a tag_group to be selected, and it was added in the composer without the user having to select the bug tag.

If I try to publish this topic without selecting the tag_group it will flag that I must fill out the required fields.

When published, it looks like this:

Configuration

This plugin uses json_schema to configure it.

Here is a print of how I made new question button.

general configs:

tag group config:

tag_group can be the name of any tag group

CHANGELOG

• Init!
• Added a highlight when in URL feature that follows this pattern to highlight the button
  • it also highlights the dropdown button when it is in the same categoryId as defined in the settings.

TODO

• the composer does not behave the same when editing. Maybe this is a feature for the future

[Heliosurge (Dan DeMontmorency)]

An interesting idea. Could this be made to work with form-templates?

Ie based on template chosen for topic it automatically adds a Tag?

Definitely can see this & form-templates could be a good pairing.

[grubba (Gabriel Grubba)]

@Heliosurge

Ie based on template chosen for topic it automatically adds a Tag?

Yes!! Exactly!

[Heliosurge (Dan DeMontmorency)]

How do we target a template-form selected to automatically assign tag?

[denvergeeks]

I love this feature!

I would also like a setting to position this button in the site header!

[jrgong]

Has anyone tested it with Custom Wizard plugin yet? We have a troubleshooting category in which we require a CW to be filled out to create a new topic.

[Mr.X_Mr.X]

This would be fantastic to be coupled with this plug-in. Did anyone manage to have it working?

[Heliosurge (Dan DeMontmorency)]

I asked a similar question regarding the link below. However I suspect my post was not clear enough

Introducing Experimental Form Templates

Hello, Discourse Meta Community! We are excited to introduce a new experimental feature, form templates. With it, you can enforce a structured form with data validation as part of the topic creation flow. [multiple_form_templates] Enabling the feature The feature is hidden behind a site-wide experimental flag. To enable it, just turn on the experimental_form_templates site setting under Admin ▸ Settings. Managing the templates The form templates can be created, edited, and deleted a…

---

@grubba

@Heliosurge

Ie based on template chosen for topic it automatically adds a Tag?

Yes!! Exactly

@Heliosurge

How do we target a template-form selected to automatically assign tag?

[jrgong]

For our use case, we are mostly intrigued by the dropdown button feature.

For us it would be already sufficient to simply modify the “New Topic” button with multiple dropdown items and assign hyperlinks to each.

But I reckon, a theme component might achieve something like that, right?

[grubba (Gabriel Grubba)]

I did not know that this was a feature!

I did it from scratch and using the composer. I have not thought/tested how it would work with template form.

@jrgong

theme component might achieve something like that, right?

If the dropdown links are based on a configuration made by an admin and no backend is required(getting some data from somewhere). I think you can get this done by a TC.

[Heliosurge (Dan DeMontmorency)]

@grubba

I did not know that this was a feature!

I did it from scratch and using the composer. I have not thought/tested how it would work with template form.

My apologies for not ensuring my query was not precise. With you being part of the discourse team; I had mistakingly thought/presumed you were aware of this fairly new feature added. I should have linked the feature announcement to ensure my query had proper clarity.

I will try to ensure I do not make this kind of error in future.