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

Make non-profit status more explicit #1511

Open
ArtOfCode- opened this issue Jan 11, 2025 · 2 comments
Open

Make non-profit status more explicit #1511

ArtOfCode- opened this issue Jan 11, 2025 · 2 comments
Assignees
Labels
area: frontend Changes to front-end code complexity: easy Issues that should take limited effort to resolve/fix/build. priority: medium status: in progress This is being worked on type: change request New feature or request

Comments

@ArtOfCode-
Copy link
Member

meta:293270

Our non-profit status should be more explicit, particularly when we're promoting the organisation or asking for support/donations. This post suggests adding a "non-profit" callout in the Codidact sidebar panel.

@ArtOfCode- ArtOfCode- added area: frontend Changes to front-end code type: change request New feature or request priority: medium complexity: easy Issues that should take limited effort to resolve/fix/build. labels Jan 11, 2025
@cellio
Copy link
Member

cellio commented Jan 13, 2025

Our non-profit status on our network should be more explicit. Currently that sidebar text is baked into the code, and we could easily edit that code to add "non-profit", and that wouldn't be worse for other instances that have to route around our baked-in URLs, but maybe we can do better.

Proposed solution: add a (global) site setting with a text value, like the tour settings. Generalize the current text so it's not about our network specifically, as a default and an example/starting point for other networks. Modify the sidebar view to check for the existence of this setting and display it if found (like we do for chat). After we deploy this change, edit that global site setting in prod and on the dev server to have the current text + the non-profit part.

@cellio
Copy link
Member

cellio commented Jan 19, 2025

The change to add the setting is merged, but there is an issue with caching that needs to be fixed before we deploy, and only after deploying can we update that language on our network. I'm keeping this open until that all happens so we can easily find it and its meta post.

@cellio cellio added the status: in progress This is being worked on label Jan 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: frontend Changes to front-end code complexity: easy Issues that should take limited effort to resolve/fix/build. priority: medium status: in progress This is being worked on type: change request New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants