Hey Syahril,
Thanks for your reply.

That's a great result for just a few days worth of work.  I couldn't do it
that quick.  I thought the site was supposed to be about ready for release
already.

I'm more of a developer/coder than a designer.

I'll be happy to help out with the coding issues and the proof-reading.

I'm good with JavaScript, jQuery, HTML, and CSS.  I haven't done any work
with Joomla specifically, but I'm good with PHP/MySQL and I'm not afraid to
dig into the code to figure something out.

I have a dedicated development server with a full lamp stack.  So, if you
want me to work on any specific issues, I can do it on my own server and
just send you changes.

I'll put some responses below, too ...

On Mon, Apr 18, 2011 at 12:14 AM, Syahril Zulkefli <[email protected]>wrote:

> Hi Ghodmode,
> thank you for your valuable feedback. Below are my response to some of the
> issues you mention.
>
>
> There were a lot of HTML errors:
>>
>> http://validator.w3.org/check?uri=http%3A%2F%2Fwww.mosc.my%2F&charset=%28detect+automatically%29&doctype=Inline&ss=1&group=0&verbose=1&user-agent=W3C_Validator%2F1.2
>
>  You're using deprecated attributes on some of your tags.  This was
>> probably picked up by the HTML validator linked above.  I noticed a language
>> tag on a script element.
>> Why do you have script elements in the body of the page?  I've read
>> arguments for putting it before or after the content, but never right in the
>> middle of the content.
>>
> - some of the errors produces by 3d party extensions, and even from
> facebook code. to be honest, i'm working on this website in few days only,
> including design mockup in photoshop, slicing, configuring extensions,
> adding + finding content, etc etc. so i dun have much time to focus on code
> validity which i assume not as important as what user see on the screen.
> maybe we can work on it after all the process complete.
>

You're absolutely right.  What's on the screen is more important especially
during development.

I'll be glad to help out with code cleanup.



> And CSS Errors:
>>
>> http://jigsaw.w3.org/css-validator/validator?profile=css21&warning=0&uri=http%3A%2F%2Fwww.mosc.my%2F
>
> - i'm using css3 code here, including border radius, rgba color, box
> shadow, gradient, etc. by using css3, we can reduce image usage on the page,
> for example for rounded corners or drop shadow. and not to mention that some
> of the code have different syntax for each browsers. i personally believe
> that using latest technology such as css3 is better even if the code contain
> errors in the validator.
>
>
> btw, nice reading for code validation:
> http://net.tutsplus.com/articles/general/but-it-doesnt-validate/
>

I haven't used CSS3 features much yet, except for experimentation, so I
guess I haven't run into validation issues with that.  I didn't realize that
the validator defaults to CSS 2.1.  There's still a bunch of errors, even
when I turn on the CSS3 and vendor extensions options for the validator, but
I realize that you haven't had time to even look at them yet.




> The Schedule, Back Stage, and Contact navigation links don't go anywhere,
>> but they add the "active" CSS class to the element regardless of which page
>> you're on.
>
> The Schedule, Back Stage, and Contact navigation links add the hash (empty
>> anchor name) to the end of the URL.  A link that doesn't go anywhere should
>> have onclick="return false;" (preferred) or href="javascript: void;" (also
>> usually works) properties.
>
> - i haven't receive content for this section yet. and like mr haris mention
> in his email, this is a first draft, there's lot of things might not
> working.
>
>
>  Clicking the link for the page I'm already on reloads the page and the
>> scroll position is at the top.  The navigation item for the current page
>> (the one with the "active" CSS class) should have the onclick="return
>> false;" property.
>
> - yup, i agree with you. maybe we will have to add this for better
> usability.
>
>
>>    - There are a lot of separately linked CSS files and a big chunk of
>>    CSS in the code of the page itself.  It would probably provide a 
>> significant
>>    performance improvement to 
>> compress<http://developer.yahoo.com/yui/compressor/> and
>>    combine all of this.  It's also a good idea to separate the presentation 
>> of
>>    the elements (the CSS) from the content.
>>
>>
>>    - There are a lot of separately linked JavaScript files.  Compressing
>>    and combining JavaScript usually yields an even greater performance 
>> benefit
>>    than with CSS.
>>
>> - i built the template using T3 framework, which comes with css & js
> minifier / compressor. but since we still in development mode, i have to
> disable this feature so i can fix any issues easier. i will enable this
> features once we are done with the site, but not for now.
>
>
> MooTools distributes a minified version 
> (here<http://mootools.net/download/get/mootools-core-1.3.1-full-nocompat-yc.js>).
>> You should use that.  Even better, take advantage of the benefits of a 
>> Content
>> Delivery Network <http://en.wikipedia.org/wiki/Content_delivery_network> for
>> MooTools.  I usually use Google's 
>> CDN<http://code.google.com/apis/libraries/devguide.html#mootools> for
>> JavaScript libraries.
>
> this is comes with joomla. too bad, i really like CDN, but at the moment,
> hacking the core code just because we want to save few KBs seems like
> wasting time. can you see i use jquery on the website as well? i'm not good
> with mootools actually. if you can code with mootools, i really hope we can
> work together.
>

I know what you mean.  With such a short time to work on the site, small
optimizations like this had to be low priority.

hehe I'm a jQuery guy, too.  I've experimented with MooTools a bit, but I
haven't worked on any serious projects that use it.

I'm pretty good with JavaScript, though.  Before I discovered jQuery, I was
obsessed with not using flash so I wasted a lot of time writing complex
JavaScript from scratch to create some of the effects that typically
required flash.




> The top part is huge.  I have to scroll below *the fold* to see any of the
>> content.
>
> yeah, i agree. when designing in photoshop, and using big monitor, i can't
> see the issue there, but yeah, it's too big and wasting valuable space.
>
>
> That fade in/out block at the top of the page looks nice, but it's not
>> doing anything useful.  Maybe it could have a position: fixed and contain
>> the nav elements?  I like having the page nav always available.  I do it on
>> my page.
>
> totally agree with you. at first, it seems so cool, but now i feel we need
> to do something about that.
>
>
> That animated image that slides back and forth is cantik, but useless.
>> None of the images are linked to anything or provide useful information
>> related to the conference.
>
> yeah, so true. unfortunately, i'm just designer, and i need to fill it with
> something before i can get 'real data' from others.
>
>
> It doesn't say "Malaysian Open Source Developer's Conference", or even
>> "Conference" in any of the page's static elements.  It only says it in some
>> of the news items at the bottom of the page.  That should probably be in the
>> banner image.  If I didn't already know what MOSC was, I wouldn't know from
>> looking at this page.
>
> so true. again, unfortunately, i'm just designer, even my english is not
> good. so i have to rely on others to provide me more useful content to put
> on the website.
>
>
> I would be happy to help OSDC with this page.  In fact, I'd like an
>> opportunity to work with CodeThePixels if possible.
>
> i very happy with your offer. yes, i really need help to finish the
> website. hopefully rizal read this and do something about it.
>
>
>
> some side story:
>
> i start designing mockup on 14 april, and posted on mailing list on 15
> april. everything you guys can see online right now, i do it in just 2 days.
> and yeah, i'm still sleepy right now because i don't have enough sleep. i'm
> so sorry, i'm not complaining, just to tell you guys 'what's going on'.
>
> everything i put on the website right now, i get it from all over the
> places; facebook group, last year website, even some of the content i copied
> from other conference websites. i know it's a bad habit, but i have to do it
> because we need something to show to our potential sponsors, something on
> the web.
>
> i really need helps to finalize the website. cikgu shaifful will help on
> setting up ecommerce and some other security things.
>
> so, what we need now is:
>
> 1. content for the website. we need more useful content about the event,
> just like Ghodmode mention.
> 2. developer to fix coding issues.
> 3. proof-reader to check any spelling or grammar errors.
>
> i'll be working on mobile devices template.
>
>
> p/s: I can speak English, tapi tidak sangat cantik juga :)
>
>
> Best regards,
>
> Syahril Zulkefli
> Manager, Joomla! Trainer, Web Developer
> http://www.codethepixels.com
>
>
>
>
> On Sun, Apr 17, 2011 at 10:11 PM, Ghodmode <[email protected]> wrote:
>
>> On Sun, Apr 17, 2011 at 11:29 AM, Harisfazillah Jamel <
>> [email protected]> wrote:
>>
>>> Team,
>>>
>>> Please give us feedback for MOSC2011 website. This is first review
>>> before we broadcast. This still under development, we need feedback
>>> and comments.
>>>
>>>
>> What kind of feedback do you want?  Do you just want to know if it looks
>> nice?
>>
>> Well, I'm a Web Developer, so I'm going to give Web Development
>> feedback...
>>
>> Many of these items can probably be blamed on Joomla.
>>
>>    - There were a lot of HTML errors:
>>
>>    
>> http://validator.w3.org/check?uri=http%3A%2F%2Fwww.mosc.my%2F&charset=%28detect+automatically%29&doctype=Inline&ss=1&group=0&verbose=1&user-agent=W3C_Validator%2F1.2
>>    - And CSS Errors:
>>
>>    
>> http://jigsaw.w3.org/css-validator/validator?profile=css21&warning=0&uri=http%3A%2F%2Fwww.mosc.my%2F
>>    - The Schedule, Back Stage, and Contact navigation links don't go
>>    anywhere, but they add the "active" CSS class to the element regardless of
>>    which page you're on.
>>    - The Schedule, Back Stage, and Contact navigation links add the hash
>>    (empty anchor name) to the end of the URL.  A link that doesn't go 
>> anywhere
>>    should have onclick="return false;" (preferred) or href="javascript: 
>> void;"
>>    (also usually works) properties.
>>    - Clicking the link for the page I'm already on reloads the page and
>>    the scroll position is at the top.  The navigation item for the current 
>> page
>>    (the one with the "active" CSS class) should have the onclick="return
>>    false;" property.
>>    - There are a lot of separately linked CSS files and a big chunk of
>>    CSS in the code of the page itself.  It would probably provide a 
>> significant
>>    performance improvement to 
>> compress<http://developer.yahoo.com/yui/compressor/>and combine all of this. 
>>  It's also a good idea to separate the presentation
>>    of the elements (the CSS) from the content.
>>    - There are a lot of separately linked JavaScript files.  Compressing
>>    and combining JavaScript usually yields an even greater performance 
>> benefit
>>    than with CSS.
>>    - MooTools distributes a minified version 
>> (here<http://mootools.net/download/get/mootools-core-1.3.1-full-nocompat-yc.js>).
>>    You should use that.  Even better, take advantage of the benefits of a 
>> Content
>>    Delivery 
>> Network<http://en.wikipedia.org/wiki/Content_delivery_network>for MooTools.  
>> I usually use Google's
>>    CDN <http://code.google.com/apis/libraries/devguide.html#mootools> for
>>    JavaScript libraries.
>>    - You're using deprecated attributes on some of your tags.  This was
>>    probably picked up by the HTML validator linked above.  I noticed a 
>> language
>>    tag on a script element.
>>    - Why do you have script elements in the body of the page?  I've read
>>    arguments for putting it before or after the content, but never right in 
>> the
>>    middle of the content.
>>
>>
>> I live in KK and the max broadband speed in my housing complex is 1Mb/s
>> down.  I'm pretty sure the best you can get anywhere in Sabah is 4Mb/s
>> down.  So, I pay very close attention to site performance.
>>
>>
>> These are just my opinion:
>>
>>    - The top part is huge.  I have to scroll below *the fold* to see any
>>    of the content.
>>    - That fade in/out block at the top of the page looks nice, but it's
>>    not doing anything useful.  Maybe it could have a position: fixed and
>>    contain the nav elements?  I like having the page nav always available.  I
>>    do it on my page.
>>    - That animated image that slides back and forth is cantik, but
>>    useless.  None of the images are linked to anything or provide useful
>>    information related to the conference.
>>    - It doesn't say "Malaysian Open Source Developer's Conference", or
>>    even "Conference" in any of the page's static elements.  It only says it 
>> in
>>    some of the news items at the bottom of the page.  That should probably be
>>    in the banner image.  If I didn't already know what MOSC was, I wouldn't
>>    know from looking at this page.
>>
>>
>> I would be happy to help OSDC with this page.  In fact, I'd like an
>> opportunity to work with CodeThePixels if possible.
>>
>> I can speak Malay, tapi tidak sangat cantik :)
>>
>> --
>> *Ghodmode*
>> http://www.ghodmode.com/blog
>>
>>
>>
>>
>>> http://www.mosc.my/
>>>
>>> Thanks to
>>>
>>> Syahril Zulkefli
>>> http://www.codethepixels.com
>>>
>>> for the design and setup of the website.
>>>
>>> and join MOSC2011 twitter and facebook
>>>
>>> http://twitter.com/mosc2011
>>>
>>> http://www.facebook.com/mosc2011
>>>
>>> MOSC2011 event page
>>>
>>> http://www.facebook.com/event.php?eid=152695794775143
>>>
>>>

-- 
To unsubscribe from and detail about this group 
http://portal.mosc.my/osdc-my-mailing-list-information

MOSC2011 http://fb.me/mosc2011 and http://portal.mosc.my/

Kirim email ke