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

create about page for lexbox #854

Closed
hahn-kev opened this issue Jun 4, 2024 · 5 comments · Fixed by #859 or #1104
Closed

create about page for lexbox #854

hahn-kev opened this issue Jun 4, 2024 · 5 comments · Fixed by #859 or #1104
Assignees
Milestone

Comments

@hahn-kev
Copy link
Collaborator

hahn-kev commented Jun 4, 2024

should talk about what it's for, what software uses it, and the nature of our relationship to Payap.

@hahn-kev hahn-kev added this to the v2 (orgs) milestone Jun 4, 2024
@rmunn
Copy link
Contributor

rmunn commented Jun 5, 2024

@psh0078 - Go ahead and create the page with placeholder content; we'll write the actual content, but I'd like you to create the page with the URL /about. It should be reachable by everyone, whether logged in or not, and should use the same basic layout as the rest of the LexBox pages.

@rmunn
Copy link
Contributor

rmunn commented Jun 7, 2024

#859 just had placeholder content. @psh0078 linked it to this issue at my suggestion, because I wanted him to see how auto-closing issues works. But this issue is not actually fixed yet since we still need to populate the About page (which we will do in a separate PR), so I'm reopening it.

@rmunn rmunn reopened this Jun 7, 2024
@megahirt
Copy link
Contributor

megahirt commented Aug 1, 2024

Maybe we can do the content authoring as a GitHub wiki page in markdown and then create a PR to publish the content as a separate step

@hahn-kev
Copy link
Collaborator Author

hahn-kev commented Aug 3, 2024

That's a good idea, I'm just not sure about how to handle images and such. Do we just reference them from GitHub? Or do we copy them in to the app so it gets deployed? I'd rather deploy the images when the app so the page doesn't have an odd dependency outside of the service.

@megahirt
Copy link
Contributor

megahirt commented Aug 3, 2024

yeah, I agree images should be hosted by our own service. Maybe /frontend/static/images/about ?

@hahn-kev hahn-kev self-assigned this Aug 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants