flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ashish Desai - Zootar <ashish.de...@zootar.com>
Subject Re: [DISCUSS] New website content
Date Tue, 03 Jul 2012 01:47:50 GMT
I need a little information on how the CMS works with web. Is there a page that describes it?
Want to leave the scope for integration while  we create working HTML pages.

Ashish Desai
Zootar LLP

On Jun 29, 2012, at 9:53 AM, Nicholas Kwiatkowski wrote:

> Flex is for applications, not full websites.  HTML is the way to go.
> We may want to wait for Tomasz's design next week.  I'm sure it will give
> us a great head-start with the entire thing.
> Sharing via GitHub would make sense.  Based on the stuff in GitHub, I can
> put stuff on our staging server, so we can see how it works with our CMS.
> -Nick Kwiatkowski
> Apache Flex PPMC Member
> quetwo@apache.org
> On Thu, Jun 28, 2012 at 9:26 PM, Ashish Desai <ashish.desai@zootar.com>wrote:
>> Based on the prototype that Tomasz had created, I have already started
>> working on the web page creation.
>> Need some inputs on following:
>> Should i build it in flex or HTML and JS?
>> How can i share the work i have done with the DEV team as i don't have
>> committing rights yet?
>> Ashish Desai
>> ashish.desai@zootar.com
>> On Jun 28, 2012, at 4:09 AM, Tomasz Maciąg | Fuse Collective wrote:
>>>> Open@Adobe content should be under Creative-Commons (CC_BY_SA) so I
>> think
>>>> you don't have to worry to much about copying text.
>>> I think Nicholas was referring to Adobe website not open@adobe. Sadly
>> there isn't much at http://sourceforge.net/adobe/flexsdk/ which we could
>> (beside about text)
>>>> I wonder if we can grab an old features list from the old Flex SDK page
>> on
>>>> Adobe's site.  Not the text, but at least the highlighted features...
>>> There are a lot of stuff we could use so this was my initial idea. I've
>> already asked Alex about possibility of using content form Adobe site and
>> it seems to be not an easy task and it would require some effort.
>>> I think for now we'll start with what we have right now and we can
>> always add new pages later on. I'll try to compile some texts about
>> features because IMO this is must have on start.
>>> --
>>> Tomasz Maciąg
>>> Fuse Collective
>>> www.fusecollective.com

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message