From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: website question Date: Mon, 3 Apr 2017 12:08:02 +0000 Message-ID: <20170403120802.27zef5ueqnj5mcbh@abyayala> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44596) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cv0mS-0008Jl-0E for guix-devel@gnu.org; Mon, 03 Apr 2017 08:08:21 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cv0mO-0000ll-Rh for guix-devel@gnu.org; Mon, 03 Apr 2017 08:08:19 -0400 Received: from latitanza.investici.org ([2001:888:2000:56::19]:34115) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cv0mO-0000lI-I4 for guix-devel@gnu.org; Mon, 03 Apr 2017 08:08:16 -0400 Received: from [82.94.249.234] (latitanza [82.94.249.234]) (Authenticated sender: niasterisk@grrlz.net) by localhost (Postfix) with ESMTPSA id E3E221200D9 for ; Mon, 3 Apr 2017 12:08:12 +0000 (UTC) Content-Disposition: inline List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org Most initial texts for pragmatique's website are now done. As I don't want to introduce it with a plain white one-page site, I thought about what I want to use. Jinja (taler.net) or Guile (guix, guile). The software part of the project is based on and into Guix, so it would be good to make use of Guile where possible. The only reason I'd choose taler.net template for is that it already has a solution for #26302 (translation of texts)[0]. As I dislike keeping changes which could be beneficial for others: If I start with an individual repo, could patches which would fix for example the translation problem still be applied "somehow" to guix-artwork although both repositories share no root but just similiar files? Or do I have to commit again into guix-artwork then to share the changes? It makes no sense for me to re-use the guix-artwork repository as too much content (graphics, texts, posts) will diverge from the one Guix uses. I guess there will be maybe 20% code of guix-artwork.git/website/ left over. What do you suggest to do? 0: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=26302