nodejs / foundation.nodejs.org Goto Github PK

This will be CMSd content that is controlled by... probably... marketing/PR. So, since I don't really know a conduit to communicating to those folks- I'm posting here....

I'd like to propose that, when this site goes live, there is a friendlier Board Member Page.

The current page lists the info.. which is does its job... but I think we can help alleviate any perception of a secret corporate overload board (feedback I've heard) by simply putting faces to names. Certainly there isn't a requirement in the by-laws for someone to have a picture up to be on the board... but I bet many will be fine with it.

Picking a random example for illustration, AirBnB's founders page:

See! Nice, friendly faces :D

Why the new website?

See: nodejs/nodejs.org#581

That issue, mentions these will get moved to this repo:

• Press Releases
• In the News
• Member List

@mikeal Is the intention of this site to be a standalone site (i.e.: has it's own landing page)? or a site that is interwoven with the current site? (like the design will be the same as https://nodejs.org and people won't really even know they are in the microsite)

Has there been a proposal/discussion of the architecture of this setup with @nodejs/build, @nodejs/website, etc?

Is this repo maintained by @nodejs/website WG?

If these discussions have already happened, please link them here so future visitors can follow along.

I haven't seen any updates here for awhile. Any update on how/where this initiative is going?

Hey team,

Sorry I'm using an issue for this - not sure what the best communication channel is, let me know if there's a more appropriate way to open discussions.

I'm back on deck after the birth of my first child (yay!) and ready to pick this up again. We're about to release some meaningful updates to the KeystoneJS generator and a new version of Keystone itself which would dovetail nicely into updating the scaffold @mikeal put in place, which I raised in #3.

In doing so, does someone have a design or spec for what the site will contain & how it will look? We can either design it as content-managed drop in pages that are part of the nodejs.org site, or it could have its own navigation structure as a (slightly) standalone area... I'm quite happy with either, just need some direction.

This is picking up on some of the questions raised by @williamkapke in #4, if there's any answers or someone I can follow up with to get them, that would be great. Alternatively, if there's just a "we have no answers, do something good and we'll probably roll with it" I can work with that.

Cheers!

@mikeal Just checking to see if your choice of hbs was a strong preference out of the options available in the generator? I've personally found it the most obtuse to work with because of the need for helpers, which can also be a bit of a barrier to contribution.

If you're not put off by the syntax, Jade has been really good to work with, or if you want your templates to look like HTML I'd usually go with nunjucks. Because you can actually call functions from either, things like the underscore methods in Keystone are a lot more readily usable, e.g.

{% if data.post.publishedDate %}
    on {{ data.post._.publishedDate.format("MMMM Do, YYYY") }}
{% endif %}

Those two implementations are also more complete in the generated templates.