Nodejs.dev: Marketing text for homepage

Created on 28 Apr 2020 · 17Comments · Source: nodejs/nodejs.dev

Summary

On the new homepage there are some sections with lorem text. Do we have actual text for this yet?
https://www.figma.com/proto/lOxAGGg5KXb6nwie7zXkz6/NJ---Design-System?node-id=1338%3A13127&viewport=-232%2C-1378%2C0.21998274326324463&scaling=min-zoom

Right below the how to install tabs
Screen Shot 2020-04-27 at 8 55 43 PM

Below that are company logos

Note the newsletter signup section was removed.

Below that is more text

Screen Shot 2020-04-27 at 8 55 32 PM

MVP question wr-agenda

Source

benhalverson

Most helpful comment

I would recommend not approaching benefits since there are dramatically different benefits for different use cases, and each use case has tradeoffs. For example:

Speed: speed is entirely relative and dependent on _how_ you build things. There are also tools that in certain use cases are _faster_ than Node.js.
One language for front-end and back-end: This is definitely a good point, but there are also many use cases beyond back-end JavaScript and I would prefer to avoid limiting our public messaging to a single lane of JavaScript on the back-end.
Crossplatform: This is fair but also expected at this point, I think.

I'll restate what I said in Slack (#nodejs-website-redesign):

I think approaching this in a similar way that Electron does would be beneficial. You can see a similar setup here:

I'd personally recommend "JavaScript", "Open-Source" and "Everywhere":

JavaScript: covers the intent of "one language" by naming that language, without restricting us to front-end and back-end. The argument _could_ be made that we're more than JavaScript, but this is the primary focus for Node.js so we should be good.
Open-Source: This is a benefit that speaks to individuals and corporations - it's not exclusive for any use case, and while it _is_ currently an expected state for projects it's also a _value_ for us as a project and for our users that I think extends beyond the expectation.
Everywhere: Addresses cross-platform without restricting to what folks typically think of when that term is used: operating systems. Node.js _is_ everywhere - it's been adapted to work in a wide variety of places that I don't think fall under the typical assumptions that come with cross-platform.

bnb on 4 May 2020

🚀3 👍1

All 17 comments

@benhalverson I can work on this if the contents are available

kodekage on 29 Apr 2020

The content doesn't exist right now. Any interest in helping with it @OPARA-PROSPER

benhalverson on 30 Apr 2020

@benhalverson I'd be super excited to do that. I'm not exactly sure the type of content to craft, the image placeholders don't give me any ideas.

kodekage on 30 Apr 2020

Maybe we can do the top 3 benefits of Nodejs

Speed
One language for the frontend and backend
Crossplatform

@bnb @Trott do you have any suggestions?

benhalverson on 3 May 2020

I would recommend not approaching benefits since there are dramatically different benefits for different use cases, and each use case has tradeoffs. For example:

Speed: speed is entirely relative and dependent on _how_ you build things. There are also tools that in certain use cases are _faster_ than Node.js.
One language for front-end and back-end: This is definitely a good point, but there are also many use cases beyond back-end JavaScript and I would prefer to avoid limiting our public messaging to a single lane of JavaScript on the back-end.
Crossplatform: This is fair but also expected at this point, I think.

I'll restate what I said in Slack (#nodejs-website-redesign):

I think approaching this in a similar way that Electron does would be beneficial. You can see a similar setup here:

I'd personally recommend "JavaScript", "Open-Source" and "Everywhere":

JavaScript: covers the intent of "one language" by naming that language, without restricting us to front-end and back-end. The argument _could_ be made that we're more than JavaScript, but this is the primary focus for Node.js so we should be good.
Open-Source: This is a benefit that speaks to individuals and corporations - it's not exclusive for any use case, and while it _is_ currently an expected state for projects it's also a _value_ for us as a project and for our users that I think extends beyond the expectation.
Everywhere: Addresses cross-platform without restricting to what folks typically think of when that term is used: operating systems. Node.js _is_ everywhere - it's been adapted to work in a wide variety of places that I don't think fall under the typical assumptions that come with cross-platform.

bnb on 4 May 2020

🚀3 👍1

@benhalverson with @bnb feedback I'd be able to land a PR that replaces the dummy text and also work on vector images using figma (I share them here before using them) to also replace the dummy image placeholders

kodekage on 6 May 2020

👍1

I worked on a mockup @benhalverson @bnb

marketing-design

https://www.figma.com/proto/RepQL7h21unQFvhbEtTwvI/Nodejs.dev-contribution-mocks?node-id=3%3A2&scaling=min-zoom

kodekage on 6 May 2020

👍1

Based on our discussion last week during the redesign meeting (05/7/2020), we had decided to get a bigger vote from the team in order to see what we really want to do with the mockups and colour scheme of them as well, as we did have a lot of back and forth and things seemed to reach a standstill

designMoreWeb on 14 May 2020

Lets use this issue to keep iterating on marketing copy! We have something out right now, so no huge fire to get updated copy out the door, but please drop all ideas and suggestions below. Remember: there are no bad ideas! We brainstorming now – GO 🎉

amiller-gh on 21 May 2020

From CommComm Discussion Today:

Add a Slack Join Input inside Home Page
Get +1 permission from Babel, Webpack and other projects to use their logos and add in Home
Add Where To Go From Here, add inside home page ?all possible? needs for users
Add Node School and Other Community Projects

Also @bnb Will join our next meeting to help discuss those things. ❤️

saulonunesdev on 28 May 2020

👍2

accordingly with today's commcomm meeting, the best aproach to resolve the pendent issues is to do async, so please post here your concerns here.

in my case:

Get +1 permission from Babel, Webpack and other projects to use their logos and add in Home (Who can pick this up?)
Add Where To Go From Here, add inside home page ?all possible? needs for users (@bnb Can you clarify this please, which topics we must cover inside the home page aside the installation tabs)
Add Node School and Other Community Projects (can we have a list of all community projects that should be included in the home and/or should this be a new view?)

Can we have a designer to sketch this in our home figma?

saulonunesdev on 11 Jun 2020

See https://github.com/babel/babel/discussions/11731#discussioncomment-28281 for permission on using Babel's logo

benhalverson on 9 Jul 2020

Hello! I have left a couple of suggestions, hope you don't mind! 😄