►
Description
In this session we cover the final steps we need to take to completely decouple the handbook and marketing websites in the www-gitlab-com repo.
A
B
A
In
last
week's
issue,
refinement-
and
I
think
you
know
like
michael
watched
that,
obviously
and
and
the
fact
that
we
don't
have
to
do
that
is-
is
definitely
going
to
be
a
benefit
in
terms
of
just
this
specific
issue
and
then
the
the
issue
that
deals
with
the
progress
you
know
he.
He
also
was
very
open
to
the
idea
of
using
this
this
well.
A
A
D
A
A
So
when
you
click
save
it
introduces
this
extra
capture
step
and
then
once
that's
done,
is
we
no
longer
wait
for
the
the
promised
chain
to
complete
before
we
transition?
We
immediately
transition
to
this
interim
state
where
we
we
fire
off
those
promises.
Those
three
promises,
the
creating
the
branch
creating
the
the
commit
and
creating
the
merge
request,
and
we
use
those
promise
chains
to
just
update
the
progress
of
what's
going
on.
C
E
A
Cool
all
right,
in
that
case,
I'm
not
gonna,
spend
any
time
on
that
today.
I
do
want
to
then
move
on
to
this
next,
one
completely
decouple
the
handbook
from
the
marketing
site
assets
you're
more
than
welcome
to
to
stay
around
for
that
one
derek.
But
I
understand
if
you
want
to
drop
off,
but
this
is
one
that
chad
and
I
have
a
big
interest
in,
because
this
is
our
our
last
big
kind
of
like.
Well,
it's
our
second
la
the
last
big
decoupling
effort.
A
E
E
A
A
G
G
The
third
one,
that's
not
really
covered
in
design
and
navigation
is
like
the
functionality
like
functionality.
That's
currently
shared,
you
know,
job
roles
or
sections
or
any
of
the
dynamically
generated
helpers
stuff
that
currently
appears
on
both
sides.
I
think
that's
like
the
biggest
other
major
area
and
like
not
keeping
an
instinct
for
those
means
it's
going
to
go
to
one
place
or
the
other
and
either
not
be
in
in
the
one
or
included
via
an
iframe
at
runtime
or.
A
From
a
design
and
navigation
point
of
view,
and
once
the
marketing
site,
redesign
and
serious
conver
conversion
has
been
completed,
we
will
consider
working
towards
consistency
to
allow
for
future
navigation
consistency.
The
marketing
site
should
consider
generating
its
navigation
options,
either
from
a
data
file
or
a
headless
series
data
source.
So
the
handbook
can
reuse
that
data
source
and
to
allow
future.
E
G
G
A
G
G
I
don't
have
the
web
page
up,
I'm
just
looking
at
the
monorepo
yemel
and
seeing
that
we
had
to
add
direction
as
something
that
is
used
from
both
plages
both
places.
I
think
there's
some
page.
I
don't
know
the
exact
url
of
it
in
the
handbook
that
renders
dynamic
information
related
to
the
the
direction.
G
A
A
G
G
A
G
C
G
G
G
A
So
so
highlight
tooltip
that
that's
something
that
we'd
have
to
duplicate,
and
you
know
that's
a
piece
of
functionality
that
that,
if
they
wanted
in
the
marketing
site,
then
they
they
need
to.
You
know,
duplicate
and
maintain
for
now
and
we
need
to
create
a
you
know,
we
can
create
an
external
package
for
it
over
time,
but.
A
A
A
C
C
C
C
G
A
A
D
G
A
G
And
in
this
case
it's
like
it's
there's
a
lot
of
stuff
and
it's
like
directly
coupled
to
the
structure
of
the
company
like
there's
something
to
change
all
the
time.
And
it's
really
important
to
keep
in
sync
that
you
really
wouldn't
want
to
duplicate
like
if
you
live
in
one
place
or
the
other
or
it's
guaranteed
to
get
out
of
sync
and
the
sort
of
thing
people
are
going
to
care.
If
it's
out
of
sync
can't
have
one
site
misrepresenting
the
the
structure
of
the
company
or
the
direction
of.
F
G
A
Yeah
that's
severe
and
to
be
to
be
honest,
the
directions
section
is
is
one
of
those
that
is,
I
mean
it
looks
like
handbook
pages,
you
know,
and
I
you
can
probably
make
an
argument
that
it
is
handbook
and-
and
it
is
because
you
know
it's
it's
strategy-
you
know
it's,
but
you
could
also
make
a
case
for
that.
It's
not
so
it's
one
of
those
weird
words.
What
I
actually
want
to
so
another
one,
for
instance,
is
job
famines.
You
know
that
for
me
feels
like
it's
something
that
should
be
in
our
handbook.
A
You
know
it
it's
job.
Families
are
part
of
how
we
kind
of
like
run
our
business.
You
know
that
should
be
part
of
the
handbook
and
I
I'm
actually
going
to
create
an
issue
to
let
let's
actually
do
this
while
I'm
at
this.
I
want
to
create
an
issue
that
that
resolves
these
gray
areas
and
makes
a
call
on
the
is
direction
part
of
the
handbook
or
or
the
marketing
site,
because
we
just
need
a
definitive
call
on
that
that
that's
my
point
of
view
on
this.
A
A
A
A
A
A
G
C
A
F
G
C
F
C
C
A
D
A
Isn't
it's
called
type
typo?
It's
one!
It's
one
that
I've!
It's
it's
just
a
markdown
editor!
I
I
don't
like.
Sometimes
I
just
wanna
like
raw
edit,
a
file,
but
I
don't
always
want
to
write
in
mark
and
I
sometimes
want
to
be
wizardwig
mode,
but
I
want
the
markdown
source
and
so
I'm
trying
it
I'm
not
sold
on
it
yet,
but
giving
it
a
go
anyway.
D
A
G
A
Yes,
but
okay,
so
so
my
the
principle
here
that
I
think
is
the
the
file
should
follow
the
site
like
I.
I
don't
think
we
should
have
anything
in
the
top
level
of
the
repository
that
it
that
relates
to
you
know
like
ultimately
what
I
really
wanna
wanna
wanna
see
is.
You
know
like
if
this
is
the
top
of
our
repo.
I
want
to
see
data
and
I
want
to
see
sites.
A
G
A
G
I
know
how
to
resolve
that
we're
talking
past
each
other.
You
need
another
entry
here,
which
is
everything
in
the
root
and
like
that
implies
some
other
things
that
are
in
these
folders,
such
as
bin
steps.
So,
like
everything
in
the
root
includes
the
package
json
and
the
gem
file,
you
know
the
ruby
and
the
known
ecosystem
that
those
both
imply
stuff
under
bin
and
and
live
in
other
places.
A
G
F
G
A
G
F
G
F
A
G
A
A
We
like
it
has
to
for
various
reasons,
and
the
other
thing
is,
you
know
like
base,
so
you
you,
for
instance,
I'm
I'm
referring
to
that
issue
that
carl
opened
about
you
know
the
stages
and
and
categories
yammer
file.
You
know
that
that
that
they
use
for
the
labeling
of
of
issues
and
so
on.
This
is
so
many
services
outside
of
the
handbook
and
the
marketing
side
that
use
these
data
files.
You
know,
I
mean
they're
pretty
much.
A
You
know
the
lifeblood
of
of
many
services
in
the
company
that
keeps
things
going
and
and
having
them
actually
in
the
in
the
the
repo
here
makes
them
feel
in
a
way,
like
you
know
like
new.
It
doesn't
bring
that
seriousness
in
terms
of
the
fact
that
changes
to
these
can
actually
break
things
that
you
know,
systems
that
we
build.
You.
A
G
Now,
when
they
came
up
yesterday,
when
I
was
helping
ken
johnson
was
like
his
problem
was
he
was
trying
to
use
just
the
data
dot
object
directly.
You
know
the
the
one
middleman
exposes
directly
from
yeah
existence
of
a
yaml
file
under
data,
but
what
he
really
needed
to
use
to
emulate
the
page
he
was
trying
to
copy
was
to
use
these
class
wrappers.
We
have
which
correspond
to
them.
G
There's
like
a
group
class
which
is
really
a
smart
rapper
that
consolidates
some
a
lot
of
the
data
files,
there's
category
and
there's
others
so
that
that
stuff
lives
under
lib.
I
think
mostly
under
lib,
but
maybe
these
other
directories
is
very
tightly
coupled
to
the
the
structure
of
the
data,
at
least
the
existence
of
their
data
files.
So
those
really
aren't
going
to
move
to
one
side
or
the
other
if
the
data
doesn't
because
they're
directly
tied
to
but
this
structure,
but
this
mean.
A
F
G
All
of
that
logic
in
it
and
it
would
just
expose
you
know-
json
interfaces,
graphical
standard
api
and
then
which
marketing
if
they
want
to
go
the
route
and
the
other.
You
know
non-handbook
groups
in
the
company
if
they
want
to
go
the
same
route
of
using
different
tools
than
middleman
or
some
or
front
men.
A
G
A
A
A
C
F
A
G
F
A
G
F
G
F
A
D
G
A
Because
but
because
they're
they're
lips
you're
like
I
actually
think
that
look
might
be
one
of
those
that
we
keep
at
the
top
level,
then
because
they're
not
actually
they're,
not
related
to
any
side
they
their
logic.
The
logic
of
the
of
the
code
isn't
necessarily
dedicated
to
a
site
as
far
as
I
can
see,
and
it
it
doesn't
have
to
move
with
a
site
like.
G
D
F
A
A
A
C
A
G
Are
specific
to
handbook
some
they're
specific
to
marketing
and
some
are
pretty
general
like
how
middleman
works
or
how
you,
you
know,
run
the
dev,
but
I
think
most
of
them
should
be
specific
to
one
or
another
legal
blog
product,
yeah,
okay,
contributor
license
agreements.
I
don't
know
those
get
duplicated
or
not.
G
D
A
C
A
G
G
C
A
A
A
G
A
G
G
F
B
A
A
F
F
F
G
C
G
A
G
C
C
D
A
A
G
G
G
A
Well,
we've
consolidated
all
of
the
conversation
and
we've
got
a
we've
got
to
we've
got
principles.
We've
got
execution
plan,
we've
got
further.
So
essentially
this
is
the
plan
and,
like
you
mentioned
something
to
refer
back
to
when
somebody
asks
what
what
happened
here.
You
know
like
this.
Is
it
so?
What
I'm
going
to
do
is
I'm
going
to
ask
lauren,
brandon
and
michael
their
manager
to
review
this
again
and
make
sure
they're
happy
with
it
as.