- [Instructor] This is a
quick demonstration on Typo3
and CMS Connect.
We hope to show you, in this
demo, how you can translate
any of your Typo3 sites with no hassles.
Let's start with why you
would use CMS Connect
to translate your Typo3 content.
Well, quickly, you're
basically centralizing
all of your data sources.
Whether you have multiple
websites or a single site,
it's very easy to translate the content.
Let's face it, translating
content from your websites
is difficult, it's complex.
What we'll do is make it easy for you.
We'll allow you to use
different workflows.
So, in other words, if you
have in-house translators,
or you have subject matter
experts that need to weigh in
on your translation, it's easy to do that
within CMS Connect.
And nobody wants to manually
import jobs or tasks.
We've all had to do that, where
we're either dumping content
into an Excel spreadsheet, or
manually collecting hundreds,
if not thousands, of XML files.
Nobody really want to do that.
Of course, it opens up
all sorts of opportunity
for errors and issues.
So, by using CMS Connect,
you'll, of course, reduce errors,
and basically all of that
effort in manually emailing
or FTPing files, and quite
frankly, it's very simple to use.
So those are reasons why
you should use CMS Connect.
Now let's talk a little bit about
the Typo3 plugin, specifically.
The plugin allows you to
translate any pages, sites,
or subsites, and it allows
you to send single pages,
a selection of pages,
or even an entire site,
directly through Typo3 templates.
There is absolutely no
manual export or import
of translations, the jobs flow
back and forth automatically,
and you can even use the
internet templates to customize
translatable fields,
including custom fields
that you've created for your site.
You can also go from any
source language to any target
language, and either
direction is just fine.
So, in case you're creating
content that is, y'know,
starting in Italian, say,
and coming back in English,
that's okay, that can all be
managed through this process.
You also have the option
to send both the source
and existing translated text for approval.
That's really a great option,
because if you have some of
your own in-house translators,
or say you have an office
that is creating some of its
own content directly into Typo3
but yet you'd like to have
it approved by either someone
else, or even your translation
team, you can do that.
And we also isolate
all of the HTML markup,
so it can't be corrupted.
That's a common problem
that happens in translation
of web content.
And you can connect to
your preferred provider,
or any in-house team,
and you can easily track
all of your requests.
Later in the demo, you'll
see how you can see your
open requests in the system.
And automatically, upon the
completion of the translation,
it will insert the content
back into your site.
Alright, let's roll
into the demonstration.
So, we'll go ahead and
access this Typo3 test site
we have here, and what you'll
notice is that we've already
set up the languages, we
set up German and Danish.
We won't be able to click
on them just yet, because,
of course, there's no
translation contained
in the system yet.
But we'll go ahead and take
care of the German first.
So let's jump into the backend of Typo3.
What you'll notice is
that we've already created
configuration for the full site.
So, in other words, we
created a configuration
for the localization manager
with two languages required,
again, that's German and
Danish, and we've defined
the full site as requiring translation.
So, in this area, you'll
see we see both languages,
German and Danish, and
again, for this example,
we'll go ahead and choose German.
And then we'll create the export.
Essentially, this just
creates an XML file.
In fact, if you'd like to
click on it and just review
the XML file, you can do so.
But, essentially, this puts
that XML file in queue.
Now, remember, we've already
installed the plugin,
so you can scroll down to
the options for the plugin,
near the bottom of the
screen, and we'll head over
to the Beebox cart.
This is where you'll see
the job waiting for us
to assign it, and you'll see
that there's a status here,
and now we'll go ahead and
assign the project to Beebox.
Now, for this example, we
should note that, in order
to expedite things, what
we've done is we've connected
everything to Beebox, then
to Wordbee, which is our
translation management system,
and in order to facilitate
quick translation, we've
simply connected it
to a machine translation tool.
So, here's when we'll go ahead and send
or submit the project to Beebox.
So, at this point, this is the
screen you can come back to
to check when the translation is complete.
If you simply refresh here,
you'll always see status updates.
So now, we're just waiting
for Beebox and Wordbee
to process the file.
Alright, so we'll head over
to Wordbee and just log in,
where we can simulate
the translation process.
So we'll log in as if we
were, y'know, one of our users
or one our linguists
accepting the project.
And here's where you will
see the project in question.
Comes up as a job that's in production.
And we can go ahead
and accept the project,
and as I mentioned earlier,
we set up a workflow where
we'll just machine translate
the content, just to quickly
transition it back for
the purposes of this demo.
So, in this view, you'll
see all of the content.
If this were a real human
translation workflow,
this is the screen where the
translator would implement
all of their content, and
then, upon completion,
the editor would be alerted,
so it would be their turn
to review the content before
submission back to you
and back to your website.
And, for the sake of the demonstration,
we'll go ahead and just finalize the task.
This will then send the
translations back to Typo3, and
again, this is via the connection
from Wordbee to Beebox.
So now, back into the backend of Typo3,
where we'll go ahead and
request the translation status.
Again, if you ever want to
check progress on a job,
you come here and merely
request translation status,
and you'll notice it updated
and says that the status
of the project is finished,
the translation is finished.
So now you can submit another
action, where you're actually
going to download the translated files.
And at the point, they are
now ready to be imported.
So we'll set up another
action, where we can import
all the translated files, and
the content'll then be ready
and in the site.
Now we'll go ahead and look
at the frontend of the site,
and you'll see the the Deutsch
or German link is active,
because it contains translation.
We'll click on it.
And there it is, you'll see
all of the test translation
that we put in for this demo.
If you have any questions
about the Typo3 implementation
of CMS Connect, please feel
free to contact us any time.
Thanks for tuning in.
