Milosh those look really excellent! Ok let me finalize a logo and propose it as the new logo. Lets hope it doesn't start a war. I will comb through the fonts suggested and see if there is a licensed one I can complete the word mark with that fits the logo well.
On Thu, Apr 4, 2013 at 6:50 PM, Milosh Vujnovic <mil...@techcolossus.com>wrote: > Hi Andrea, > > thanks for explaining that thoroughly -- at least we'll know what are > options are. > I guess the current website is operating on IIS, if it isn't LAMP stack, > right? > > As for your question - no this wasn't made with the purpose to be > implemented into Wordpress. > It was prepared to be converted with Boilerplate HTML5 framework, then we > can move on from there and either use some form of a CMS, or think of some > other way of managing website content. > /* > *//*Re: PSD and then convert to HTML with a responsive framework or use > Wordpress*/ > Yes actually that was one plan, PSD > HTML > Wordpress, but as I pointed > out above, we're not confined with Wordpress. > > -- > > To other collaborators - please feel free to comment out everything. > > If there are any copywriters involved, it would be great - I noticed large > "gap" inside current OpenOffice website - content is disorganized, main > points and features are not properly explained and placed (this is > extremely crucial to optin rates), and other details as well. If there are > content writers out there, I would like to hear their thoughts on this. I > can lend marketing perspective on it and we can work something out. > > Best, > Milosh > > > > On 4/5/2013 12:40 AM, Andrea Pescetti wrote: > >> Milosh Vujnovic wrote: >> >>> http://techcolossus.com/**openoffice/OpenOffice-V01-**Milosh.jpg<http://techcolossus.com/openoffice/OpenOffice-V01-Milosh.jpg> >>> >> >> Quite nice! I remember that you had suggested two options, i.e., PSD and >> then convert to HTML with a responsive framework or use Wordpress. >> >> The first one may be architecturally feasible (the "Apache CMS" is not a >> real CMS, but a simple infrastructure to automate some inclusion of common >> elements and allow markdown syntax); on the other hand, Wordpress would be >> rather problematic, since we don't have a PHP-enabled infrastructure at the >> moment and storing pages in a database does not fit with the current >> workflow. I hope this attempt is not assuming that we can use Wordpress, or >> any LAMP CMS for that matter. >> >> Regards, >> Andrea. >> >> ------------------------------**------------------------------**--------- >> To unsubscribe, e-mail: >> marketing-unsubscribe@**openoffice.apache.org<marketing-unsubscr...@openoffice.apache.org> >> For additional commands, e-mail: >> marketing-help@openoffice.**apache.org<marketing-h...@openoffice.apache.org> >> >> >
