디스커스 코어에서 블로그가 필요하지 않은 7가지 신화

기여 기능
1

I’ll try to dispel the myths that discourse doesn’t need a built-in blog. I believe that abandoning a blog in the core of discourse carries more negative consequences than blog in discourse. There are dozens of topics on this page where users wonder why discourse doesn’t have a built-in blog. For more than 5 years, users have been searching for blog functionality in the forum!

1. Discourse doesn’t need a blog at all.

Your competitors will be happy. Without a blog, we lose traffic and visitors. All forums have articles. Basically it’s the instructions and quick start guide. Instead of writing them as forum topics, it would be much more correct to design them in the form of a blog. The Invision Community developers were wise. They added the blog to the core and now it has become their advantage over other forums.

2. You can use wordpress or another platform. Using Discourse instead of WP comments is a good way to drive blog traffic to your forum.

Yes, but we spend our time and money installing and constantly maintaining two platforms instead of one. And this applies not only to wordpress, other platforms are even more complicated. Instead of one successful project with good SEO indicators, we get 2 projects with unpredictable indicators. Instead of one platform, users visit 2 platforms, the traffic of each platform is lower than one, the positions in search engines fall and the traffic becomes even lower. We lose traffic, not attract it. Your competitors are happy again) At the same time, we lose the ability to conduct collective blogs and other advantages, such as the use of tags, PUSH notifications. Our PWA doesn’t work for blogs! Wordpress has redundant functionality, we need a few database lines and a few MB of code. Unfortunately, wordpress is not an Easter cake from which you can cut a piece.

3. Wordpress is better for writing blogs.

Are you serious? We don’t know that yet. The developers of discourse are cool guys, they will tear up wordpress or something else with their eyes closed.

4. Blogging in the core of discourse will complicate the platform.

We live in the 21st century, everything is complicated here. The blog module is not artificial intelligence. A blog is the simplest thing you can add. But it is easier to write a whole module for integration with WordPress to pull useless ballast on the subdomain. It’s a step back. 20 years ago, such a decision would have been correct, but not now. How much will the blog module for discourse weigh? How many tables will appear in the database? I will answer: a little. I don’t expect a blog to have millions of posts. But if you have millions of posts, then I will congratulate you.

5. Forums can be flooded with spam links.

Assign trusted people, not everyone. Instead of developing the community, we need to pull the ballast in the form of an ancient blog on wordpress. We need to be distracted by blogging on our own. We lose the opportunity to use the creativity of the community to write great articles. There may be many members of the community can write free blogs better than us.

6. Discourse and blog are designed for different purposes.

The blog is needed to attract traffic. Guess what the forum needs for its development?

7. It can be much easier for users to scroll through and read only blog posts than to be distracted by all the content created by users on the forum.

In the creepy way that discourse is used as a blog engine, I agree. Many ways have been devised. It’s simple, you need a separate module with its own navigation and page. Making posts from forum topics is equivalent to making posts from chat messages. I’ll give you an example of invision community, although they have a terrible design. It is very convenient to add comments, likes, tags, a subscription to news, a link to a product from an online store, etc. to a blog post. From such posts, it would be wiser to build wiki pages. In reality, you can find more advantages, but for now, this is enough.

When choosing an engine for my community, I needed a built-in blog and I really didn’t want to look for another platform, as I liked discourse. I really hope that the developers will hear our requests and help make this wonderful platform better.

8개의 좋아요
4

I agree- blogs are a very useful tool to share expertise, engage members and draw in new traffic. The posts also don’t get lost in everything else as you already mentioned.

So did they do away with blogs here? I dont see any, I think it would be valuable to resurrect.

2개의 좋아요
5

Is Page Publishing anywhere close to what you are looking for: Page Publishing? I’m interested in using it as the end point for a collaborative writing project, but haven’t got too far with the details of that yet.

6

Use news plugin

7

Oh. Not to offer… content?

SEO-wise I get way more better response from Google and DuckDuckGo from WordPress than Discourse. Sure, that could be fixed but as long a blog means some layout tricks in this context.

A blog needs quite more than layout fix. Just only meta-needs are different.

BTW, Discourse works already as a blog platform. I’ve using it that way a long time now. But when, not if…, I have an article that is not tied closely to purpose of my forum it will be published via WordPress.

Comment section of blogs are perhaps the second most overrated thing in the webistan. SEO-tricks are number one. Most of blogs get never comments, neither those few would give any value.

Sure — it would expand use of Discourse. Quite many would use Discourse for everthing, but would that be a smart move? I don’t think so. It is always better to do one thing really good than everything in mediocre way.

There is only one thing missing in Discourse: working way to change look of a blog writing.

And even that is not that big question because visitors… just don’t care as long they can read that text easily and without beggins for signing up to a mail letter.

Basically you are now saying choise to do blogging is missing but for me: how is that missing?

The editor… it is so limited that I don’t want create anything else here than just pure text with few images. It works perfectly in forums (well, almost perfectly because something like 99 % of the world can’t markdown, html or bbcode but it just doesn’t matter because majority never use formatting).

You just make a demonstration how to blog using Discourse. What tools did you miss?

1개의 좋아요
8

For me to understand… Discourse still is (awesome) Forum Software and isn’t becoming a CMS, right?

I’m using a blog, build with hugo, cause it’s fast. Comments are possible with Discourse and automatically linked to the Forum. (Same way as Discourse is doing it with blog and meta.) So I got the best of both worlds.

Comments are rarely used, but possible. And reading the Blog in the Forum too.
And people who read a blog aren’t necessarily the same people who want to be active in the forum and vice versa.

9

I’d be interested to know what your tactics are.

And generally, I’d be interested to know what a blog feature would look like. How is it different from what I have now? What does it allow? What does it forbid?

1개의 좋아요
10

질문을 완전히 이해하지는 못했습니다 — 무슨 뜻이신가요?

꽤 쉬운 전술이 있습니다: 긴 글을 쓰는 것입니다. 그것뿐입니다. 여기 OP(게시글 작성자)는 실제로 블로그 포스트를 썼습니다(여기서 블로그라는 말은 요즘 의미하는 바, 즉 일기나 로그만이 아닌 것을 의미합니다).

아니면, 제가 언제 디스코urses(Discourse)를 사용하고 언제 워드프레스(WordPress)를 사용하는지 묻는 건가요? 글쎄요… 그것은 상황에 따라 다릅니다. 그리고 그것은 플랫폼 자체의 이점이나 한계에서 비롯되는 것이 아닙니다.

저에게는 워드프레스의 편집기를 사용하는 것이 디스코urses가 제공하는 것보다 훨씬 쉽고 효율적입니다. 왜 그런지 완전히 이해합니다(기사 작성 vs. 빠른 일상적인 포럼 게시물), 하지만 그것이 영향을 미칩니다. 워드프레스에서는 로컬 링크를 훨씬 쉽게 만들 수 있습니다. 적절한 플러그인을 사용하면 테이블 사용 측면에서 워드프레스는 디스코urses가 제공하는 매우 기본적이고 수동적인 마크다운보다 우월합니다. 워드프레스에는 실제 미디어 라이브러리가 있지만, 디스코urses에는 그것이 전혀 없습니다. 초안(Drafts)… 글쎄요, 그 길은 아예 가지 않겠습니다 :wink:

그럼에도 불구하고 저는 디스코urses를 블로그 플랫폼으로도 사용합니다. 하지만 오직 다음 경우에 그렇습니다.

  • 일기/로그 유형의 글을 쓸 때
  • 대화를 기대할 때 (디스코urses는 어떤 솔루션을 사용하더라도 워드프레스의 댓글 기능보다 압도적으로 좋습니다)
  • 좋은 검색과 태그 기능이 필요할 때 (워드프레스가 제공할 수 없는 것)

저는 주로 세 가지 유형의 글을 씁니다:

  • 개 관련 글: 이 글들은 워드프레스에 게시합니다. 해당 사이트가 정말로 강력한 SEO 가치를 가지고 있기 때문입니다.
  • B2B/기술 관련 글: 여기서는 워드프레스와 디스코urses를 50/50으로 사용하며, 주요 이유는 대화를 기대하는지, 아니면 단순히 사실과 아이디어를 전달하는지에 대한 기대치 때문입니다.
  • 하이킹/패들링 이야기: 디스코urses에 게시합니다. 워드프레스는 추가 가치를 전혀 제공하지 않고, 대화를 얻을 "위험"이 높기 때문입니다.

즉, 저에게는 어떤 전략도 없습니다. 글쎄요, 아마 하나 정도는 있겠죠. 공유와 클릭을 최대화하려고 할 때는 항상 워드프레스를 사용합니다. 제 언어권에서는 사람들이 포럼 링크를 클릭하는 것을 별로 좋아하지 않는 것 같습니다. “일반적인” 사이트가 더 쉽습니다.

왜 그런 걸까요? 저는 모릅니다. 아마도 디스코urses의 외관이 조금… 지저분하다는 뜻은 아니지만, 모바일에서 약간 혼잡해 보일 수 있기 때문일지도 모릅니다. 핀란드에서는 몇 년 전 데스크톱 판매가 급감했고, 거의 모든 사람이 모바일을 사용하고 있습니다. 이는 모든 것이 모바일 퍼스트로 설계되어야 하고, 데스크톱은 개발자가 여가 시간이 있을 때 다뤄야 한다는 것을 의미합니다 :wink:

또는 사람들이 타블로이드 신문들의 저질 댓글 때문에 포럼을 싫어하는 걸까요? 아니면 소셜 미디어가 이 전쟁에서 이긴 걸까요? 아니면 포럼(모든 포럼)은 모두가 싫어했던 블로그 허브의 일종의 에코를 주는 걸까요? 아니면… 저는 아무것도 모릅니다. 하지만 아마도 포럼은 댓글을 기대하지만, 모바일로 작성하는 것은 즐거운 일이 아니기 때문일 수 있습니다 — 워드프레스 기반 사이트는 단순히 읽기를 제공하기 때문입니다.

다시 말을 돌리지만, 모바일은 제가 저질 콘텐츠라고 여기는 것들, 예를 들어 한 줄 댓글, GIF 등에게 주요 이유입니다. 어딘가에서는 그것들이 원하고 환영받지만, 저는 다르게 생각합니다. 그리고 저만이 아닙니다. 포럼 링크를 보면 그저 오래된 농담을 보여주는 반짝이는 GIF와 트위터 스타일의 짧은 댓글만 가득할 것이라는 기대가 있을 때… 누가 그곳에 가겠습니까? 그리고 다른 측면에서 — Google이 모든 포럼을 Q&A 기술 또는 고객 지원 환경으로 본다면, 포럼의 검색 결과를 표시하는 방식이 변할 것입니다. 그 포럼이 Q&A나 지원이 아닌 다른 것이라면, 그렇게 매력적이지 않을 수 있습니다.

아니요. 저는 디스코urses를 비난하지 않습니다. 하지만 아마도 관리의 편의성 때문에 모든 것을 하나의 플랫폼에서 하려고 하는 것을 그만두어야 할까요? 아마도 우리는 모든 측면 — CMS, LMS, 포럼, 이커머스… — 이 필요하며, 그것들은 다른 플랫폼에서 제공되어야 하고, 디자이너가 그 모든 패키지가 어떻게 보일지 말하게 한 후에 코더들이 그들의 마법을 부리게 해야 할지도 모릅니다.

하지만 제 핵심은 디스코urses가 콘텐츠를 생성하고 게시할 수 있는 모든 플랫폼과 마찬가지로 블로그 플랫폼이라는 것입니다.

모더레이터 — 이 주제를 #contribute:feature에서 #community-building으로 옮기는 것이 좋을까요?

(죄송합니다 — 이상한 문법과 오타가 많을 것입니다… 영어는 꽤 기이한 언어입니다)

11

That’s what I was implying in a discussion Discourse vs Invision. I used to run a blog on WordPress, and I almost hated it mostly because the engine was too overloaded with features stemming from the approach: “let’s build 1000 features, knowing that an average user will employ at most 5%, but at least we’ll be appealing to audiences that span distinct 5% partitions”.

Also,

one, okay, I, could argue that it’s precisely WordPress that ruined blogs on the internet. Within few clicks, every author has a SEO optimization plugin which tells you how you should artificially construct your blog so that it’s not too short, not too long, has at least N references to keyword and blah blah blah. And of course which adds a stupid “sign up to my unnecessary newsletter” banner.

Anyway, back to the topic. Part (or maybe that makes up 100%) of what makes Discourse great is the ability of developers to focus on what they deem essential, not trying to accustom all possible niches.

1개의 좋아요
12

There are certainly people already using Discourse as a blog, and more commonly as the comment engine of their blog.

To keep this on the topic of new features, what new features would Discourse need to better support blogging?

2개의 좋아요
13

Now there is a news plugin, it is developing well. I think it works great as a blog

14

Thanks - that was interesting. As you say, one can always just write a long post, and then if it gets replies, or not, that’s very like a blog.

In what way is it not like a blog, I wonder? Well, perhaps

  • there’s no specific way to link to previous/next posts (threads) by one person
  • no specific way to see all of a person’s posts
  • no calendar view of a person’s posts
  • no person-specific tagging for their own set of posts.

But all these seem - to me - fairly small usability aspects. We do have tags, and searches, and categories. And it’s easy enough to link from one post to another.

15

There’s the Portfolio feature introduced by Topic List Previews that allows you to see all Topics by a User tagged with a specific tag or within a specific Category and accessed from a button on the User Card.

So you could have a tag called blog … and rename the button “User Blog”

I seem to recall a feature having been built to cover this recently … but it’s not currently supported by TLP …

2개의 좋아요
16

I reckon it is mostly just layout question. Blog post styling component would keep most of users happy. But last time I checked it doesn’t use DiscoTOC — because it erases timeline. Or I remember totally wrong.

I would use docs but there is one major layout issue.

There is some meta-tricks that would tell to Google what is purpose, but I think it goes over the scope of Discourse. Again — from my point of view Discourse should stay as a damn good forum platform.

It doesn’t understand tags. It needs category. I understand totally that because its main purpose is show news, not blogs.

1개의 좋아요
17

That I use. All blogs are tagged blog and name-of-the-blog. It works just fine. Well… almost fine because every now and then there is needs to show in publishing date order. But that is not real question mark, more like .would be nice to have.

Portfolios… I’ve forgotten that totally. Thanks.

2개의 좋아요
18

거의 3년 만에 이 글을 다시 읽게 되었습니다. 현재 커뮤니티 사이트에는 워드프레스 블로그와 몇 개의 정적 페이지가 있습니다. 커뮤니티 자체는 페이스북에서 운영되고 있으며, 곧 디스코스로 이전할 예정입니다. 따라서 이런 문제가 생겼습니다. 워드프레스 블로그를 메인 페이지로 유지하고 워드프레스로 정적 페이지도 관리할까요(이 부분은 주로 대외적으로 노출되는 콘텐츠입니다)? 그리고 디스코스는 서브도메인으로 운영할까요? 아니면 메인 도메인에 모든 것을 디스코스로 통합할까요? 그리고 제 질문은 이렇습니다. 만약 후자를 선택한다면, 디스코스에서 ‘블로그를 메인 페이지로 사용하는’ 구조를 재현하는 방법이 있을까요?

블로그 게시물을 위한 별도 카테고리를 설정하고, 저만 게시할 수 있도록 할 수 있습니다(하지만 일반 대중은 댓글을 달 수 있을까요?). 그리고 커뮤니티에는 다른 메인 페이지(예: /support/)를 제공할 수 있습니다. 하지만 이렇게 하면 깔끔하게 작동할까요? 아직까지도 이 부분을 제대로 파악하지 못했습니다.

1개의 좋아요