About the village pump notifications, I am thinking we may need to do a bit more thinking here in terms of what might be most useful and technically feasible to show. Is it the title of the most recent topic in the discussion, or is it the occasional notifications (milestone related) that the starter kit might push to the village pump? Or for MVP, just link to the village pump of the wiki. And only show this tab if the village pump exists on the wiki. I am leaning towards the latter for the MVP.

I also noticed that in "Recruit native speakers" we have multiple platform options to share messages. We might want to think this through carefully as well - what is actually most relevant to show. We could potentially drop Twitter & Email completely for the MVP.

For the mentors list, perhaps we could look at how Growth features handle this. There is a list of mentors maintained at Special:ManageMentors for every wiki. For Hindi, see here. To begin with, it could be a simple global list of mentors. For MVP, we could add mentors involved in the Language Diversity Hub initiative after obtaining their permission.

I've made some changes to the prototype to reflect these comments. Take a look here.

toluayo opened https://gitlab.wikimedia.org/repos/lpl/starterkit-v1/-/merge_requests/30

Add Community and collaboration card

ngkountas merged https://gitlab.wikimedia.org/repos/lpl/starterkit-v1/-/merge_requests/30

Add Community and collaboration card

As discussed offline, the mentors list used by Growth features is mainly for our internal reference. For the starter kit, we may want to build a separate list of our own. For the MVP, this could be a simple list to begin with that includes a few mentors. It might also make sense to host this on the test wiki for now, similar to how other starter kit templates are set up.

Earlier, I had suggested adding members from LDH, but after digging a bit more, it seems that group might be fairly small. I also came across Let’s Connect skills, and while I’m not sure how active it currently is (I can check), it feels more relevant than the Growth mentors list. The Growth list is tied to a more specific use case, with mentors signed up for particular tasks, whereas the skills directory is broader and categorized and using it may not require obtaining permissions from listed mentors. Some categories there could be more useful than others. It also looks like this work may now be evolving into CapX, which might be worth exploring further:

https://meta.wikimedia.org/wiki/Grants:Knowledge_Sharing/Connect/Skills_Directory
https://capx.toolforge.org/

From @JStephenson: The Let’s Connect project is being decentralised to exist in community based spaces, such as hubs and networks. All the registration and profiles have migrated to CapX, and this is the main tool we are using to search for people by skills, organisation, language, project, etc. I think CapX would be a very powerful tool for this purpose. The Capacity Exchange skills list was based on the Let’s Connect one, but is constantly being extended based on community feedback and partnerships with peer learning/mentorship programmes. CapX also created a mentorship feature precisely to make those connections you are looking for. I can set up a call with Amanda from CapX so she can run through how it works and see how to integrate your specific needs.

toluayo opened https://gitlab.wikimedia.org/repos/lpl/starterkit-v1/-/merge_requests/46

Bug: T423409

ngkountas merged https://gitlab.wikimedia.org/repos/lpl/starterkit-v1/-/merge_requests/46

Make village pump tab on community and collaboration card dynamic

toluayo opened https://gitlab.wikimedia.org/repos/lpl/starterkit-v1/-/merge_requests/56

Seperate specialist link and Village pump implementations

ngkountas closed https://gitlab.wikimedia.org/repos/lpl/starterkit-v1/-/merge_requests/56

Seperate specialist link and Village pump implementations

Documenting what we learned from CapX project team members.

1. CapX does have an API that allows for programmatic access to profiles and their associated capacities. You can retrieve a list of profiles filtered by specific capacities such as tools, technology, Incubator, outreach, etc. This would allow you to surface those results on your external platform like the Starter Kit. It is hosted on https://capx-backend.toolforge.org/ and it is structured with OpenAPI 3.0 specification, so it is as open as possible.

2. For interactions, you can indeed direct users back to CapX for connecting via the messaging features, or even use the API as a Service (APIaaS) to facilitate communication between your platform and CapX. This way, users can seamlessly connect and interact without leaving your platform entirely.

@ToluAyo I see that there are following capacities available in CapX:

Wikimedia tools, Technology, Editing, Wikipedia, Incubator, Templates, Gadgets, Community engagement, Community development, Workshop, Training, Outreach, Technical support, Mediawiki, Wikimedia incubator, Wikipedia, Wikimedia bot, Wikimedia gadget, Pywikibot, Mediawiki userscript

For now, I think we can use these for filtering, and in the future, have a dedicated capacity specifically for the Starter Kit.

A few minor things I noticed in the design.

The font of the description should be the same as the description font in Essential Tasks. Right now it appears bold.

Also, in the mockups, you will notice that the height of the Community & Collaboration box is similar to the height of the Essential Tasks box.

I also noticed that the communication venue text is appearing in red (e.g., Telegram channel), while in the design it is gray.

I am guessing the implementation for the recruit native speakers / mentors module and adding the link to the Telegram channel for LDH is still in progress. Also, how can we test the village pump feature?

toluayo opened https://gitlab.wikimedia.org/repos/lpl/starterkit-v1/-/merge_requests/67

Feat: implement mentor fetching logic from CapX for community/collaboration card

Thanks @srishakatux for the comment.

Regarding the feedback for the design, they're currently in progress and are being addressed, which includes the implementation for the recruit native speakers button.

And to test the Village pump feature, it can be tested by specifying a live wiki as a target wiki.

toluayo merged https://gitlab.wikimedia.org/repos/lpl/starterkit-v1/-/merge_requests/67

Feat: implement mentor fetching logic from CapX for community/collaboration card

toluayo opened https://gitlab.wikimedia.org/repos/lpl/starterkit-v1/-/merge_requests/73

Add functionality to Recruit native speakers button

ngkountas merged https://gitlab.wikimedia.org/repos/lpl/starterkit-v1/-/merge_requests/73

Add functionality to Recruit native speakers button

toluayo opened https://gitlab.wikimedia.org/repos/lpl/starterkit-v1/-/merge_requests/75

Fix community card UI

ngkountas merged https://gitlab.wikimedia.org/repos/lpl/starterkit-v1/-/merge_requests/75

Fix community card UI

toluayo opened https://gitlab.wikimedia.org/repos/lpl/starterkit-v1/-/merge_requests/84

Add redirect links to relevant CTA buttons/strings in Community card

ngkountas merged https://gitlab.wikimedia.org/repos/lpl/starterkit-v1/-/merge_requests/84

Add redirect links to relevant CTA buttons/strings in Community card