ER: Issue with Public Facing Slack Channel Links for Non members #6129
Labels
Complexity: Large
Complexity: See issue making label
See the Issue Making label to understand the issue writing difficulty level
ER
Emergent Request
Issue Making: Level 2
Make issue(s) from an ER or Epic
P-Feature: Getting Started
https://www.hackforla.org/getting-started
P-Feature: Project Info and Page
A project's detail page (e.g. https://www.hackforla.org/projects/100-automations)
P-Feature: Projects page
https://www.hackforla.org/projects/
role: front end
Tasks for front end developers
size: 0.25pt
Can be done in 0.5 to 1.5 hours
Milestone
Emergent Requirement - Problem
Prospective members might have been attempting to join slack channels via public facing links. Since they aren't members they are unable to join.
Issue you discovered this emergent requirement in
Date discovered
1/17/24
Did you have to do something temporarily
Who was involved
@bonniewolfe @djbradleyii @nelsonuprety1
What happens if this is not addressed
Prospective members might attempt to join these slack channels, but will be unable to due to the fact that they are not members resulting in a poor user experience. This might deter potential members from reaching out or associating with HackforLA.
Resources
Screen Shot of Community of Practice Slack link
Recommended Action Items
Potential solutions [draft]
Make an issue to determine the technical feasibility of the below
if the issue is feasible, do we have to make unique pages, or can we do it dynamically. If we can do it dynamically, then go ahead and execute. If we need separate pages, write-up how it would work and make a template for making each page, then get sign-off by dev lead and product.
Using an Iframe, and deliver a page that says
and then has a unique link for the team's slack link they just clicked on
[INSERT TEAM SLACK LINK NAME or CoP NAME THAT WILL LINK TO TEAM/CoP SLACK LINK THAT YOU JUST CAME FROM]
Add this resource to the issue and whatever resources from above that are applicable.
Resources
The text was updated successfully, but these errors were encountered: