Welcome to the WOWEN website repository! We're thrilled to have you here as we embark on a journey to revolutionize FemTech. 🚀
- About
- Deployment and Staging
- Changelog
- Roadmap
- Developer Documentation: Technical Architecture and Stack Overview
- Contributing
- Feedback and Support
- Connect with Us
WOWEN is not just a company; we are a creative powerhouse with expertise in full-stack development, FemTech, UX, design, and marketing. We have a unique ability to transform high-level strategy into practical implementation at the intersection of business development, communication, and technology.
Our website is hosted and deployed with Netlify. Production site www.wowen.tech is main
branch, staging site staging--wowen.netlify.app is staging
branch.
In most cases, changes should never be directly deployed to our main
branch, which serves as the production environment/main branch/site. Instead, commit and deploy your changes to our staging branch first, and if approved it will be merged and synced into our main
branch. For the website (www.wowen.tech), the staging branch is named staging
and can be accessed at https://staging---wowen.netlify.app.
For those who are new with the terms:
- Branch: A branch is like a version of our code, our
main
branch is our Web App/production site https://www.wowen.tech and ourstaging
branch is our staging site https://staging--wowen.netlify.app where we stage/test updates before they end up on our production site, themain
branch. This is a way to work on updates or new features without affecting the publicly known and used live website. Once you're satisfied with the updates onstaging
, you can combine ("merge") thestaging
branch into themain
branch, the main version of the code, our production site. - Staging: Is a separate test version of our site. Our branch
staging
is our staging enviroment. Current branch update/status/deployment is always accessed live at https://staging--wowen.netlify.app. - Pull Request: Is a proposal to update some part of our website's code, if the proposal is good, it will be "merged" into
main
branch, our production site https://www.wowen.tech. - Merging: Merging is the process of taking the changes from one branch (version) of our code and combining them with another branch, usually the
main
one. This allows us to update the official version of our project with new features, fixes, or improvements that we've been working on separately on staging. Once merged, those changes become part of themain
or target branch and are reflected on https://www.wowen.tech. - Deploy Contexts: Are settings that tell Netlify how to handle our different branches when turning them into live websites.
- Deploy Previews: Are temporary websites that Netlify creates to show you what these changes will look like if they go live. When someone suggests changes to our code, they often make a "pull request." With this setting, Netlify will automatically create a temporary, live version of our site incorporating those suggested changes. This is called a "Deploy Preview." This allows you to preview changes before they go live on our main site (
main
branch). - Branch Deploys: The
main
branch serves as our production branch, while branch deploys encompass all other branches created here that we designate to be included as "Branch Deploys."
- Production Branch:
main
- Branch Deploys:
staging
Note: Netlify is with this setting ignoring any other branches we create in this repo; it won't make websites from them. - Deploy Previews:
Any pull request against your production branch / branch deploy branches
This changelog provide a high-level overview of the changes made in each version of the website:
At present, we do not have a roadmap for wowen.tech website.
Our technical infrastructure is designed to be robust and scalable, leveraging a variety of technologies and services. Below is a detailed breakdown of our current setup:
- Technologies: HTML, CSS, JavaScript
- Description: The frontend is a simple setup consisting of HTML, CSS, and JavaScript files.
- Registrar: One.com
- Description: We've registered our domain (
wowen.tech
) and all associated subdomains with One.com. As of now, we intend to continue using One.com as our domain registrar due to its other convenient features.
- Platform: Netlify
- Description: We use Netlify for hosting and deployment. We've set up the DNS settings on One.com to point to Netlify, which serves as the platform for both our frontend hosting and deployment.
- Netlify Forms: Used to collect contact forms on
/contact
and/sv/kontakt
. - Tally: Used to collect applicant forms on
/careers
and/sv/jobb/
.
- Google Analytics: Used for web traffic analysis – (
WOWEN – wowen.tech – GA4
). - Plausible: An additional tool for web traffic analysis – (
WOWEN – wowen.tech
). - Google Tag Manager: Used for managing pixels and tags on the website, current implemented tags: Google Analytics, Facebook Pixel, LinkedIn Insight Tag – (
WOWEN – www.wowen.tech
)
As of now, we plan to continue using Netlify for hosting and deployment and One.com for domain management. However, we are evaluating other options for hosting and domain management, potentially transitioning to AWS Services or Vercel.
- One.com (Domain management + database possibilities + archive for old email domain wowen.se)
- Netlify (Hosting, frontend deployment, form collection, authentication)
- Tally (Form builder)
We welcome contributions from the FemTech Dev Community. If you'd like to contribute to our projects, please follow our Contributing Guidelines.
Have feedback or need support? Feel free to reach out!
- Website: wowen.tech
- First Contact Email: [email protected]
Thank you for your interest in WOWEN. Together, we're making FemTech innovative, creative, and powering. 💪
Copyright © 2019-2024, WOWEN. All rights reserved.