►
Description
Discussion about what we can do to help users get started with pages
Epic: https://gitlab.com/groups/gitlab-org/-/epics/5330
A
A
A
Clear,
but
if
I
already
have
a
repository,
I'm
not
sure
what
I
need
to
do,
and
so
I
want
to
share
my
screen
and
just
do
the
walk
through,
even
though
I
know
that
you
know
how
to
set
up
pages,
but
lately,
especially
since
I'm
trying
to
get
up
to
speed
with
pages
I've
been
asking
random
people
that
I've
had
coffee
chats
with.
If
you
needed
to
start
with
pages,
where
would
you
go
so
so
we're
going
to
do
that
activity
together?
A
A
B
C
B
A
C
D
B
B
A
B
Because
yeah,
it's
like
a
project
templates
and
the
main
documentation,
and
maybe
the
current
docs
is
kind
of
very
extensive
and
show
you
everything
step
by
step.
But
I
would
love
to
have
something
like
a
few
photographs
just
explaining
that
yeah
in
order
to
deploy
you
just
have
to
have
a
simple
ci
cd
configuration
and
you
can
use
these
projects
as
examples
yeah.
Just.
A
A
A
A
The
beginning
of
the
yaml
file,
but
I
really
need
to
know
what
I'm
looking
for
in
order
to
use
that.
So
that's
a
little
bit
of
a
downside
and
I've
opened
some
some
issues
regarding,
like
the
fact
that
I
can
just
look
for
instead
of
html.
I
can
look
for
pages
and
that'll.
Give
me
like
a
list
of
the
templates
and
the
pipeline
authoring
team
is
now
working
on
an
editor.
C
A
B
Yeah
also
remember
that
only
for
html,
you
can
just
create
the
yaml
file
and
it
will
work.
So
if
you
take
any
other
modern
static
site
generator,
you
have,
you
need
to
have
much
much
more.
For
example,
if
you
need
jacob,
you
will
have
like
a
bundle
file
you
will
have,
and
basically
you
will
have
like
20
30
files
before
you
can
actually
start.
So
this
creation
of
the
one
yama
file
will
not
help
you
that
much.
B
A
So
I
actually
have
a
really
interesting
question
about
that,
even
though
it
has
nothing
to
do
with
getting
started
with
pages.
But
if
I
have
a
github
pages,
if
I
have
github
pages
already
set
up,
is
there
any
way
for
us
to
do
a
clean
migration,
or
do
we
have
a
procedure
for
that?
I
assume
that's
what
we're
going
to
need
for
the
self-managed
portion
of
what
we're
working
on
in
object,
storage,.
B
B
A
A
A
B
B
There
is
a
problem
actually
that,
like
currently
it's
like
what
we
show
on
pages
website
and
what
is
in
the
wrapper
is
the
different
things
right.
So,
for
example,
in
wrapper
you
have
some
markdown
files
for
jackal
posts
and
you
will
have
actual
html
files
for
the
actual
web
pages
right
interior.
We
have
this
feature
which
allows
you
to
link
one
to
the
other.
I
don't
remember
how
it's
done,
but
it's
definitely
possible
and
then
we
can
kind
of
do
what
jaime
suggests
just
show.
C
C
Maybe
I
want
to
have
a
button
here
near
my
page
that
will
take
me
even
to
that
folder,
but
it
might
be
easy
for
me
to
to
do
it
from
the
page.
Instead
of
that,
we
need
to
go
to
the
repository
and
look
for
locate
this
directory,
so
it
will
be
from
the
landing
page
next
to
each
next
to
each
page
available
a
button
for
a
folder
that
I
will
be
able
to
manage
the
files
or
at
least
see
what
I
mean.
A
C
So
this
is
actually
I'm
this,
I'm
a
user,
a
production
user
of
pages,
because
all
of
my
demos,
I
created
the
link
here
in
the
repository,
and
if
I
click
here
I
will
it
will
open
for
me
this,
but
I
don't
know
where
is
the
h
html?
So
if
I
had,
for
example,
here
a
button
that
will
take
me
to
the
this
file
there
folder
that
I
can
see
what?
Where
are
the
index
html?
C
B
A
A
So
I
think
it
would
be
helpful
to
also
show
it
in
another
place
in
the
project
where
you
have
view
only
permissions
or
not
even
view.
Only
maybe
you
can
change
the
code,
but
you
can't
push
it.
I
don't
know
different
different
kinds
of
use
cases,
so
you
know
just
someone
else
in
the
project
can
see
the
url
and
see
this
just
the
high
level
status
of.
Is
it
okay
or
is
it
like?
You
know
just
returning
a
404
and
is
unreachable,
something
like
that.
C
C
A
I
want
to
take
take
something
out
of
the
settings
I
think
having
something
under
the
settings
is
hard
to
find
and,
as
I
mentioned,
not
everyone
in
the
project
has
access
to
the
settings.
Only
maintainers
and
up
have
access
to
settings.
So
if
we
have
a
bunch
of
members
in
the
project,
but
only
two
are
maintainers,
no
one
else
has
access
to
this
page.
D
A
B
B
So
yeah
that's
a
great
idea.
Maybe
we
can
just
make
this
page
work
differently
for
people
having
different
permissions.
So
if
you
don't
have
anything
any
permissions,
you
will
not
have
these
buttons.
You
can't
remove
pages,
you
can't
add
domains,
but
you
can
see
domains
and
you
also
can
see
the
urls
assigned
to
the
phrases
like
the
simplest
iteration
that
just
to
disable
everything,
if
you
don't
have
permissions.
A
A
D
A
C
Know
another
thing
is
what
is
the
size
of
the
files,
because
I
had
a
problem
here
that
I
put
a
very
large
files
and
I
got
some
complaints
from
some
of
the
teams
here
in
the
github.
I
don't
remember
which
one,
but
it
would
be
interesting
to
know.
Okay,
I
uploaded.
I
want
to
see
what
is
the
size
of
the
files,
because
I
I
believe
there
are
limitations
for
pages,
so
maybe
this
information
also
can
be
useful.
B
C
B
Yeah
also
like
this
is
idea
for
the
future,
but
at
some
point
we
wanted
to
introduce
some
rate
limits
for
projects
like
there
are
people
who
hosts,
for
example,
source
for
very
popular
browser
extensions,
and
we
have
millions
of
requests
on
pages,
and
sometimes
it
creates
a
lot
of
loads.
So
we
want
to
introduce
some
limits
from
like
github
by
the
way
already
has
them
like
you
have
one
thousand
one
hundred
thousand
requests
free
and
everything
about
that
is
paid
or
something.
B
B
A
C
Yeah,
so
I
I
have
another
idea:
maybe
it
can
be
crazy,
but
I
will
say
it
anyway.
What
about
always
you
have
pages?
Always
we
have
a
default
web
page,
very
simple,
hello.
This
is
pages,
so
always
typing
will
have
you
have
a
project?
You
have
the
pages
very
small,
but
just
you
know
one
one,
one
one
file,
so
people
really
will
notice
the
people
will
notice.
Oh
there
is
this
feature.
This
is
interesting.
A
A
B
There
there
is
a
problem
with
that
people
use
different,
set
generators
for
right
and
they
are
all
not
simple
like
when
you
have
a
readme
file.
You
add
a
single
file,
you
don't
add
30
files
to
your
repository
and
they
do
not
conflict
with
any
other
stuff.
You
want
to
add
right,
so
I'm
sure
that's
such
a
great
idea.
Also,
these
templates
need
to
be
maintained
actually,
and
we
will
change
and
so
on.
Today
you
have
one
version
objective
tomorrow
you
have
another,
so
it
will
be
updated
like
every
time
you
click
this
button.
A
B
A
A
A
A
A
A
A
Yeah
so,
but
I
didn't
oh,
where
did
I
go?
I
don't
know
what
I
clicked,
but
going
back
what
I,
what
we
said
we
will
work
on
is
that
you
we're
gonna,
have
like
some
kind
of
way
to
help
people
out
with
jobs.
So
I'm
not
going
to
commit
this.
Don't
worry
so.
If
someone
write
pages
it'll
give
you
some
kind
of
snippet
to
help
you
get
started
things
like
that.
B
B
Again,
I'm
not
sure
how
helpful
it
will
be
since
for
most
of
the
templates,
you
need
more
than
the
yaml
file
and
the
simplest
configuration
right.
Is
it's
a
simple
job
which
copies
something
to
public
and
exports?
It's
as
an
artifact?
That's
all
it
does
yeah
yeah,
I'm
not
sure
we
can
create
some
stuff
like
jekyll
pages
or
some
other
statics
are
generated
in
pages
and
how
to
complete
this.
A
Okay,
something
else,
that's
really
cool
that
I
showed
jaime
in
our
you
know.
Our
conversation
was,
let
me
open
this
page
in
github
pages.
What
I
really
liked
about
their
pages
was
that
you
can
choose
a
theme.
I
don't
know
if
you've
seen
this,
but
they
let
you
like
just
set
your
your
website
with
different
themes
that
they
give
available.
A
B
There
is
a
public
websites.
If
you,
google,
jekyll
teams,
I
guess
to
call
these
chicken
jackal
things.
You'll
find
how
basically
all
you
all
you
need
to
do
is
to
add
some
kind
of
jam
and
one
line
into
the
jack
open
click.
I
guess
and
it
will
be
used
unless
you
use
the
gitlab
template,
because
current
gitlab
template
for
the
jekyll
hardcode
steam
and
you
actually
need
to
remove
like
12
20
files
before
you
can
use
this,
oh
wow,
which
is
super
annoying
yeah.
There.
B
Stuff
right,
but
what
did
that?
Basically,
in
the
we
use
a
special
bitclub
theme
in
this
jekyll
template
and
instead
of
exporting
it
as
an
external
repository
and
linking
it
as
a
gem
as
everything
everyone
else,
does
we
just
uploaded
it
into
the
repository?
And
now
you
can
you
need
to
remove
all
these
files
before
you
can
use
another
team.
A
B
Yes,
that's
right
can
like
one
last
comment,
what
you
just
shown
this
kind
of
gallery.
We
can
do
it
for
the
current
projects,
for
example.
Maybe
in
docs
we
can
just
have
links
for
what
projects
we
already
have
and
then
we
can
do
the
same
projectile
and,
for
example,
if
we
fix
the
default
jackal
template,
we
can
then
create
a
bunch
of
repositories
with
different
things
and
use
some
kind
of
yeah
use
them
in
the
gallery.