Return-Path: X-Original-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4A6A7D946 for ; Fri, 16 Nov 2012 12:18:18 +0000 (UTC) Received: (qmail 1730 invoked by uid 500); 16 Nov 2012 12:18:14 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 1439 invoked by uid 500); 16 Nov 2012 12:18:13 -0000 Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: flex-dev@incubator.apache.org Delivered-To: mailing list flex-dev@incubator.apache.org Received: (qmail 1386 invoked by uid 99); 16 Nov 2012 12:18:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Nov 2012 12:18:12 +0000 Date: Fri, 16 Nov 2012 12:18:12 +0000 (UTC) From: "Erik de Bruin (JIRA)" To: flex-dev@incubator.apache.org Message-ID: <383867091.123448.1353068292654.JavaMail.jiratomcat@arcas> In-Reply-To: <103345923.8862.1341498634714.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (FLEX-33134) New Apache Flex website MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/FLEX-33134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13498759#comment-13498759 ] Erik de Bruin commented on FLEX-33134: -------------------------------------- Stefan, Basically, no :-( The Apache CMS is a custom CMS loosely based on Django. It took me a (long) while to figure out how it operates, as documentation is scarce and all over the place (if it even exists). My current setup is that I have HTML copies of all the files in the "again" branche and I work on those locally. Once I'm satisfied with the result, I break the changes down into their separate template parts (header, footer, content, navigation, CSS) and update SVN. The commit to SVN triggers the 'buildbot', which pulls together the templates and content and creates new HTML that is put on the 'staging' server. This is my first 'real life' look at the results. After tweaking a bit, I get to 'publish' all staged files (not sub-sets or anything that fancy) to the 'live' server. TL;DR: make a local copy of the files, work on those and submit patches based on your changes. HTH, EdB > New Apache Flex website > ----------------------- > > Key: FLEX-33134 > URL: https://issues.apache.org/jira/browse/FLEX-33134 > Project: Apache Flex > Issue Type: Task > Reporter: Tomasz Maciag > Assignee: Erik de Bruin > Attachments: apache_flex_website_psd.zip.001, apache_flex_website_psd.zip.002, apache_flex_website_psd.zip.003, website.zip > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira