[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [libreoffice-documentation] SEO for LO online help?


Hi Claire

Search Engine Optimization is close to black magic and a moving target
exercise that Google and others SE lay to prevent frauds and unfair
behaviour.

At the moment, each release of the online Help pages have thousands of
web pages per language and a few basic and proven techniques for SEO,
notably sitemap of all pages and Schema.org that you suggest.

The work was done in 2017 when the new online help was designed. At that
time, I implemented

<body itemscope="true" itemtype="http://schema.org/TechArticle";>

<h1 itemprop="articleSection" id="hd_id3153884">The LibreOffice Help</h1>

for all the Help. However I couldn't measure if the recipe worked
because SEs have their own pace for indexing the pages and our volume
isn't so appreciated by them.

Furthermore, our Help system is historically a mix of Reference contents
and User Guide contents, which makes the selection of the right schema a
challenge. Solutions exist but need a bit more work to improve the
internal XML of our Help, such that pages can have the right indication
of its semantics.

So the use of Schema.org looks simple at first glance but it brings
several issues to our current Help implementation.

- The video shows a very simple HTML editing that works with a dozen of
pages. When it comes to 1000's times 50 languages it becomes impractical
to do it manually.

- LibreOffice has its Help pages in Extensible markup Language (XML) to
simplify Help editing, reuse of contents and be translation friendly. As
said above not every page will follow the same schema, and the
transformation from XML to HTML must therefore consider the semantics.
This is not yet implemented.

- Each change in paragraphs attributes such as "itemprop" example above
in the source XML will trigger retranslation of the paragraph contents
wrapped by the <h1></h1> tags, a job our translators often complain.

Sorry for the techy lines above, the idea behind Schema.org is
interesting and is implemented since 2017, but it is still far from
optimal and I'd like to have some assurance that the energy to spend in
this technique worth the effort.

Kind regards
Olivier



Em 18/07/2019 21:53, Jean Weber escreveu:
> Please send LO-related email to the list, not to me personally. Thanks!
> Jean
>
> ---------- Forwarded message ---------
> From: Claire Wood <clairedwood@googlemail.com>
> Date: Fri, 19 Jul 2019 at 07:43
> Subject: Forwarded from Ellis Pratt (linkedin.com/in/ellispratt):
> https://youtu.be/4rRFuonBTw0
> To: <jeanweber@gmail.com>
>
>
> Hi Jean, I don’t know who manages the online help but are there plans for
> ranking instructions via search engine optimisation? I thought this video
> by Ellis was very good and worth sharing.
>
>
> https://youtu.be/4rRFuonBTw0
>

--
Olivier Hallot
LibreOffice Documentation Coordinator
Comunidade LibreOffice
Rio de Janeiro - Brasil - Local Time: UTC-03:00
http://tdf.io/joinus

--
To unsubscribe e-mail to: documentation+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/documentation/
Privacy Policy: https://www.documentfoundation.org/privacy

References:
[libreoffice-documentation] SEO for LO online help?Jean Weber <jeanweber@gmail.com>
Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.