간소화된 카테고리 설정

[lindsey (Lindsey Fogle)]

Whether you’re new to Discourse or looking to expand your existing community, we want to make it easy for you to create categories to support meaningful conversation. To that end, we’re introducing a significant improvement to the category creation process, which should make this process easier for most use cases, while still allowing for more advanced configuration where required.

In this topic, we’ll review the major changes and share how you can start using this simplified system today.

What’s changed

Let’s walk through some of the changes to category creation.

Old category creation, for reference

1. Focused fields

With our goal of making typical category creation simpler, we’ve trimmed down this initial page to just the bare essentials.

2. Updated color selection

The new color selector (i.e. dropper button) shows the background color and the text color. ^[1]

We’ve also tucked away the suggested colors and previously selected colors (indicated by a checkmark) because we felt these added noisiness to the category creation page.

3. Improved style inputs

The Style inputs were tidied up to take up less space, while making the various options (i.e. Icon, Emoji, or Square) more visible.

4. Simple access controls

Discourse offers a lot of flexibility around category access, but we wanted to give you a simple version to cover most use cases. With this new system, you can easily decide between:

• Public access, so everyone can see, create topics, and post replies ^[2]
• Private access, where you specify the group(s) that should be able to see, create topics, and post replies

If you need more flexible permissions, the quick link points you to the advanced settings area (see next section!) where you can adjust access.

5. Advanced settings access

For most categories, you should have everything you need on this main page. However, if you need access to all the various settings we have to offer, select the Advanced settings toggle to expose all the extra options.

Most of this is unchanged, with two exceptions:

• Category slug has moved from the main page to the Settings tab.
• Text color has moved from the main page to the Appearance tab.

Turning on simplified category creation in your community

For now, this is considered an experimental change! We’re welcoming your feedback, which will help us make improvements so that this can soon become the new default experience for category creation.

To turn this on, head to the Upcoming changes page in your admin area (/admin/config/upcoming-changes) and find the Enable simplified category creation item. Update the Enabled for… field to opt your site in to this new design:

Note: This Upcoming Change item doesn’t change who can create categories — if you set it to “Everyone”, only admins (and moderators, if you have enabled moderators manage categories and groups) will see it since they’re the only ones who can create categories.

What do you think?

We’d love to hear what you think of this new category creation process. Did it make creating a category easier? Are there any other improvements you think we could make here to keep making this process simpler?

---

1. We automatically set to either white or black based on what’s most accessible on your selected background. You can set your own text color on the Appearance tab, shown when toggling on Advanced Settings. ↩︎

2. To be precise, everyone who can see your community and everyone who can post topics / replies in your community can do so in this category. If your community is private, any logged-in user can see and post topics / replies in the category; if your community is public, any site visitor can see the category, but only logged-in users can post topics / replies in it ↩︎

[loginerror (Maciej Kuźmicz)]

It looks really nice; it’s a really nice quality of life change.

I have a question about how others are creating categories, though. For me, I practically never create a category that will be public right away. This is because, by default, a new category contains this “About the category” topic that doesn’t have much in it and is mostly a placeholder for further changes.

I only make the category public once that About the category topic is ready to go.

Maybe it’s just my own flow, but I’m curious if anyone can relate to that.

[sren-1]

Thanks for your efforts. It looks really nice and could be beneficial if you just want to create a category for immediate use. However, how often does this actually happen in an admin’s daily workflow?

Focused fields, access controls, and advanced settings access:

In fact, all the important settings are now hidden by default. From my point of view, these settings are the bare essentials.

Color selection, style inputs:

Nice

[lindsey (Lindsey Fogle)]

@loginerror

I only make the category public once that About the category topic is ready to go.

Interesting, makes a lot of sense, too. We can look into making that easier to accomplish from the category itself so you don’t have to go back-and-forth.

@sren-1

In fact, all the important settings are now hidden by default.

This is helpful to know, thanks for sharing. When you are creating a category, what fields do you typically update?

[putty]

This is great!

@lindsey

Category slug has moved from the main page to the Settings tab.

So if someone doesn’t dig into the Settings tab, is the slug just derived from the category name (swapping spaces for hyphens)?

[sren-1]

@lindsey

When you are creating a category, what fields do you typically update?

The following settings are mandatory:

General
Category name
Category slug

Styles
Style
Color

Security
Group: See, Reply, Create

Settings
Position on the categories page

Images
Category logo image

I usually review this later to ensure it’s correct:

Localizations
…

[lindsey (Lindsey Fogle)]

@putty

So if someone doesn’t dig into the Settings tab, is the slug just derived from the category name (swapping spaces for hyphens)?

Yep, exactly. That’s how it worked previously too, it was just more front-and-center, which we felt was too much prominence for something we didn’t anticipate most communities were editing.

[jordanjay29]

@lindsey

@lindsey

These are the biggest advancements for me. Is this color picker going to be added to Discourse for plugin/component devs to make use of as well? It would be great to have that wherever color is being asked for, whether custom or by Discourse from the start.

[awesomerobot (Kris)]

@jordanjay29

Is this color picker going to be added to Discourse for plugin/component devs to make use of as well?

It’s available for use within formkit forms… here’s where it’s used in category creation:

frontend/discourse/admin/components/upsert-category/general.gjs

…but it hasn’t been made available for use outside of forms.

We also have a couple separate admin components, ColorInput and ColorPicker, which we should consider unifying at some point as well.

[jordanjay29]

Would be a useful add to BBCode/toolbar plugins and the new color features of Tag Icons, etc. Old members of my new site are confused why there’s no color picker they’re used to from previous software.

But I digress…as far as category creation goes I turned this on and gave it a try. About the only thing I find less simple the way that Private permissions wind up being a little oversimplified necessitating a trip into the advanced settings anyway. I really like the streamlined approach otherwise!

[gormus (Osman Görmüş)]

@awesomerobot

We also have a couple separate admin components, ColorInput and ColorPicker, which we should consider unifying at some point as well.

Would be great to see if this component enabled for theme settings objects too

[stephtara (Stephanie Booth)]

Haven’t tested yet but it really looks like it’s going in the right direction to me!

[gormus (Osman Görmüş)]

I noticed that after enabling this feature, I noticed that the Tags tab settings are not preserved.

Specifically the Restrict these tag groups to the ‘…’ category and the Require new topics to have tags from tag groups settings.

I had tag groups defined in those fields. After enabling this experiment, those fields were displayed empty.

Strangely though, saving the form as it looked empty, didn’t remove the previously set configuration, didn’t reset the configuration. The fields still looked empty.

[Moin]

https://github.com/discourse/discourse/pull/37591

[RGJ (Richard - Communiteq)]

@lindsey

이 새로운 카테고리 생성 프로세스에 대해 어떻게 생각하는지 듣고 싶습니다. 카테고리를 만드는 것이 더 쉬워졌나요?

왜 이것이 '카테고리 관리’가 아니라 '카테고리 생성’이라고 불리는지 모르겠습니다.
어쨌든, 꽤 훌륭한 단계라고 생각합니다. 몇 가지 추가 수정이 있다면 정말 훌륭할 것입니다.

@lindsey

이 프로세스를 더 단순하게 유지하기 위해 여기에서 더 만들 수 있는 다른 개선 사항이 있을까요?

이것은 더 일반적인 Contribute > UX 토픽에 속할 수 있습니다. 그렇다면 이 게시물을 거기의 새 토픽으로 이동해 주시면 됩니다.

제 의견을 말씀드리겠습니다:

"Security"를 "Permissions"으로 이름 변경

보안(Confidentiality, Integrity, Availability)은 훨씬 더 넓은 개념이며, 무섭고 기술적으로 들립니다.

"Settings"를 "Advanced"로 이름 변경하고 오른쪽(마지막 위치)으로 이동

모든 탭이 설정입니다. 이 탭만 그런 것이 아닙니다. 그리고 그것은 저에게 도움이 되지 않는 매우 일반적인 용어입니다.

“Moderator approval” 설정을 “Permissions” 탭으로 이동

"모든 새로운 XXX에 대해 관리자 승인 요구"를 Permissions 탭으로 이동하세요.

기능 요청: 더 세분화된 관리자 승인

모든 항목에 일괄 적용하는 체크박스 대신, 생성/답변에 관리자 승인이 필요한 특정 그룹을 지정할 수 있다면 좋겠습니다.

"Category slug"를 "Appearance"로 이동

그것이 바로 그것에 관한 것이기 때문입니다.

"카테고리 페이지에 표시되는 주제 수"를 "Appearance"로 이동

그것이 바로 그것에 관한 것이기 때문입니다.

더 많은 도움말 텍스트 추가

• 템플릿은 안내가 없는 에디터일 뿐입니다.
• 모든 설정 옆에 작은 팝업을 표시하는 아이콘이 정말로 도움이 될 것입니다. 특히 Settings Advanced 탭은 매우 압도적일 수 있습니다.

“color”, “style” 및 미리보기가 함께 속해 있음을 명확히 함

이 세 가지는 현재 "Category name"과 “Subcategory of” 사이에 있지만, 시각적으로 그룹화되어 있지 않습니다. <fieldset>에 <legend>를 사용하여 묶으면 훨씬 더 명확해질 것입니다.

모든 탭에 플러그인 아웃렛

api.registerEditCategoryTab은 매우 환영할 만하지만, 기존 탭을 확장할 수도 있으면 편리할 것입니다. 모든 탭에 “Create” / “Save” 버튼 바로 위에 플러그인 아웃렛이 있는 것은 아닙니다.

• Security, Settings, Appearance에는 있습니다.
• General, Template, Chat에는 없습니다.

General의 경우, 고급 모드인지 여부를 지정하는 인자가 있을 수 있습니다. 또는 고급 모드를 위한 하나와 항상 표시되는 하나, 두 개의 아웃렛을 가질 수도 있습니다.

탭별 아웃렛 외에도, 탭을 인자로 전달하는 추가적인 범용 아웃렛이 유용할 수 있습니다.

[nathank (Nathan Kershaw)]

I second everything that @RGJ just said!!!

[awesomerobot (Kris)]

All solid observations, we’re planning on doing a lot of this…

@RGJ

All tabs are settings, not just this one

Right this tab kind of became a dumping place for everything, including plugin extensions… a lot of it can be spread out

@RGJ

These three are now between the “Category name” and “Subcategory of” but they are not grouped visibly. Putting them in a <fieldset> with a <legend> would make things a lot more clear.

We’re going to try to combine all of these, possibly something like this

[RGJ (Richard - Communiteq)]

@awesomerobot

possibly something like this

Ohhh I like that!!! Awesome!

[newkid (Chris)]

Now using the category setup. Much easier than before. Easier to use on the mobile app. I always applaud any help to make using Discourse easier. Thanks team