►
From YouTube: Best Practices SIG - July 12, 2023
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
A
A
A
C
A
B
B
C
C
A
D
We
need
to
go
the
other
way,
I
think
because
we're
we're
on
a
very
outdated
version
of
Doxie
and
Hugo
and
I
I
spent
the
morning
going
through
about
a
hundred
updates
just
to
see
what's
changed,
and
it
looks
like
quite
a
lot
of
the
internationalization
of
stuff
that
we're
going
to
need
to
use
in
later
versions.
So
that's
probably
why
it's
not
doing
what
we
expected
zero.
C
Though
that
is
a
very
interesting
thought,
some
of
it
could
certainly
be
related
to
that,
but
the
container
construction,
also
just
you
know,
does
does
well
it's
bad.
It
does
like
Pips
and
and
wgets
and
other
types
of
things
so
that
that
had
platform
related
things.
Okay,
so
I'm
sorry,
the
I
was
just
gonna.
Go
look
at
your
ticket.
C
Where
did
it
go
issues
upgrades
you
go?
Okay,.
D
So
I
had
to
do
this
for
City
events,
and
it
was
a
fairly
major
piece
of
work
and
they
had
less
modifications
than
than
we
have.
D
So
it's
it's
definitely
going
to
be
a
slog
there.
There
are
some
significant
changes
from
where
we
are
to
to
the
later
versions,
including
some
a
completely
different
way
to
actually
import
doxy
as
a
as
a
library.
C
D
Yeah
you
should
you
should
be
able
to
see
what
I
did
on
on
that
one.
D
Where,
where
we're
gonna
have
some
difficulties,
I
think
is
that
I
I
wrote
a
number
of
bits
of
styling
stuff,
which
we've
added
to
the
doxy
layout.
To
allow
us
to
do
things
like
those
little
speech
bubbles,
and
so
we're
gonna
have
to
make
sure
that
we
pour
all
of
that
stuff
across
as
well.
D
But
yeah
so
there's
a
there's.
There
are
some.
There
are
several
layers
of
conflict
changes
that
we'll
need
to
make
in
order
to
upgrade
to
later
versions,
and
some
of
that
will
mean
porting
over
style
sheet
changes.
D
D
And
that
was
a
little
while
ago,
so
I
imagine
there
also
lagging
behind
again
now
and
there
may
be
another
serve
additional
changes
that
we
need
to
make
to
get
us
up
to
current
release
version.
C
Okay,
I
found
a
commit
that
you
and
Andreas
worked
on
revised
refresh
44
change
files
with
1600
Editions.
C
B
C
C
B
C
B
A
B
Some
words
in
in
in
English
similar
your
questions
about
the
best
practice
is
continuous
delivery.
Best
practice
and
I
need
your
opinions,
your
success
questions
and
for
maintained
in
English,
or
translate
all
the
content
to
Spanish
but
I
think
in
in
the
in
the
beer
we
come
to.
This
could
discuss
this.
This
topic,
okay,.
A
D
D
B
B
B
C
D
That's
that's
a
that's
a
a
problem
in
English
that
you
you
you
need
to
manage
because
of
you
know,
subtleties
of
Clauses
so
where,
where
those
problems
don't
occur
in
different
languages,
we
don't
need
that
whole
sentence
where
there
are
similar
problems
but
different
words.
The
words
should
be
translated.
B
B
B
Okay,
okay,
this
is
this
is
my
my
one,
one
good
question
and
the
peers
propose
I
propose
at
the
end
of
the
old
website.
Translation
up
for
Section.
Is
that
good
approach?
B
D
So
where
we
are
at
the
moment
is
that
the
the
version
of
Hugo
we're
running
on
in
production
doesn't
support
blending
two
languages
into
one
View,
there's
no,
so
you'll.
Only
if
you
go
to
the
Spanish
version.
You'll
only
see
the
pages
that
you've
actually
translated.
You
won't
see
any
of
the
other
English
documentation,
so
that
would
tend
to
encourage
us
at
the
moment
to
try
and
do
as
much
of
a
translation
as
possible
and
then
release
the
whole
thing.
D
D
Useful
so
so
I
think
right
now,
there's
less
advantage
to
doing
an
incremental
release
of
translations,
but
there
will
be
a
benefit
once
we've
upgraded
the
platform.
A
B
C
D
D
A
D
Think
the
the
big
decision
on
on
that,
if
I
remember
correctly,
was
that
in
initially
Doxie
was
something
that
you
added
to
your
own
repository.
So
you
actually
stuck
all
the
all
the
doxy
in
your
repository
as
a
folder
hierarchy.
C
C
D
D
Need
to
look
at
how
we
then
override
some
of
the
rendering
to
allow
us
to
do
the
little
tricks
that
we're
doing
at
the
moment.
C
C
D
Yeah
I'll
definitely
help
you
to
to
get
through
this
stuff.