What inspired your project?
History erases so many key figures simply because they were “different” compared to people in society. LGBTQ+ people throughout history mostly have been forgotten about or washed over because they are gay, trans, or just simply didn’t fit the societal norm. We wanted to create a place where we could start bringing LGBTQ+ people’s names back into history and restore their accomplishments in history books.
What problem does your project solve?
The biggest problem that we are aiming to address is the erasure of important LGBTQ+ people in history. We also wanted to address several identities that are misunderstood due to the amount of false information spread about them in the media. We wanted to include information about LGBTQ+ identities and some information about pronouns in order to bring more understanding to different terms and words that aren’t often used but should be due to their importance.
How does your project solve the problem?
Our project focuses on educating about LGBTQ+ topics and people as they are a minority group that society tries to conceal and erase. By focusing on research and important topics to our group, we were able to make a product that we are happy with that focuses on educating about identities and forgotten people. We also gathered extra resources, if the viewer wants to learn more about the different subjects, that are varied in their topic and who their audience is (someone in the community, a supportive ally, etc).
What technologies did your project use? Include programming languages, libraries, and any external tools.
Through Visual studios we created a website and the program languages we used included: HTML and CSS. We didn’t use any external tools or libraries.
What challenges did you run into?
One of our biggest challenges was that the program we were using to collaborate on the code wouldn’t allow everyone to view the website, it would only allow the owner of the project to view it, so we had to have a video call where the owner shared their screen the whole time. Another issue we ran into is that everyone is very inexperienced and we often had to search up solutions for the dozens of small details we were missing or didn’t understand. Having to double check our code often and research better solutions to create what we wanted was quite time consuming, and cut down on our coding time for this project.
Log in or sign up for Devpost to join the conversation.