Solfege

I think consulting asexualsurvivors.org, both the website design and team members, would be really helpful for everyone working on the arospec website. Or heck, contact the staff/volunteers at AVEN, it can't hurt. Don't tell me "But they're ace, not aro!" They have experience building the sort of website you're aiming for, and could give you a lot of helpful tips about how to do it yourself. I also see a couple of potential problems: starting too big, and focusing on the superficial parts. "AVEN for arospecs" is too big and vague to be a useful goal. You need to start with something smaller and concrete, e.g. "provide an educational resource for people curious about the aro spectrum." And you need to define how you're going to pursue that goal, like "publish essays explaining aromanticism and related concepts." If you don't clearly define your goals and methods, you'll waste time and money on things that don't actually make your website a solid resource. Also, I think you're starting too big by trying to build a self-hosted website right off the bat. You've made a big promise but haven't provided any sample of what the content would look like, and are asking for money, which makes it hard for people to trust you. Instead, why not set up a subdomain at wordpress.com for free, begin publishing content, and migrate to wordpress.org self-hosting once the community has gotten to know to your work? You could even market the earlier site as a "beta version" and use it as a chance to invite feedback from the community and get diverse voices contributing. Another way this project is "big" is that the aromantic spectrum is a huge, complex topic, and you will need to do a ton of research or add guest contributors' content in order to represent it accurately. Preferably both. It's good to have diverse identities represented on your staff, but having an identity doesn't automatically make you informed on its history, issues, intersections with other identities, or the best way to advocate for it. And you need to read actual books and articles, from inside and outside the community, not just blog and forum posts. Otherwise, you're likely to post factual errors or prejudiced content by mistake. Speaking of which, I agree with Coyote's point about representing aro-spec people of color on your team. I'd also want people with mental disorders, the autism spectrum, and physical disabilities represented, either on the team itself or as major guest contributors. A lot of anti-aro prejudice is related to racism and ableism. The other big issue is that you may focus on the superficial aspects of building a website, like its appearance, domain name, "aro 101" content, and logos, without paying enough attention to the logistics. Who will maintain and update links? Who will pay the bills? Who writes what content, and who proofreads it? Can team members edit each other's content? Who is in charge of soliciting input from the arospec community? How will you make the website accessible to people who are blind, dyslexic, or have other disabilities? If two team members disagree, how will you resolve it? If a factual error or prejudice sneaks into the website's content, who will fix it, and how? Will you copyright your content, and if so, how will you protect it? How will you protect the website's security, and its users/contributors' privacy?