Skip to content

2025-03-26 Express Working Session #350

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
github-actions bot opened this issue Mar 20, 2025 · 4 comments
Closed

2025-03-26 Express Working Session #350

github-actions bot opened this issue Mar 20, 2025 · 4 comments
Labels

Comments

@github-actions
Copy link

github-actions bot commented Mar 20, 2025

Date/Time

Timezone Date/Time
America/Los_Angeles Wed 26-Mar-2025 14:00 (02:00 PM)
America/Denver Wed 26-Mar-2025 15:00 (03:00 PM)
America/Chicago Wed 26-Mar-2025 16:00 (04:00 PM)
America/New_York Wed 26-Mar-2025 17:00 (05:00 PM)
Europe/London Wed 26-Mar-2025 21:00 (09:00 PM)
Europe/Amsterdam Wed 26-Mar-2025 22:00 (10:00 PM)
Europe/Moscow Thu 27-Mar-2025 00:00 (12:00 AM)
Asia/Kolkata Thu 27-Mar-2025 02:30 (02:30 AM)
Asia/Shanghai Thu 27-Mar-2025 05:00 (05:00 AM)
Asia/Tokyo Thu 27-Mar-2025 06:00 (06:00 AM)
Australia/Sydney Thu 27-Mar-2025 08:00 (08:00 AM)

Or in your local time:

Agenda

Extracted from top priority labelled issues and pull requests from expressjs/discussions prior to the meeting.

Invited

This meeting is open for anyone who wants to attend. Reminder to follow our Code of Conduct.

@expressjs/express-tc
@expressjs/triagers
@expressjs/security-wg

Links

  • Minutes:

Joining the meeting

@bjohansebas
Copy link
Member

The plan for this meeting is mainly to resolve issues related to the website, primarily expressjs/expressjs.com#1787 and expressjs/expressjs.com#1676.

cc: @expressjs/docs-wg

@UlisesGascon
Copy link
Member

Are we all able to meet tomorrow (cc: @expressjs/docs-wg @expressjs/docs-captains @expressjs/docs-collaborators @crandmck @nglngl @micheleriva)?

Use 👍 👎 as a response to this 🙏

@jonchurch
Copy link
Member

Thread where the idea of working with a designer was put forth: expressjs/expressjs.com#1787

Rand: We should separate the Implementation and the Design, in terms of we are discussing the end result not how we get there. The visual design and (maybe?) the IA are on the table currently.

Question from rand: Do we want to keep the minimalist design as a principle? Or is everyting on the table?

Angela is presenting a kickoff deck they prepared

Rand: help with Layout, Design system, brand identity are super welcome, for IA it's something we might want to evaluate on its own.

Brand Identity: What does this mean for us? We are bikeshedding on the fact that we are thinking about getting a new logo, Angela is explaining that it is Tone of Voice, Style, positioning, etc etc.

Chris: If we are going with a wholesale new logo, we should be careful and deliberate about that. It's been around for a long time (the logo) it does have brand recognition, we should be sure that if we are doing a new logo we dont negatively impact our own recognizability and goodwill.

Ulises: We currently have no brand identity solidified, tone, colors, etc. We dont even have a transparent version of our own logo. We've discussed having separate logos per major, for fun.

Next step on Brand Identity: We are leaning toward keeping our current logo, we would love to do a brand identity workshop as it is something we are missing currently.

Michele: Demoing Orama AI chat, which is being used on Node.js Docs and Tanstack docs. We can selfhost the Orama core (which is open source) in the OpenJS infrastructure.

Wes: We want to make sure that the failure mode is good, in terms of if we are going to use Orama chat.

Next step for Orama Chat: After we do branding discussion, chat with Michele (sync or async) about the technical details of Orama chat.

Next step overall: Brand Identity workshop with Orama folks. Targetting April 9th, the next Working Sesssion

@bjohansebas
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants