✍️ Writing an "about page"

[tatianamac]

Overview

As the project grows, having a full separate about page that explains the context for the project would be beneficial.

Things to cover

• Back story; why does this project exist and why is it important
• Caveats about how language evolves
• Caveats about how self-identifying terms do not necessarily always have consensus and how we shouldn't be seeking consensus
• Content warnings
• Usage/licensing
• Open source backbone of project
• Future plans

Helpful resources

• README

[ivana-mcconnell]

Hi Tatiana! I'd like to help with this one. It's pretty clear to me, but I just have a few questions for you before starting:

1. Content warnings: I'm assuming you'd like to outline why they're used, when, and what they look like on the site?
2. Usage/licensing: Do you have any guidelines on what you'd like said about this? Do you mean usage or licensing of the concept, of the code, or something different? I assume this should include "Maintain OSS nature for non-profit and other OSS uses, but charge for corporate uses," yes?
3. Open source backbone: I'm assuming this means a description of both the ethos of the project, but also the usage of Eleventy, Contributor Covenant, and github itself?

[tatianamac]

Hi, @ivana-mcconnell ! Yay! Your second issue! 🎊

Answers below!

Also, I'd love to invite you to our Slack community. Every Saturday, I'll be hosting "Self-Defined Saturdays where I'll help folks work through issues! I hope multiple folks will come to work on it. 😅

1. I think it's good to reference to ⚒️ Build content warning logic #142 for more context. Broadly, it's a little meta. I'd like to both [1] express that reading this site may be triggering for some, so that we've tried to care for that by placing content warnings in the site around topics; and [2] educate people on using content warnings. As you will see from ⚒️ Build content warning logic #142, there is a lot to say, and in the Slack channel we've discussed creating a content warning definition in the future. The about page could link to this. In the meantime, what you said is great.

2. Yes, I think that explicitly we state the license. Right now I think I'd like to use GNU AGPLv3 might be a good place to start. Long term, I do not want FAANG touching the code and making it into a profiteering machine.

3. Correct! That all tools we use also be part of the open-source ecosystem.