►
From YouTube: GitLab 13.5 Kickoff - Create:Knowledge
Description
Issues mentioned:
Group Level Wiki: https://gitlab.com/gitlab-org/gitlab/-/issues/13195/
Wiki Deep Nesting: https://gitlab.com/gitlab-org/gitlab/-/issues/17673/
A
A
So
I'll
quickly
show
you
what
each
of
those
are
so
for
group
level
wiki.
We
are
duping
project
level,
wiki
functionality
and
moving
it
up
to
the
group
space,
which
makes
a
lot
of
sense.
If
you
have
content
that
your
whole
org
needs
to
know
about
so
here
in
this
mockup,
you
can
see
I'm
on
gitlab.org,
which
is
a
group
and
on
the
left
nav.
I
can
see
that
wiki
is
appearing
there,
able
to
add
pages
edit
pages
and
create
content
all
at
the
group
level.
A
A
What
we've
moved
off
to
mvc2
is
the
ability
to
have
git
access
and
search
to
wikis,
as
well
as
the
settings
to
turn
it
on
or
off.
So
to
get
our
mvc
out.
We
decided
to
move
those
further
out
on
the
road
map
but
be
sure
to
participate
on
those
epics,
so
we
can
get
more
upvotes
and
get
those
moved
up
in
terms
of
reaching
parity
with
project
with
ease.
A
So
that's
the
first
one.
The
next
one
has
171
upvotes,
it's
also
really
big,
and
that
is
reflecting
the
wiki's
deep
nesting
structure
in
the
sidebar.
So
I
have
an
example
of
a
test
wiki
to
show
the
problem.
That's
currently
happening
with
the
wiki
sidebar
and
what
you
can
see
here
is
I
created
three
test
pages
within
this
wiki
and
I
nested
them
one
under
a
single
level
directory
second
level
and
fourth
level
directories.
A
Now,
with
such
a
small
number
of
pages,
potentially
you
could
figure
this
out,
but
it's
very
not
intuitive
to
how
you
would
think
about
a
tree
structure.
So
it's
a
it's
hard
to
grok,
where
your
content
is
living.
A
So
what
we're
doing
what
our
solution
is
for
this
release
is:
we
are
following
common
tree
structure
for
your
content
and
it
will
nest
indefinitely.
I
think
we're
figuring
out
the
number
of
lusting
nesting
levels
we
can
achieve
with
this
right
now,
but
it's
going
to
nest
and
it's
going
to
match
the
mental
model
that
most
wikis
should
have
and
what
you
would
expect.
A
So
those
are
the
two
big
issues
that
we're
shipping
in
13-5
and
there
has
been
a
ton
of
work
going
into
these
from
the
team.
So
I'm
really
thankful
to
the
knowledge
team
for
all
of
their
work.
Getting
these
working
on
them,
scoping
them
and
it'll
be
really
cool
to
see
these
go
live
in
13.5.