Discourse Discover 소개

Three days ago I fix waf block but I’m not listed yet: https://segredin.com/

4개의 좋아요

I agree. Can we get rid of the “International” category and instead add a filter to display sites by their default language? Each site could also indicate its default language with a subtle eg en or fr etc.

Maybe we could also add a country filter, for the home country of the site or if it is obviously geared towards people in a specific country?

12개의 좋아요

Filters are fun. I can’t be the only person who likes clicking on them. Adding a Country filter would allow you to highlight Discourse’s international appeal.

5개의 좋아요

Sorry, but that is really anglo centric point of view. For me English is other language :smirking_face:

8개의 좋아요

Finnish version could read: “Muut kielet” then. If the display language is in English then “Other Languages” would make sense as category for all other languages, or they could just have a list of each country/language.

1개의 좋아요

But it would actual mean ”Other languages than English, including Finnish”. That page isn’t that dynamic it would change content per language.

No big deal, only really irritating because it is always English vs. rest of the world :joy:

4개의 좋아요

At the moment, we don’t have enough sites per language to warrant a language filter. French, Spanish, Portuguese have 4-5 sites each, but the rest have one or two sites.

It’s a little tricky to label this grouping, because it includes communities in non-English languages but it also includes multilingual communities (i.e. English sites that have categories in at least one other language). A different label (other than “International”) would need to convey all that and fit in the available space on desktop and mobile.

5개의 좋아요

That makes sense. Then let’s just remove the “international” filter and let :rainbow: rainbows flourish. People can find out for themselves from the descriptions whether they can read the forum and want to be part of it.

4개의 좋아요

What wonderful forums Discourse has. :heart_eyes:
I’m looking forward to the day when my site will be added.
PVPFARM :crossed_swords:

3개의 좋아요

That page have no index tags? I cant see it on Google . :confused:

1개의 좋아요

That’s because we haven’t officially launched it yet. Once we do, it’ll be indexable by Google and other search engines.

7개의 좋아요

We’re getting to close to an official launch for this feature, and a big step in that direction is adding support for Discover in the DiscourseHub mobile app. I am happy to announce today that we have beta releases ready for the app. If you’d like to help us test the changes, please use the following links to install the beta on your device(s):

iOS (for iPhone, iPad and macOS): https://testflight.apple.com/join/4Fd4fVnI
Android: https://play.google.com/apps/testing/com.discourse

9개의 좋아요

This is amazing! I join beta Good work guys

3개의 좋아요

Is it staying on discover.discourse.org then? As this is where the button sent me and its the link in the new #announcements:blog post.

6개의 좋아요

Yes, correct, discover.discourse.org is now officially launched, that’s the final URL. (You’ll notice we’ve updated the main discourse.org website header with a link to Discover as well.)

11개의 좋아요

Congratulations for this new launch!!!

:discourse: :fire_extinguisher: :fire: :fire: :sun_with_face: :star2: :ocean:

7개의 좋아요

며칠 전에는 사소한 버그인 것 같았는데, 그 이후로는 다시 발생하지 않았습니다. Discourse의 discover 페이지에 사이트가 전혀 표시되지 않았고, 검색창에서는 커뮤니티 목록이 아닌 메타 사이트를 검색했습니다:

Contribute > Bug :

3개의 좋아요

What browser are you using @Architect ?

2개의 좋아요

Believe that was Safari

3개의 좋아요

Looks like you ran into this issue: iOS doesn't load CSS sometimes when navigating between subdomains, very much a Safari-only problem. (I and multiple other team members are running into that issue daily, though, it’s very disorienting, but not sure there’s much we can do, it feels like an upstream Webkit problem. We’ve reported it in the Webkit bug tracker, too.)

6개의 좋아요