Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Latest commit

 

History

History
69 lines (45 loc) · 2.95 KB

2018-04-12.md

File metadata and controls

69 lines (45 loc) · 2.95 KB
Raw

Node.js Foundation Website Redesign Strategic Initiative Meeting 2018-04-12

Links

Present

Manil Chowdhury (@chowdhurian) Tierney Cyren (@bnb) Adam Miller (@amiller-gh) Francisco Tomalsky (@tomalsky) Abraham Agiri Jnr. (@codeekage)

  • Website Redesign Strategic Initiative Team: @nodejs/website-redesign

Agenda

  • Coordinating "Getting Started" content with NodeSchool content #18
  • Website Wireframes #15
  • Tech Exploration for In-Browser Node.js Playground #12

Announcements

@oe is stepping back from managing the @nodejs/website-redesign initiative. @chowdhurian and @amiller-gh are stepping up as co-champions for the initiative.

Welcome @codeekage to the team! Happy to have you!

*Extracted from wr-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/website-redesign

Coordinating "Getting Started" content with NodeSchool content #18

  • shouldn't let getting started block us.
  • We should start to transition to active content development and high-fidelity mockups – can happen in tandem.
  • Should move on the getting started breakout meeting

Website Wireframes #15

  • Adam: Made updates to reflect feedback on download and releases flow. Will be live soon.
  • The homepage needs an iteration for content. For homepage, the content will inform the layout so we'll need to do that first.
  • Homepage will need a space for events that the Foundation can push to, and security notifications
  • We need tighter feedback loop (such as a dedicated channel in Node.js Slackers or Twitter DMs) between design iterations and users

Tech Exploration for In-Browser Node.js Playground #12

  • See RunKit demo
  • Idea from RunKit: Active Nightly Demos?
  • Docs run behind nightlies, dedicated "hot features" page?
  • Lock RunKit Node.js version down to docs version

Action Items

  • TODO: Manil to split out the current team members by interest in IA, Design, Code.
  • TODO: Adam to send out Dribble for breakout meeting.
  • TODO: Adam/Tierney to make a list of items we want on Getting Started.
  • TODO: Adam to create Node.js Slackers #website-redesign channel.
  • TODO: Adam to submit a Node.js extended colour palette for review.

Q&A, Other

Upcoming Meetings

Click +GoogleCalendar at the bottom right to add to your own Google calendar.