flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erik de Bruin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLEX-33134) New Apache Flex website
Date Fri, 16 Nov 2012 12:18:12 GMT

    [ 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:


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.


> 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

View raw message