Skip to content

Commit 86b1dc3

Browse files
authored
Merge pull request #100 from plus-hi/master
Programs page updates: events section, Luma links, hero copy, docs cleanup
2 parents b06b00b + c375b54 commit 86b1dc3

11 files changed

Lines changed: 173 additions & 7 deletions

File tree

.github/workflows/deploy.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ name: Deploy to GitHub Pages
33
on:
44
push:
55
branches:
6-
- main-update
6+
- feature/programs-page-update
77
- master
88

99
permissions:

.gitignore

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -35,3 +35,6 @@ yarn-error.log*
3535

3636
# intellij
3737
.idea
38+
39+
# windows zone identifier files
40+
*:Zone.Identifier

docs/github-pages-migration.txt

Lines changed: 47 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,47 @@
1+
TechLadies Website GitHub Pages Migration Update
2+
3+
A PR has been created to master: https://github.com/TechLadies/website/pull/98
4+
5+
Note: A deployment from the main-update branch was attempted but GitHub Pages on this repo restricts deployments to the master branch only. A merge to master is required to trigger the GitHub Pages deployment.
6+
7+
What happens on merge:
8+
- A GitHub Pages deployment should be triggered (workflow has been set up and tested on staging).
9+
- If the repo is still connected to Vercel, a Vercel deployment may also be triggered.
10+
- The live site at techladies.co should not be affected unless DNS is updated.
11+
12+
---
13+
14+
Steps to switch from Vercel to GitHub Pages
15+
16+
1. Update DNS (at domain registrar)
17+
18+
Remove any existing A records or CNAME pointing to Vercel, then add:
19+
20+
A records (IPv4):
21+
185.199.108.153
22+
185.199.109.153
23+
185.199.110.153
24+
185.199.111.153
25+
26+
AAAA records (IPv6):
27+
2606:50c0:8000::153
28+
2606:50c0:8001::153
29+
2606:50c0:8002::153
30+
2606:50c0:8003::153
31+
32+
If using www.techladies.co, also add a CNAME record:
33+
www TechLadies.github.io
34+
35+
Reference: https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site
36+
37+
2. Configure custom domain in the repo
38+
- TechLadies/website Settings Pages Custom domain enter techladies.co
39+
- Enable "Enforce HTTPS"
40+
41+
3. (Optional) Disconnect Vercel
42+
- Vercel dashboard TechLadies project Settings Git Disconnect
43+
- This stops unnecessary Vercel builds
44+
45+
Note: DNS changes can take up to 24 hours to propagate.
46+
47+
If the production deployment to Vercel continues to work well, there is no urgency to migrate the site can remain on Vercel with no changes needed. The GitHub Pages setup has been tested on staging (plus-hi.github.io/techladies-staging) and is available as an option whenever it makes sense to switch.

docs/techladies-2026-overview.pdf

1.14 MB
Binary file not shown.
58 KB
Loading
274 KB
Loading

src/components/EventCard/index.js

Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
import clsx from "clsx"
2+
3+
import styles from "./index.module.scss"
4+
5+
export default function EventCard({ image, title, date, url, status, wide }) {
6+
const isUpcoming = status === "upcoming"
7+
8+
return (
9+
<div className={clsx("card", styles.card)}>
10+
<div className={clsx("row g-0", wide && "align-items-center")}>
11+
<div className={wide ? "col-md-5" : "col-12"}>
12+
<img
13+
alt={title}
14+
className={clsx(styles.poster, !isUpcoming && styles.posterPast)}
15+
src={image}
16+
/>
17+
</div>
18+
<div className={wide ? "col-md-7" : "col-12"}>
19+
<div className={clsx("card-body", !wide && "card-body-sm")}>
20+
<span
21+
className={clsx(
22+
"badge mb-3",
23+
isUpcoming ? "bg-purple" : "bg-secondary",
24+
)}
25+
>
26+
{isUpcoming ? "Upcoming" : "Past"}
27+
</span>
28+
<h4 className="mb-3">{title}</h4>
29+
<p className="text-body mb-4">{date}</p>
30+
{isUpcoming && (
31+
<a
32+
className="btn btn-primary"
33+
href={url}
34+
target="_blank"
35+
rel="noreferrer"
36+
>
37+
Sign up on Luma
38+
</a>
39+
)}
40+
</div>
41+
</div>
42+
</div>
43+
</div>
44+
)
45+
}
Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
.card {
2+
height: 100%;
3+
overflow: hidden;
4+
}
5+
6+
.poster {
7+
display: block;
8+
width: 100%;
9+
height: auto;
10+
}
11+
12+
.posterPast {
13+
filter: grayscale(0.4);
14+
opacity: 0.85;
15+
}

src/data/events.js

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
import prefix from "../utils/prefix"
2+
3+
// Change status to "past" once an event is over — it moves from the Upcoming
4+
// section near the top of the Programs page to the Past section at the bottom.
5+
const events = [
6+
{
7+
status: "upcoming",
8+
title: "Saturday Nature Hike: Southern Ridges",
9+
date: "Sat, 22 Aug 2026 · 8:30am",
10+
image: `${prefix}/events/2026-08-22-southern-ridges-hike.jpg`,
11+
url: "https://luma.com/24qkprvm",
12+
},
13+
{
14+
status: "past",
15+
title: "Build Your Career With Confidence",
16+
date: "Thu, 16 Jul 2026 · 6:30pm",
17+
image: `${prefix}/events/2026-07-16-build-career-confidence.jpg`,
18+
url: "https://www.meetup.com/women-devs-sg/events/315367903/",
19+
},
20+
]
21+
22+
export default events

src/data/quiz.js

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -133,7 +133,7 @@ const ACTION = {
133133
</div>
134134
<a
135135
className="btn btn-primary mb-5"
136-
href="https://www.eventbrite.sg/o/techladies-11040976589"
136+
href="https://luma.com/user/usr-kXtH2e6ihZuXcEd"
137137
target="_blank"
138138
rel="noreferrer"
139139
>

0 commit comments

Comments
 (0)