Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Redirect / to /organize #1826

Open
joe-irving opened this issue Mar 14, 2024 · 2 comments · May be fixed by #1917
Open

Redirect / to /organize #1826

joe-irving opened this issue Mar 14, 2024 · 2 comments · May be fixed by #1917
Assignees
Labels
🚪 entry-level Good for newcomers 🐟 Small Should be a quick-ish fix. 📥 user-request

Comments

@joe-irving
Copy link
Collaborator

Description

When getting new organisers into Zetkin gen 3, it has been tricky to describe the process of logging in. Logging in has actually been one of the biggest onboarding issues for the platform so far

Steps to reproduce

  1. Go to app.zetkin.org

Expected Behaviour

  1. Go to app.zetkin.org
  2. Get directed to app.zetkin.org/organize
  3. Log in
  4. Organise some amazing things

Actual Behaviour

  1. Go to app.zetkin.org
  2. Try to work out how to log in
  3. Get lost
  4. Give up on Zetkin and the left

Suggested solution

Add temp redirect on next release to /organize if possible. I think adding this line in the root page would work

redirect("/")

but i don't know Next that well. Thank you xx

@richardolsson
Copy link
Member

I'm fine with making this change, as long as we mark it as a temporary redirect (HTTP 302 Found, not HTTP 301 Moved Permanently). Once we have the activist portal in Gen3, it will live here (with easy to find links for organizers to log in).

@richardolsson richardolsson added the 🐟 Small Should be a quick-ish fix. label Mar 17, 2024
@kizouker
Copy link

kizouker commented Apr 8, 2024

I'm on it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🚪 entry-level Good for newcomers 🐟 Small Should be a quick-ish fix. 📥 user-request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants