Skip to content

Add agenda section#34

Open
haywirebanana wants to merge 26 commits intomainfrom
feature/agenda
Open

Add agenda section#34
haywirebanana wants to merge 26 commits intomainfrom
feature/agenda

Conversation

@haywirebanana
Copy link

I tried to implement a collapsable/accordion feature for the different dropdowns, but was unsure about how to deal with some HTMLAttribute errors so I decided to go for Detail & Summary Tags for ease of dealing with event handlers.

image

@lindan4 lindan4 requested a review from a team January 19, 2025 15:28
lindan4 and others added 11 commits January 19, 2025 17:01
What did we do?

Update documentation by replacing npm commands with pnpm commands

Why was it done?

Since we are using pnpm, different files will be generated.
What was done?

Ran pnpm dlx @astrojs/upgrade tp upgrade Astro to the latest version.

why was this done?

To keep Astro up to date. This is major version upgrade, and considering how early we are in the development of the project, it is better to do it now.
@lindan4
Copy link
Collaborator

lindan4 commented Feb 8, 2025

Screenshot 2025-02-07 at 7 12 59 PM Screenshot 2025-02-07 at 7 13 21 PM

@haywirebanana according the mockup we have, it looks like your designs may have to be changed. These include, but are not limited to:

  1. There should be no expand/collapse icon (disclosure triangles) on the left and at the bottom, but they should be on the right centred vertically.

  2. Font styling and text alignment needs to be changed.

Comment on lines +12 to +24
<details class="accordion">
<summary class="accordion-header">
<div class="header-content">
<span class="time">{time}</span>
<span class="title">{title}</span>
<i class="fa fa-caret-down toggle-icon"></i>
</div>
</summary>
<div class="accordion-body">
<p class="body-text">{body}</p>
<p class="speaker">{speaker ? `Speaker: ${speaker}` : ''}</p>
</div>
</details>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we will have to use another outer element to match designs. details would be a lot more convenient though

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With our previous discussions, I needed to visualize what it would look like compared to the old "version" in Figma where it was just plain text. I created that visual on Figma on a whim. Should I adhere to it?

I figured details/summary would be convenient as we are working on a static website, is there an alternative I can use?

font-size: 25px;
}

.body-text {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about accordion-body-text?

<meta name="viewport" content="width=device-width" />
<link rel="icon" type="image/svg+xml" href="/favicon.svg" />
<meta name="generator" content={Astro.generator} />
<link href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.15.4/css/all.min.css" rel="stylesheet" />
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we need this?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Refer to comments on feature/footer branch

Copy link
Collaborator

@lindan4 lindan4 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You'll have to make changes, but also rebase your branch as there are merge conflicts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants