►
From YouTube: Website Redesign Past, Present, and Future
Description
OpenJS Foundation Collaborator Summit, Berlin, 2019
More details: https://github.com/nodejs/website-redesign/issues/155
Level-setting
* Pace of progress picked up quickly, would be good to see if we’re still functioning well
* Recap of the process so far and future plans.
Introduction to the machine and improve onboarding docs
* Workshop to get new people on board. We're not teaching React/Gatsby. We're teaching people about how we implemented nodejs.dev
* In the process improve onboarding docs
* Nice to have: Get good first issues in the issue queue and use as walkthroughs
Collaboration
* with core docs contributors: How we want to tackle API docs
* with i18n: How to best consume localized API docs"
A
What
plan
is
what's
next
so
started
year
ago
now
with
us
trying
to
figure
out
what
what
a
website
redesign
might
look
like
really
wish
I
could
share
because
start
out
with
a
couple
medium
posts
for
me,
this
epic
length,
you
can
go
find
it
do
we
look
good
yeah
yeah
grab
an
issue
for
us
to
go
in
second
drop
links,
trialled
open,
let's
go
over
to
the
nodejs,
slash
website,
redesign
repo,
we're
gonna
pop
into
issue
just
closed
it.
Unfortunately,
just
this
close
yeah.
B
A
Awesome
we're
gonna,
go
open
to
issue
155
and
website
redesign
I'll
drop
links
in
there
so
that
we
can
like
yeah
I'll
look
at
stuff
together,
blue
of
sharing.
So
it
started
out
on
a
medium,
a
good
chunk
of
time
about
59
155
yeah,
with
this
kind
of
epic
length,
article
I
posted
a
while
back
called
redesigning
no
js'
part
1
yep,
so
if
you're
kind
of
just
a
competitive
analysis
a
whole
bunch
of
other
websites.
A
A
There
was
a
lot
of
conversation
online
with
the
existing
website
team
and
with
a
whole
bunch
of
new
folks
talking
about
information
architecture
and
just
making
sure
that
all
the
content
fits
into
there
and
then
from
there
put
together
a
vision
board
with
a
whole
bunch
of
link.
I
just
dropped
in
the
issue
as
well,
which
is
kind.
B
C
A
Scaffolding
of
how
the
websites
gonna
look
a
few
questions
like
it's
not
gonna,
be
blue,
it's
just
for
structure
and
like
information,
yeah
information
structure,
and
then
we
want
to
start
getting
started
on
building
something
made
a
few
technical
choices
and
had
the
pleasure
of
working
with
miles
who
got
a
deal
with
Google
to
get
us
the
domain.
Nodejs
dev.
A
We
spun
up
a
new
dedicated
code
repo,
so
the
repo
that
you're
all
looking
in
right
now
is
the
website
redesign
repo,
there's,
also
no
js'
slash
nodejs
dev,
which
is
the
kind
of
code
repository.
Let's
talk
about
unifying
the
two
but
opted
to
keep
them
separate
website.
Redesign
is
kind
of
the
admin
repo
and
no
ji
dam
is
the
Kohen
repo,
but
no
guest
dev
is
the
home
of
dev.
A
A
Yes,
so
we
need
to
get
some
content
up
there.
So
we
kind
of
took
the
layout
of
this.
This
wireframe
turned
it
into
the
site.
You
see
it
no
gets
out
that
if
you
go
take
a
look
at
the
repo,
it's
a
ghastly
sight
so
you'll
page
about
split,
it's
an
awesome
framework
for
building
documentation
and
kind
of
pulling
in
content
from
a
whole
slew
of
different
sources
and
I'm
missing
right.
We
have
a
wonderful
co-worker
of
mine
at
LinkedIn.
Is
a
developer.
A
A
As
far
as
ia
goes,
we
have
a
good
direction
to
work
with
here
and
there's
some
pretty
well
scoped
out
sections
in
the
site
to
start
tackling
next,
that's
kinda,
I
was
hoping
to
take
this
session.
To
focus
on.
You
know,
make
some
technical
decisions
around
how
we're
gonna
move
forward
with
API
Docs
page
the
releases
page.
You
know
all
this
and
you
can
start
actually
opening
fine-grained
issues
that
we
can
divvy
out
and
treat
it's
kinda
like
after
planning
session
the
next
few
months.
A
C
A
Question
I
think
the
hope
is
once
we
get
content
parity,
we
will
approach.
The
website
team
is
aware
of
this
and
werewolves
are
so
exciting
and
proposed,
essentially
switching
over
the
site.
So
the
hope
is
the
content.
That's
currently
on
node.
Guess
then
we'll
move
over
to
org
and
then
we
get
to
have
the
fun
conversation
of
what
do
we
do
with
the
depth
domain
now
like?
Can
we
just
make
it
a
mirrored
version?
B
A
A
Yeah,
there's
a
lot
more
I
want
on
this.
This
learn
pinch
like
right
now.
It's
just.
We
had
an
amazing
donation
from
Flavio
Gomez
for
getting
started.
Guides
dumps
tired
and
you
buy
it
to
mark
down
that
he
published
in
their
dominant
right,
but
there's
a
lot
of
more
like
advanced
content.
I
won't
get
in
there
and
there's
actually
a
lot
of
guides
currently
buried
them.
The
note
the
current
site
that
would
be
good
to
figure
out
what
it
didn't
push
em,
where
they
can't
go,
delete
those
engines.
C
A
A
B
A
Any
getting
started
resources.
How
to
learn
note.
Have
you
I
think
beyond
downloading
a
binary
like
so
there's
there's
a
lot
of
content
in
use
cases
that
aren't
met
by
just
the
API
Doc's
take
just
the
big
old
download
button
and
it's
we're
with
the
learn
pages
from
the
internet,
we're
getting
closer,
but
there's
so
much
more
content.
We
didn't
act,
including
you
know.
I
am.
A
A
Website
the
advance
guys
looks
like,
but
it's
really
just
kind
of
the
guys
right,
yeah,
it's
just
kind
of
a
hodgepodge
of
what
what
folks
in
the
deep
in
the
technical
side
have
decided
that
they
want
to
write.
I
mean
it's
it's
also
three
years
of
technical
part
of
our
website.
Those
are
temporary
ones,
so
yeah
that
lip
service
temporary-
and
it's
not
been
temporary,
I'd-
really
love
to
actually
take
a
make.
A
A
C
A
B
B
A
A
A
Learning
page
content
is
a
pretty
large
mute
still
like
we
have
enough
there
that
like
if
we
got
everything
else
on
the
site
switched
over
and
like
I,
have
content.
Barony
like
I'd,
feel
pretty
comfortable
switching
over
with
the
content.
That's
there
right
now,
just
the
things
are
getting
started
study,
but
we
can
make
it
a
lot
better.
C
A
A
A
Can
kind
of
set
a
dependency
on
anything
in
stitches
it
together,
so
yeah
I,
API
Doc's
a
kind
of
a
special
little
beast,
because
we
all
this
stuff
also
need
to
get
translated,
so
we're
working
with
the
brute
figure
out
how
like
what
their,
what
their
publisher
coat
looks
like
artifact.
They
just
that
again,
and
we
know
that
so
this
there's
a
lot
of
outstanding
work
there
we're
kind
of
waiting
on
it--
and
then
to
get
there.
A
We
had
a
concession
yesterday
we
can
figure
out
how
that's
gonna
work,
but
we
also
get
to
figure
out
how
we
were
not
blocked
by
that.
In
the
meantime,
it's
like
for
the
NDI
not
specifically
right
now,
every
version
of
every
json.parse
file
in
the
API
Doc's
folder,
just
living
currently
deployed
on
org,
so
good,
like
first
first-pass
integration.
A
We
can
hit
that
up
like
it
says
an
API
just
go
fetch
the
JSON
as
we
need
it
and
rendered
on
HIV
see
fit
so
there's
link
baseline
work
in
the
site
right
now,
API
Doc's,
just
you
know
we
don't
have
a
whole
bunch
of
design
yet
for
it.
But
there's
a
lot
of
data
work,
just
hooked
up,
I'd
love
to
see
like
a
good
strategy
for
the
first
of
procures,
like
we,
we
always
bake
in
the
latest
release
into
the
sign
itself.
A
A
C
A
A
Prominently
displayed
with
that
extra
download
options
and
hopefully
a
better
communication
model
for
the
release
process.
It's
it's
kind
of
hard
for
new
users
to
drop
the
release
flow
and
I
love.
I
amber
does
the
best
job
of
describing
their
release
process
that
I've
seen
so
far
keep
illustrations
for
each
release
line
and
give
you
a
pretty
nice.
C
C
A
A
A
B
One
of
the
issues
Ramona
discussing
among
the
discoverability-
oh,
the
kind
of
issues
which
we
searched
in
that
usually
Stack
Overflow
comes
in
the
top.
Then,
given
the
node.js
slash
nor
issue,
rapport
comes
up,
but
not
necessarily
the
APA
documentation.
The
green
website
only
known
that
dot
there
yeah.
So
is
it
it's
because
the
kind
of
topic
that
is
being
searched
is
not
present
author,
or
should
we
have
nerds
yeah?
B
A
A
And
keep
the
best
practices
for
all
the
metadata
for
search
engines
to
crawl
it
and
everything,
but
I
mean
so
right.
Now,
like
part
of
that,
these
are
you
know
if
you
run
the
lighthouse
test
on
the
docks
that
you
guide
us,
the
SEO
element
is
a
which
is
like
a
warning
effectively
like
you
need
to
do
better
and
googled,
except,
like
that's
a
very
serious
thing
to
them.
It's
like
if
you're
not
doing
well,
you're,
not
gonna,
get
ranked
well
get
up,
does
well
second
or
foot
as
well.
A
So
you
know
I
think
I
got
to
be
tough,
sell
a
lot
out
of
the
box
yeah
and
then
there's
minor
tweaks
that
we
can
make
like.
Please
say:
one
person
can
go
and
get
us
to
honor,
which
is
very
nice,
and
that
should
theoretically,
just
give
us
a
flat
improvement
on
that.
And
then
you
know
once
that's
done,
I
don't
think
there
are
individuals
at
Google
who
are
doing
your.
A
A
Amanda
capability
is
actually
I'd
love
to
kind
of
pick
your
brain
a
little
bit
about
how
we
can
improve
the
format
of
API
Doc's
long
term,
because
right
now
it's
it's
all
in
its
it's
somewhat
structured
data
yeah,
but
there's
the
far
better
ways
to
document
it
than
just
in
markdown
files.
You
kind
of
manually
keep
up
to
date
with
the
code.
No
there's
no
services
like
oh
yeah
yeah.
They
would
be
more
than
willing
to
give
us
their
service.
I
mean
there's.
Just
a
ghastly
has
a
great
ecosystem
around
it.
So.
A
A
A
C
So
I
see
several
please
correct
me
if
I'm
wrong,
I'm,
making
a
bunch
of
assumptions
here
with
everything
but
I
see
several
different
tracks
on
which
things
are
moving,
and
you
know
trying
to
figure
out
where
the
blockers
are
and
where
I
could
help.
You
know
remove
some
of
those
sounds
like
you
know,
there's
the
techno
technology
of
actually
building
this.
C
Which
goes
slow
or
whatever,
just
a
design
which
I'll
kind
of
love
them
with
the
technology,
because
some
of
these
people
are
working
closely
together
to
all
the
tech,
the
wireframe
and
building
it
out.
There's
the
content
side
of
it,
which
is
obviously
creating
a
content
you
want
to
see
and
then
final
one,
it's
likely
because
I've
had
disparate
all
this
is
and
how
it
would
be
drawing
content
from
committee's
information
architecture.
Essentially,
in
terms
of
you,
have
all
the
content.
Everybody
produces
two
different
formats
and.
C
Technical
debt
fix
all
that
essentially,
so
that's
one
thing
that
I
look
at
as
is
like:
if
we
can
figure
out
a
format
to
make
it
play
nice
with
SEO
and
everything
and
markdown
format
or
whatever
that
I.
Can
you
know
in
depending
on
what
y'all
are
doing
like
wrong
on
creating
content
or
tweaking
needing
to
the
so.
A
A
Be
an
oak
or
Conception
markdown
files.
If
it's
learn
page
Doc's
attorney
lives
in
website
redesign
pointed
there.
The
I
think
it's
all
documentation
bullet
right.
There
I've
solved
this
markdown
holds
in
it's
like
I
was
trying
matter
little
blob.
It
tells
it.
How
did
this
way
on
the
I'm?
Gonna
learn
page
yeah,
presumably
like
releases
page
well,
we
just
be
a
hard-coded
page
for
the
description
of
it
in
the
documentation,
repo,
but
it'll
pull
in
data
to
show
the
historical
information
so.
A
A
That
I
think
that's
the
second
type
of
blocker
we
have
is.
We
need
to
integrate
with
stuff
they
get
to
get
Sarah,
T
yeah.
So
the
the
second
second
section
where
we
need.
We
need
a
lot
of
work
to
be
done.
It's
just
like.
We
need
API
Docs.
We
need
releases
information,
we
need
in
a
very
human.
Like
a
stud.
You
know
we
have
a
whole
user
story
section
on
the
Foundation's
I'm,
probably
going
away
that
we'd
love
to
get
onto
the
site
for
the
host
that
information.
It
was
like.
B
A
A
Instruction
for
the
site
itself
was
it
kind
of
the
three
areas.
I
seem
that
we
need
to
kind
of
drive
forward
and
if
all
three
are
any
good
place,
we'll
be
able
to
flip
switching
turn
the
side
and
probably
the
the
place
where
the
most
work
can
be
done.
Right
now
is
the
application
content
and
the
integrations
so
like
just
to
unblock
the
pipes
for.
A
A
B
A
Is
like
not
to
be
rich?
What
do
we
want
to
get
out
of
the
session?
What's
the
goal
here,
yeah,
so
my
something
that
another
dude
it
sounds
like
we're
all
kind,
a
level
set
that,
like
the
goals
of
what
we're
going
to
do
long
term,
I
I,
would
at
least
personally
find
value,
and
you
kind
of
treating
this
like
it's
like
a
sprint
planning.
It's
like
that's,
actually
deep
dive
into
holding
API
Docs.
Let's
get
the
project
board
set
up.
A
Let's
make
a
bunch
of
tickets
for
the
hello
we
can
drive
against
over
the
next
month,
or
so
they
get
it,
and
then
we
can
treat
the
treat
our
regular
meetings
like
like
meetings,
so
we
can
do
you
take
that
approach
or
the
reason
you're
making
tickets
anymore?
We
can
keep
talking
about.
You
know
our
retiree
visions
for
the
future.