data model for multilingual website https://hubzilla.org

neue medienordnung plus

Tue, 25 Apr 2017 14:12:02 +0200 last edited: Mon, 22 May 2017 05:14:22 +0200

@Andrew Manning @Hubzilla Development+ Would we maybe use this model one channel for each website-language ?

http://hub1.sprechrun.de/page/en/hubzilla-project.html - master Hubzilla-Channel
http://hub1.sprechrun.de/page/de/hubzilla-project.html - deutsches Hubzilla-Kanal
http://hub1.sprechrun.de/page/ru/hubzilla-project.html - Русский Hubzilla-канал
etc. ...

Benefit of this "one channel for each website-language"-model is in my assessment, that:

all language-specific website-files are neatly arranged and the files can tidy import/export for each language-edition
each language-Team is responsible for own language-channel, for example en/de/ru/ ...

Notices:

Links in hubzilla-project-navbar -block must in this data model language-specific changed
The wrong layout in websites 1-3 is here not the matter. Here it is about data model for the language-sensitive website.

Edit 05-21-2017
Another advantage is that is it helpful for Hubzilla-Ranking in SERP , when each laanguage-Pages get one separate URL - s. to that subject: serverside delievery of appropriate lang-sense pageversion worsened searchengine ranking

#languageSensitive #datamodel #hubzillawebsite

datamodel hubzillawebsite languageSensitive

show all 8 comments

Andrew

Thu, 27 Apr 2017 04:51:58 +0200

I did more research, and as expected, most if not all of the functionality we need is already in Hubzilla's Comanche language! (Always assume @Mike Macgirvin has the code for all possible use cases already in the code and probably even documented in the help pages

) Here's an example of a page layout I created that might have all we need:


[template]zen[/template]
[region=htmlhead]
  [block][var=wrap]none[/var]htmlheader[/block]
[/region]
[region=content]
  [if $observer.language == en]
    [block][var=wrap]none[/var]english-content[/block]
  [/if]
  [if $observer.language == de]
    [block][var=wrap]none[/var]german-content[/block]
  [/if]
[/region]

The "zen" template allows you to make a clean HTML document with content in the <head> and the <body> sections denoted by the "htmlhead" and "content" Comanche "regions". The conditional logic supported by Comanche includes some information about the observer. The cool thing about the $observer.language parameter is that it is populated by the browser language settings already! A visitor does not need to be authenticated to get the information we need about their preferred language. I tested this by reordering my Firefox language preferences and reloading the page to see the content change.

In this example, the "english-content" and "german-content" blocks are HTML format, and they could in the case of the Hubzilla project webpage translations be the entire page.

So we have our solution. Tomorrow if I have time I'll create a new layout for the project page and integrate your German translated page so we can test if it automatically detects and loads the correct language.

neue medienordnung plus

Thu, 27 Apr 2017 08:05:25 +0200

"zen"-Template isn't by default installed, correct? Why is "zen"-Template by default not installed?

neue medienordnung plus

Thu, 27 Apr 2017 09:09:23 +0200

I suggest these german translations

with $observer.language -solution in Hubzilla-Help to include.

Andrew

Thu, 27 Apr 2017 12:06:16 +0200

"zen"-Template isn't by default installed, correct? Why is "zen"-Template by default not installed?

Ironically, the language is confusing here

Templates are the underlying structure of a layout webpage element, the the Comanche terminology. The template defines for example that there can be custom code in the HTML <head> tag, or that there will be three vertical panels of content in the <body> tag. The zen template is included in Hubzilla core. The layout webpage element populates a template with other webpage elements like blocks and menus, and as we've shown here, can also include conditional logic for what elements to display based customized for the observer.

This is in fact the primary selling point for using Comanche to construct websites in Hubzilla: you can render observer-dependent content in a decentralized authentication network. Without this feature, there is frankly not much reason to use Comanche since there are much more mature and robust website frameworks out there.

neue medienordnung plus

Thu, 27 Apr 2017 12:15:39 +0200

The zen template is included in Hubzilla core.

Is zen template include in Hubzilla-Version 2.0.6? Because the $observer.language -solution works on https://dev.hubzilla.org/page/flegno/language-sensitive-content (Version 2.3.4 at dev.hubzilla.org), but $observer.language -solution worksn't for https://hub.freecommunication.org (Version 2.0.6 at hub.freecommunication.org )

Andrew

Thu, 27 Apr 2017 12:19:12 +0200

Oh that may be true but Ich weisse nicht. Do you know how to search the source code? Perfect pristine documentation is always the ideal, but in practice many questions can be rather easily answered by using an IDE like NetBeans to search the Hubzilla code.

neue medienordnung plus

Thu, 27 Apr 2017 17:06:33 +0200

The perfect case would be, when I choice had one Comanche training/ webinar to absolve :).

hEARt PhoniX

Thu, 27 Apr 2017 21:26:20 +0200

It's not that hard. I will think about an online course.
#toDo for next weekend, starting on Wednesday.