►
From YouTube: Service concept design mockup
A
Hello,
so
this
is
my
super
simple
mock-up
for
the
service
concept.
It
will
show
a
Details
page
and
and
the
Matrix
of
deployments,
but
let's
start
with
the
details
page,
how
I
imagine
it
we
are
already
in
the
fancy
API
one
page.
As
you
can
see,
there
are
multiple
tabs
here
and
now
I
did
just
the
revisions
tab
and
or
this
could
be
actually
releases
as
well,
not
just
revisions.
A
A
They
have
a
pipeline
attached
which
likely
have
a
pipe
United.
Let's
say
like
that:
they've
been
deployed
at
a
certain
time
and
date
and
they
have
a
given
rollout
status.
One
is
at
90
percent
traffic
serving
the
other
serves
the
remaining
10
percent
to
the
traffic,
and
that
made
me
even
multiple,
but
like
no
more
than
three,
and
mostly
just
one.
A
Moreover,
there
is
a
change
log
where
I
would
show
a
bit
more
than
just
the
title
of
a
changelog
there's
just
not
not
much
space
on
this
paper
and
anyway,
I
want
you
likely
all
of
it.
It's
more
like
a
like
an
echo
Dion
that
that
you
can
click
on
to
see
all
of
the
change
log
with
the
read
more
button,
and
this
changelog
should
include
things
like
what
are
the
merge
requests
that
were
built
into
this
release,
artifact
and
other
extra
art
ifacts
that
are
referenced
by
this
artifact.
A
A
They
were
not
deployed
yet,
as
you
can
see,
and
no
such
status
exist
and
there
is
again
a
change
log.
That's
related
to
that,
of
course,
with
the
fancy
API,
there
would
be
some
genetic
metadata
that
we
said
like
like
the
the
for
the
searching,
and
there
might
be
the
description
with
the
links.
All
of
that
I
would
add
actually
as
tabs
here
or
in
some
other
way,
but
they
I
don't
think
they
are
necessary
to
be
seen
all
the
time
now.
A
When
somebody
clicks
on
one
of
these
revisions,
even
in
the
2.0.21,
what
we
are
clicking
on
this
page,
then
we
show
that
yes,
this
is
the
breadth
comp.
We
are
in
fancy
API
1
version
2.0.2
and
first
we
see
a
summary
of
the
status
where
it
was
deployed
to
a
given
version
at
some
date
to
staging
at
a
different
date
and
actually
later
on,
I
had
to
throw
that
in.
A
We
could
even
show
what's
currently
in
the
previous
environment.
If
there
is
a
more
recent
version
outstanding
that
version
already
there,
then
there
might
be
staging
where
we
are
right
now
and
then
we
are
pending
approvals
in
QA,
let's
say
and
then
there's
a
dotted
line
for
the
future,
where
we
don't
say
anything
about
it,
like
spending
Improvement,
nothing
like
that.
A
Besides
this
summary
view,
I
would
show
something
like
a
Facebook
wall.
I,
don't
know
how
it's
called
today
or
history,
where,
at
the
top
I
added
a
few
call
to
actions
like
promote
the
next
stage
immediately
or
reject
comment
box
books
where
you
can
comment
or
comment
and
approve
at
the
same
time,
but
before
that
there
are
just
like
more
messages
from
the
history
of
this
release
like
it
was
deployed
to
staging,
is
the
last
one,
and
before
that
there
was
some
Security
checks
running,
for
example.