사용자 포트폴리오

:discourse2: 요약 User Portfolio는 사용자 프로필에 새로운 “포트폴리오” 탭을 추가합니다. 특정 카테고리 및/또는 태그의 사용자 토픽을 표시하도록 설정할 수 있습니다. 또한 Topic List Thumbnails 와 함께 훌륭하게 작동합니다.
:hammer_and_wrench: 저장소 링크 https://github.com/discourse/discourse-user-portfolio
:open_book: Discourse 테마를 처음 사용하시나요? Discourse 테마 사용 입문가이드

이 테마 컴포넌트 설치

기능

사용자 카드에 포트폴리오 버튼을 선택적으로 추가할 수 있습니다:

설정

이름 설명
포트폴리오 카테고리 포트폴리오 카테고리 ID. 모든 카테고리에 대해 0으로 설정
포트폴리오 태그 포트폴리오 태그
포트폴리오 아이콘 포트폴리오 탭 및 사용자 카드 버튼용 아이콘
포트폴리오 섬네일 스타일 포트폴리오 페이지용 섬네일 스타일 (discourse-topic-thumbnails이 설치되고 활성 테마에 추가되어야 함)
사용자 카드 포트폴리오 링크 사용자 카드에 포트폴리오 링크 표시
포트폴리오 순서
포트폴리오 라우트 이름 URL 내 포트폴리오 페이지 이름, 예: /u/username/activity/porfolio
번역 기본값
portfolio 포트폴리오
empty_portfolio 이 포트폴리오는 채워지기를 기다리고 있습니다
empty_portfolio_link 토픽을 추가하여 시작하세요

:discourse2: 우리가 호스팅을 담당하나요? 테마 컴포넌트는 Standard, Business, Enterprise 플랜에서 사용할 수 있습니다.

46개의 좋아요

This is terrific! :partying_face:

4개의 좋아요

Fantastic component! I’ve long looked for something to make profiles more expressive.

However, thinking about implementing it, one thing is holding me back: I think it would be necessary for users to have more control over what appears on their portfolio. With edits and deletions of posts limited, that’s difficult.

Any idea how to solve this? (Making all posts in the portfolio category wikis could be a solution, though not ideal.)

2개의 좋아요

One option to give users more control is a ‘portfolio’ tag which they can apply to their posts. But you’re right, they can’t remove it later without edit privileges. Wikis are a good workaround.

Any changes to editing permissions wouldn’t be possible in a theme component, so we’d have to explore a core change or a plugin to make it possible.

6개의 좋아요

Actually this feature has been in the Topic List Previews plugin since Oct 2019 and was carried over into the TLP Theme Component:

https://meta.discourse.org/t/topic-list-previews/101646/660?u=merefield

8개의 좋아요

Hi David,

Is that possible somehow to add more category to filter the portfolio? I try to add more tags but it not work for me. If I set up category: 0 and add more tags the portfolio gone empty.

Thank you :slightly_smiling_face:

1개의 좋아요

Great component.

I don’t understand which you mean by Category ID. Is the internal ID number of the category from which to take the posts of the user into account?

It should be much useful to be able to select several categories by its name, like in topic thumbnails TC.

It would be great to let each user to select from which categories he wants to show messages in his portfolio, overriding general default (if the admin allows it).

Another great improvement would be to add an option to let the admins select in the Component config which user groups can have a portfolio (based in level, or whatever admins stimate).

Another great addition It will be a great way to create a personal gallery not just from posts in has published in a category.
To get that, some kind of per user private category should be implemented, where users can create their posts and show them in the profile.

3개의 좋아요

Hey! Loving the plugin, it’s been integral to our website for years.

One issue however, normally we’re able to filter through posts on the website by sorting them via creation date instead of reply date, utilizing the parameters for it: ?order=created

The portfolio seems unable to replicate this behavior, though I’m sure under the hood uses a simple query that should have access to this feature. Is this something you would be able to add?

3개의 좋아요

Amazing component, thank you!

I think it can also be much more than just a user portfolio tab, it can be repurposed as almost anything you want to associate with users within the forum. The community I host is based on a policy/resource library and I’m using this component to show everyone which policies/resources were created by each user. I guess in a way that is a portfolio, but somehow the word implies something visual (especially given the integration with the topic thumbnail plugin/component and the image at the top of this thread).

With that flexibility in mind, it would be amazing to be able to change the URL slug (I’ve edited the title to Policies but the slug stays as u/user/activity/portfolio

It would also be great if the user_card_portfolio_link was hidden if the portfolio is empty.

3개의 좋아요

Agree on having category names to select from, it took me a little while to hunt down the ID of a subcategory.

1개의 좋아요

Bug report: The .portfolio-link in the .user-nav needs to be wrapped in a <span>, so that the label text is hidden for tablet/mobile along with the other user-nav entries, otherwise it just sits there like a :lemon:

2개의 좋아요

Thanks for the feedback everyone !I’ve just made some updates to address some issues and add some features:

https://github.com/discourse/discourse-user-portfolio/pull/12

More than 1 category isn’t easily possible at the moment (though we’re working on some features for this in Discourse in general so maybe someday) — but I did notice that it was only working for 1 tag (despite the setting input allowing multiple)… so this update allows multiple tags to be used to populate the portfolio.

I’ve added a setting for this called portfolio_order so now you can choose created as an option as well.

I’ve added a setting called portfolio_route_name that will allow for this. Note that unless you know what you’re doing with URL encoding, it’s best to stick with a single word for this and avoid spaces and special characters.

I looked into implementing this, but there’s not a great way to do it. To know if it’s empty we’d have to fetch topics whenever someone’s usercard is opened, which is a little bit of a heavy request for a usercard (a plugin could do this in a much more efficient way by adding a field to the user data server-side with a simple count of portfolio topics)

this has been fixed

3개의 좋아요

First of all, thank you so much for taking the time to implement it. This would be such a hugely requested feature for our site. I just pulled the latest commit and changed the setting, but it doesn’t seem to be working. Is there anything I’m missing? Does Discourse need to be restarted?
image

2개의 좋아요

Hmm you shouldn’t need to restart (though you’d need to refresh the page if it’s already open)

It works for me on my test site…

For example, ordered by latest activity:

ordered by most recently created:

2개의 좋아요

Yes! Sorry, my bad, you’re absolutely correct. I’m using another plugin under the name of Topic List Thumbnails that unfortunately sometimes doesn’t wrap properly, making it seem out of order. But it’s working perfectly. Thanks so much again!

2개의 좋아요

Thank you for all these fixes, amazing!

What are the options for making such a plugin, is this something that would be considered by Discourse or should I just post a marketplace topic, or something else?

3개의 좋아요

Is it possible to add a second category at this point?

Also, how could we implement “multiple” portfolios? For example, we would like to have a general portfolio tab for all users. But for our B2B users, we would like to add a “Products” tab instead.

We might be interested in funding those features if the implementation is not too complex.

1개의 좋아요

It would be interesting if this covered another use case:

https://github.com/paviliondev/discourse-journal

This great but poorly marketed plugin gives people control over topics they create, so they can track content like DIY projects and so on. Other users can comment on the threads but their comments are reduced in scope so its folded beneath each entry.

It would be cool if your plugin could pull from multiple entries in the same thread, not just a top level image. In other words, to build the portfolio, it might use all of the images from one thread, or only the first and last entries, and so on.

4개의 좋아요

We are actually using a custom-made plugin which uses the latest image posted by the topic author as thumbnail. We mainly use it with topic list thumbnails, but the user portfolio tc should be affected the same way.

@RGJ can we open the plugin for public use?

3개의 좋아요

It’s here GitHub - communiteq/discourse-topic-thumbnail-recent-post · GitHub
Please note that it only works for journal topics.

3개의 좋아요