►
Description
This is a walk through of the Design Management and Wiki categories of GitLab.
A
Hi
there
this
is
Kristen
dubenko
and
I'm,
going
to
take
you
through
a
walkthrough
of
design
management
and
wiki,
which
are
both
under
the
crate
stage
and
where
the
knowledge
group
today
I'll
walk
you
through
design
management,
how
to
use
the
design
tab,
how
to
upload
an
image.
How
to
comment
on
it
and
look
at
the
history.
A
Design
management
is
new
within
the
last
five
releases,
so
it's
good
to
kind
of
refresh
everyone
that
it's
there
and
show
you
how
this
can
work
for
a
designer
workflow
and
then,
secondly,
secondly,
we'll
go
through
the
wiki
I'll
show
you
how
to
set
up
and
enable
your
wiki
how
to
create
and
edit
pages
and
how
to
do
some
basic
editing
in
the
wiki.
So
I'm
gonna
flip
over
to
my
test
project
on
get
lab.
You
can
see
I've
called
it
demo.
Corporate
website
I
could
get
led
demo
corporate
website
in
this
project.
A
We're
going
to
be
redesigning
the
get
lab
homepage.
So
there's
two
issues
here
in
the
repo
and
with
my
design
hat
on
right
now,
let's
say
I'm
the
designer
I'm
going
to
come
in
here
and
I'm,
going
to
look
for
this
header
image
issue
that
I'm
going
to
provide
designs
for
so
I
can
read
here.
My
manager
gave
me
the
issue
they
will.
A
A
A
So
you
can
see
there,
they
are
they're
side
by
side
on
the
design.
Tab,
there's
an
indicator
right
here
when
a
design
is
new,
it
shows
that's
green
if
it's
been
modified,
which
you'll
see
you
later
at
this
little
thing
goes
to
blue,
so
you
know
that
a
new
version
was
uploaded
for
that
design
and
we
can
always
add
new
designs
by
clicking
the
add
designs
button
right
here
again
that
gets
me
back
to
the
uploader
and
we
can
also
select
and
delete
designs.
A
A
Actually,
I'm
gonna
look
and
compare
before
I
make
that
decision.
So
just
using
these
back
and
forth
arrows
I
can
easily
go
back
and
forth
and
see
do
I
really
like
the
black
one
or
the
purple
one
better,
I'm
also
going
to
close
it,
and
that
takes
me
back
to
the
design
tab
where
I
can
see
them
both
together,
maybe
I'm
thinking
about
it
and
I'm
gonna
say
you
know.
A
A
You
can
see
here
that
on
that
there
was
a
new
discussion,
just
started
on
the
purple
header,
so
I
can
also
get
to
it
from
there,
because
she
mentioned
me
again:
I'll
be
able
to
also
see
it
in
my
to
do
so.
There's
lots
of
ways
to
know
to
come
back
to
comment
so
I
have
read
this
I
see
that
she
didn't
really
like
the
to
CTAs.
She
also
said
I
could
get
rid
of
this
black
option,
so
I'm,
actually
just
gonna
delete
the
black
option
right
now.
A
It's
that
one's
a
no,
so
that's
gone,
we're
down
to
just
the
purple
and
even
though
it
looks
gone,
it's
not
like
if
I
go
back
to
version
3,
you
can
still
get
those.
So
your
single
source
of
truth
is
what's
left
and
shown
here
in
the
design
tab,
but
you
still
got
access
to
the
ones
that
you
decide
to
delete.
Slash
archive
so
I'm
going
to
address
the
problem
with
the
CTA,
so
I'm
just
gonna
go
over
here.
A
I
did
I
had
worked
on
a
different
option
earlier
in
the
day,
so
I'm
gonna
flip
that
on
it's
a
little
more
subtle
and
it
doesn't
have
that
orange
I'm,
gonna
export
it
so
I'm
exporting
purple,
replacing
and
then
I'm
gonna
upload
it
again
right
here
so
I'm
going
to
use
the
exact
same
file,
name,
header,
purple
and
upload-
and
you
see
it
spin
and
it
replaces
it
can
now
see.
This
is
the
more
subtle
one
that
I
just
worked
on
and
you'll
see.
A
A
Comment
and
obviously
this
can
go
back
and
forth
until
we
arrive
at
a
decision.
I
might
also
drop
another
pin
and
say
hey.
This
sounds
weird,
not
a
great
comment,
but
just
showing
that
you
can
create
pins
throughout
and
have
these
conversations
that
are
ongoing
as
you
get
to
the
finished
product
and
so
going
back.
I
just
wanted
to
show
here
that
we
do
have
the
version.
So
if
I
go
back
to
version
4
there
there's
the
bad
CTA
one
and
then
I
come
up
to
the
latest
where
it's
been
fixed.
A
So
we
can
work
on
this
back
and
forth
and
then
eventually
hand
off
to
engineering
or
whoever
is
going
to
go,
build
it
on
the
website
using
the
issue.
So
that
concludes
the
design
management.
Walkthrough
part
now
I'm
going
to
jump
over
to
wiki,
which
is
a
little
bit
different,
but
they're
here
in
the
same
project.
Okay,
so
for
wiki,
you
can
see
here.
A
I
don't
currently
have
a
page
setup.
If
you
don't
see
wiki
showing
up
on
the
left
hand
menu.
Also,
you
may
need
to
go
into
your
settings
under
general
and
visibility,
project
features
and
permissions.
Scroll
down
near
the
bottom,
you'll
have
to
toggle
on
the
wiki
as
well
as
set
access
levels
right
there.
So
assuming
you've
got
the
wiki
on
the
first
time.
You
go
again,
there's
a
prompt
here
to
create
your
first
page.
So
if
I
click
that
it's
going
to
default
to
a
home
page
every
wiki
that
has
a
home
slug.
A
A
A
Wiki's
are
great
to
have
in
projects.
You
can
use
them
for
meeting
notes
for
research,
all
different
things
at
the
project
level
and
even
documentation.
If
you
want
to
so
I'm
gonna
hit
create
page,
and
we
should
have
the
home
page
here
now.
Currently,
this
is
the
only
page
that
I
have
in
my
site
if
I-
and
you
can
see
it
over
here
on
the
right-
it
says
home
if
I
wanted
to
add
a
new
page.
A
I
can
do
it
by
adding
this
new
page
button,
so
I'm
going
to
say
test
page
test
just
to
show
how
that
shows
up
over
on
the
right.
So
you
can
see
now
I've
got
my
test
page
as
well
as
my
home
page.
The
other
way
I
can
add.
New
pages
is
right
from
markdown.
Now
you
can
also
use
our
doc
asciidoc
or
org
to
format.
I'm
gonna
do
the
walkthrough
using
markdown,
but
you
feel
free
to
use
whichever
type
of
editing
you
prefer.
A
A
It
will
now
give
me
the
structure
to
add
these
two
interviews.
So
assuming
that
these
are
going
to
be
like
user
interviews
or
employee
interviews,
I
could
open
this
up.
You
could
see
it.
It
preserves
that
I
had
already
put
in
Doc's,
slash
interview,
1
and
then
I
can
use
markdown
to
my
heart's
content.
A
A
A
If
I
go
back
to
the
home,
page
you'll
see
that
interview
2
wasn't
created
yet,
even
though
that
still
exists.
So
whoever
comes
in
to
work
on
interview
2,
because
we
haven't
actually
created
that
page.
Yet
it
won't
be
there,
but
the
structure
will
be
so.
It
makes
it
really
easy
to
add
things
quickly.
A
Another
thing
to
mention
is
that
you
can
create
new
pages
and
edit
these
pages
via
get
because
every
wiki
is
actually
I
get
repo
behind-the-scenes.
So
that's
pretty
cool.
You
can
also
see
page
history,
which
is
really
handy,
which
you
can
see
all
of
the
updates
that
have
happened
and
that
can
help
when
you're
trying
to
track
down
a
change
or
something
that
might
have
been
missed.
A
But
overall
wiki
is
a
great
way
to
store
things
at
the
project
level.
So,
and
just
to
note,
we
do
have
coming
soon
and
I
know
that
this
isn't
usually
a
part
of
the
walkthrough,
but
we
will
be
making
wiki's
available
at
the
group
level
and
eventually
at
the
system
or
global
level
as
well,
so
you'll
have
even
more
flexion
flexibility
with
wiki's,
so
that
wraps
it
up
for
the
knowledge
group
walkthrough.
Thank
you
very
much
for
your
time.
Bye,
bye,.