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

Re: [lojban] taking action



Using the Jekyll static website generator with a plugin to support multiple languages seems like a good solution to me, although I don't have experience with it yet so happy for other suggestions?

https://jekyllrb.com/
https://github.com/Anthony-Gaudino/jekyll-multiple-languages-plugin


From: lojban@googlegroups.com <lojban@googlegroups.com> on behalf of Timothy Lawrence <timothy.lawrence@connect.qut.edu.au>
Sent: Monday, 22 August 2016 10:16 PM
To: mriste
Subject: Re: [lojban] taking action
 

Definitely there is an argument for simplicity. Raw HTML and CSS is simple from a web development perspective, and it was my first thought, but I feel that using HTML may alienate non-web-developers.

I was thinking about using a format that is even more accessible to everyone, perhaps Markdown, that can be used to generate the final HTML pages from a simple template.
That would separate the text content from the website structure and style, making it more easily translatable and manageable.

My suggestion for the workflow organisation utility is Phabricator because it doesn't require users to have GitHub accounts. I think the project could also be made available on GitHub if it is useful for others, but GitHub is another thing that may alienate non-programmers as it has a high learning curve. I subjectively found Phabricator more intuitive, but we may need to trial it.

Because Phabricator is open source, we could translate it to Lojban or otherwise customise it. It can also automate things like rebuilding the static website whenever a change is made or new translation is committed, et cetera. Come to think of it, it could probably automate much of the deployment of various Lojban projects (including the CLL, although I don't know much about its development so I am not sure).


From: lojban@googlegroups.com <lojban@googlegroups.com> on behalf of uakci <ciuak.prog@gmail.com>
Sent: Thursday, 18 August 2016 4:08 PM
To: mriste
Subject: Re: [lojban] taking action
 

I propose that it be a plain HTML site, constantly synchronizing to a Github repository which, in turn, will be connected to workflow organization utility.

~ mi'e co'a se tolzdi be lo nu cusku lu mi'e la uakci mu'o li'u .e lo simsa be ri do'u mu'o ~


On Aug 18, 2016 6:02 AM, "Timothy Lawrence" <timothy.lawrence@connect.qut.edu.au> wrote:

> What sorts of help do you anticipate wanting/needing?

I am not knowledgeable about much of the history of Lojban and what has been tried/achieved already, so I would need someone(s) advising me.
I am not proficient at Lojban itself, at this stage.
I am not proficient at translation workflow, or at doing translations myself. Any recommendations from others (especially translators) would be appreciated.
I would likely need assistance with any Lojban.org server systems administration.

I also need the explicitly defined design goals of the website, so nothing is missed.

My suggested shortlist is that the website should:

- advertise Lojban effectively
- provide accessible up-to-date resources for learning Lojban
- be up-to-date in translations for all target languages
- clarify the distinction between official and non-official information
- function as a centralised nexus for the community
- invite involvement in the community and connect Lojbanists
- make it easy to manage community projects
- have a low cognitive barrier-to-entry
- work easily on both desktop and mobile

From those goals, I would research to select (or build) a system that enables or automates protocols/workflows for achieving those goals.

I believe it's important to use software with a strict workflow from the start, because humans are fallible and forgetful. This will ensure adherence to the goals never accidentally slips.

This is why I personally don't think a wiki is very suitable for official information and maintaining concurrent translations.

If we have a list of persons who must approve new content, for example, the system shouldn't allow it being published until everyone from that list has approved.

If we have a protocol to manage translations, it should be trivial to enforce that no single language version should be updated on the live website without all target language versions being updated for the change. The system should automatically notify the appropriate translation volunteers as new content is added, then wait for them before the new content can be committed.

I have heard of .PO files being a popular, open-source format for translations, with an established workflow, but I have not used them.

Hope this helps,

mi'e la.timoteios.




From: lojban@googlegroups.com <lojban@googlegroups.com> on behalf of karis <comcaresvcs@gmail.com>
Sent: Wednesday, 17 August 2016 10:19 PM
To: lojban
Subject: Re: [lojban] taking action
 
The Board discussed some of the problems with the current website situation, including difficulty identifying official vs not official material. I would be happy to mention you are offering to work on the mess. What sorts of help do you anticipate wanting/needing?

karis

--
You received this message because you are subscribed to the Google Groups "lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lojban+unsubscribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at https://groups.google.com/group/lojban.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lojban+unsubscribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at https://groups.google.com/group/lojban.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lojban+unsubscribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at https://groups.google.com/group/lojban.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lojban+unsubscribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at https://groups.google.com/group/lojban.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lojban+unsubscribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at https://groups.google.com/group/lojban.
For more options, visit https://groups.google.com/d/optout.