Este es un tip muy conocido pero hay personas que recién se están adentrando al tema de programación web y el uso de HTML que desconocen esto y luego les conlleva a algunos problemas de visualización, de esta manera es que alguien me pregunto porque las páginas que realizaba no se veían igual en los diferentes navegadores. La respuesta es que los diferentes navegadores a pesar de ser miembros de las W3C no respetan las normas impuestas por este consorcio.

Entonces es necesario “inicializar” o resetear los elementos HTML, para no dar muchas vueltas simplemente añadir este código al inicio del archivo CSS.

html, body, div, span, applet, object, iframe, h1, h2, h3, h4, h5, h6, p, blockquote, pre, a, abbr, acronym, address, big, cite, code, del, dfn, em, font, img, ins, kbd, q, s, samp, small, strike, strong, sub, sup, tt, var, dl, dt, dd, ol, ul, li, fieldset, form, label, legend, table, caption, tbody, tfoot, thead, tr, th, td, center, u, b, i
{
vertical-align: baseline border: 0;
outline: 0;
font-weight: normal;
font-style: normal;
font-size: 100%;
font-family: inherit;
}

*
{
margin: 0;
padding: 0;
}

body
{
line-height: 1;
height: 100%;
}

:focus
{
outline: 0;
}

ol, ul
{
list-style: none;
}

table
{
border-collapse: collapse;
border-spacing: 0;
}

blockquote, q
{
quotes: “” “”;
}

hr
{
border: 0;
color: #000;
background-color: #000;
height: 1px;
}

blockquote:before, blockquote:after, q:before, q:after
{
content: “”;
}

O W3C Brasil disponibiliza um guia de CSS em português, quando falamos de CSS falamos de tipografia, cor, layout, alinhamento, acessibilidade…

E ainda tem designer que diz que CSS é coisa de programador….

Versão online

Versão em PDF ( 10MB )

היום החלטתי שאני אכתוב על כללים הבסיסים ביותר שבונים פורום או אתר.
למה אני כותב את זה? בגלל שהרבה אנשים ביקשו ממני עזרה עם הפורום שלהם לפני שהם בדקו את הדברים הבסיסים ביותר ולמדו עליהם אז החלטי להקדיש את הפוסט הזה לכללים הבסיסיים ביותר שצריך במילא להרחיב אבל אז זה יהיה ממש ארוך.
המאמר הזה מתאים גם לאתרים וגם לפורמים אתם צריכים רק לחשוב איך כל דבר חל גם על השני.

זהירות הפוסט די ארוך, אז תכינו לעצמם כוס שתייה ומשהוא לאכול לפני!

1. למה לבנות פורום בכלל? יש הרבה אנשים שמתחילים עם הרעיון שהם רוצים פורום בלי שיהיה להם מושג למה? איך? כמה? ומה המטרה.
   - התשובה גם בדרך כלל כי אנשים רוצים להתחרות עם פורמים גדולים אחרים, ובכן יש לי הפתעה לכל פותחי הפורמים למיניהם! שיענו לי על שאלה פשוטה, מה החידוש בפורום שלהם מכל השאר? כמו שנאמר “מה נשתנה?” כדי שיהיה לכם משהוא מעניין, כי אחרת למה שיבואו לפורום שלכם ויעזבו את הפורום שמוכר להם עם הקהילה שלהם? (והאגו שלכם זה לא סיבה טובה) בנוסף לזה אתם צריכים למצוא כמה אנשים שיריצו את הרעיון ביחד בתור שותפים לפשע כדי שיהיה הנהלה וצוות מקצועי. אם אתם רוצים שזה יהיה מעין פורום סגור ועצמאי, אפשר גם לפנות לבעלי פורום קיים ולפתוח תת פורום אצלו ולהדר עם סיסמא רק שייתן גישה בשביל אנשים שאתה רוצה וככה תחסוך המון כסף זמן.
2. באיזה מערכת פורמים תשמשו בשביל הפורמים, ידוע שיש אנשים שקונים רישיון למערכת פורמים תמורת 500 ₪ למרות שהם יכלו לקבל תמורה לא פחות טובה ממערכת חינמית, השאלה היא גם לאיזה צורך צריך את הפורום ולכן צריך מערכת מתאימה, גם כמה שליטה ועיצוב והגדרות את צריך בפורום לאיזה מטרה הפורום, מספר המשתמשים וכו’ וכו’. (מערכת פורמים בחינם).צריך לדאוג גם למהירות הטעינה – כדי שהמערכת תהיה קלה כדי שלא ייקח יותר מידי זמן להיכנס לאתר ובכל זאת עם שליטה קלה בעיצוב ועם לוגיקה בצורת הבניה שלו. ומומלץ כאלו עם קוד כמה שיותר נקי.
3. שרת – יש לכם שתי אופציות להשתמש בשרת חינמי או אחד שתשלמו עליו. בשרתים בתשלום המחיר של שרתים שונה ממטרה למטרה ולאופציות שיש בו, הטיפ הכי טוב זה לדבר עם אחראי פורמים פעיל שאתם מכירים בגלל שהמידע מתעדכן ומשתנה כל הזמן, אבל כדי שתיזהרו כל אחראי יש העדפות משלו לדוגמא יש כאלו שרוצים SSH או כתובת אימייל וכו’ וכו’, בכל שרת בסיסי יש בדר”כ FTP, גיבוי כל זמן מסוים, תמיכה כל הזמן ותחזוקה. שרתים חינמיים הם מאוד מוגבלים יחסית ואין הרבה אופציות. שרתים כאלו טובים בתור התחלה ללימודים או לפורום קטן וביתי לכמה חבר’ה.
4.  שימושיות ועיצוב – האתר צריך להיות שימושי לא משנה כמה יפה האתר, אדם שלא יכול להשתמש באתר בגלל שהוא בנוי בצורה לא מקצועית, לא הגיונית ולא נוחה יעדיף אתר אחר. לכן הכלל הראשון זה שהאתר צריך להיות בנוי באופן הגיוני או לפחות עם הוראות שימוש כל שהם, ועדיף שיהיה נקי מבחינת מראה ולא עמוס מידי כדי שייקלט ע”י העין בצורה מהירה. וזה שהאתר שימושי לא אומר לא לנסות עיצובים חדישים.
   העיצוב של האתר הוא די חשוב. אסור שהעיצוב יהיה “כבד” מדי לעין כי אחרת האתר לא נוח ואנשים יכנסו לאתר. העיצוב צריך לכלול רווח אבל לא בשפע כדי שלא יראה ריק, במקביל שלא יהיה במסגרות עם קווים כדי שלא יראה סגור, כיום העיצוב מומלץ להיות בצבעים בהירים יחסית או כהים ומבריקים, שהאיקונים לא יהיו ישרים מידי כמו בווינדוס 98 ולא עגולים כי זה יראה ילדותי מידי. אנשים גם מתלהבים מעיצוב של איקון חצי שקוף. בכל זאת שאתם מעצבים אל תוסיפו פלאש כי זה מכביד על האתר ומעריך את זמן הטעינה ואז יהיו כאלו שלא יכנסו ולכן מומלץ להשתמש בPNG. גם תיזהרו שלא תעשו עיצוב מרהיב מידי ואז לא ישמו לב לתוכן, לסיכום העיצוב צריך להיות לא כבד מידי כדי שהאתר יעלה במהירות סבירה, ושיהיה איזון בין הטקסט לתמונות, ושיהיה נוח לעין.
5.  סגור או לקהל הרחב – חלק מהחלטות לגבי הפורום הוא: מה קהל היעד? ועל מה הוא יעסוק? אם לדוגמא בחרתם לקהל רחב, איזה קטגוריות צריך שיהיה בפורום ואיך אפשר לחלק את זה באופן הגיוני שיאפשר גישה מהירה.
6. חוקיות – מה משותף לעורכי דין ולכריש? ברגע שהם מריחים מישהו פצוע הם באים לטרוף אותו. לכן שאתם בונים פורום אתם צריכים לדאוג גם לחלק החוקי אפילו שהוא לא נראה חשוב. זכרו עדיף לעבוד קצת קשה בהתחלה מאשר להצטער אחר כך. יש כל מיני נוסחים לפורמים ואתרים, הנוסח שאני ראיתי בתור המקובל הוא שמי שכותב בפורום מוותר על זכיות יוצרים על היצירה שלו, ושבעל הפורום לא אחראי על הכתוב, וכל הטקסטים שמה הם תחת רישיון שהוא לא זכיות יוצרים (GPL,CC וכו’) שתבחרו בעצמכם אחרי שתקראו אותו בעיון רב כדי למנוע מעצמכם מאוחר יותר בעיות של תביעות מחברות גדולות.
7. דרכי פרסום – זה השאלה השנייה בחשיבותה, איך אנשים ידעו על הפורום ואיך תשכנע אותם להיכנס לפורום? הדרכים הנפוצות והפחות יעילות הם לפרסם בעזרת פייסבוק, איסקיו, מסנג’ר ותחרויות בנית אתרים. העצה שלי שאם יהיו המון לינקים טובים לתוכנות, מאמרים ומידע שאנשים רוצים ושהם מחפשים אז אנשים שימצאו את זה דרך גוגל ישתמשו בזה יעבירו לחברים שלהם ויגרמו גם לזה שהדירוג יעלה במנוע החיפוש גם אם הזמן יהיה תופעת חבר יביא חבר, ואחרי שתעברו כמות מסיומת של משתמשים תפרסמו גם סטטיסטיקות שככה ישכנעו אנשים בקלות.
8. כמה זמן תשקיעו – הפורום יושפע במראה לפי זמן ההשקעה בו, ולכן צריך להיזהר שלא ישקיע הרבה בהתחלה ואז לאט לאט הוא יפסיק עם ההשקעה כי ההתלהבות הפסיקה. הטיפ שלי זה לארגן כמה חברים טובים ומומחים למיניהם להיות בצוות של הניהול ככה שחלוקת הזמן תהיה הוגנת בן האנשים ולא יהיה לחץ רק על אדם אחד. אבל צריך להיזהר לא לתת ליותר מידי אנשים כוח כי אז הם יתווכחו בניהם מה כל אחד יכול לעשות, אז נסו לארגן מעין “דרגות” של ניהול.
9.  חוקים בסיסים – יש די הרבה אנשים שלא מכירים לצערנו את חוקי ההתנהגות הבסיסים כמו לא לקלל, לא להספים וכו’, אם אתם מתכננים פורם המוני תכתבו חוקים בסיסים לפחות כדי למנוע את הבעיות בטענה שלא ידעתי, ואם אתם רוצים להדר על תיוג לכל נושא, ולהוסיף חסימה לרובוטים.
10. בטיחות מפני האקרים ופריצות – שיש מערכת מפורסמת פשוט תדאגו שהיא תהיה מעודכנת (ואל תשכחו לגבות לפני העדכון), ולא מומלץ לנסות גרסאות בטא. שיש מערכת פורמים לא מפורסמת תהיו זהירים יותר, תעדכנו את המערכת יותר, ובדקו עם אנשים שאתם מכירים מאבטחת מידע את הפורום ואל תשכחו לשים למנהל סיסמא ארוכה מאוד שכוללת אותיות ומספרים.
    בניה לפי התקן – יש ארגון עולמי שהשם שלהם הוא The World Wide Web Consortium (W3C) הארגון בעצם אחראי על האינטרנט, אבל אין לו שום כוח שמכריח אנשים. הארגון פרסם תקן של קוד של כתיבת אתרים שבזכותו כל אתר יופיע אותו דבר על כל הדפדפנים, ככה שהאתר יוצג בצורה דומה בכל הדפדפנים ובכל מערכת ההפעלה. הדפדפן שידוע בתור הכי בעיתי הוא Internet Explorer 6 , אבל חוץ מהדפדפן הזה כל השאר יציגו את הפורום בצורה דומה ואם אתם רוצים אתם יכולים להוסיף לפורום את אחד מהבאנרים הבאים (כולל קוד לפורום) דבר שיגרום לאנשים להבין איך לגרום לאינטרנט להיות לפי התקנים, ודבר שיגרום לפורום להראות מקצועי וברמה גבוהה כמו כל הפורמים שבחו”ל)
    חוץ מהצגה דומה בכל הדפדפנים, שמירה על התקן מונע פריצות ע”י האקרים בגלל שהקוד ייכתב בצורה יותר בטוחה ויותר נקייה, אם אתם רוצים לבדוק שהאתר בנוי לפי התקן שלכם את מוזמנים עם הכתובת הבאה http://validator.w3.org/ .לעוד מידע בנושא התקנים תמצאו http://www.standards.co.il/

Informations sur les principaux standards du Web.

Learning HTML:A Report on the Evaluation of

Three Educational Resources

Description of Audience

The HTML section on the W3Schools Web site begins with a very brief, but plain-spoken introduction to what HTML is and how it works. The writing throughout the site is clear and concise and appears to be without grammatical errors. In fact, the HTML tutorial keeps descriptive text, or body copy, to a minimum and uses “Try It Yourself” in-browser HTML text editors (see Interactivity section of Evaluation). There could be a negative aspect to the sparse description on the site. More description of the concepts could provide useful context and help the learner gain a more comprehensive understanding of HTML concepts.The W3Schools HTML tutorial layout is simple and functional (one would hope so, since the whole point is to teach Web design). One negative aspect of the Web page layout is a disorienting amount of text that surrounds the main body of the Web pages where the tutorial information is located. Although the navigation menu on the left, under the heading “HTML Basic” is useful, the banner advertisements and those on the left hand side of the screen are distracting. Also, the links to other tutorials for CSS, XML, Javascript and more are not needed. It would be easier to focus on learning HTML if superfluous text were removed.

Nonetheless, if the user focuses on just the tutorial information, the Schools have created a logical, step-by-step process to gradually familiarize the reader with HTML and related concepts. The Web site’s pages are short and the user can utilize the navigation menu on the left hand side of the page for links to other parts of the tutorial, as well as buttons that are present on every page labeled “<<Previous” – to go to the previous page of the tutorial – or “Next Chapter>>” – to go to the next page in the tutorial. Furthermore, within each page, the Schools have utilized easy-to-read headings, such as “What is HTML?” “HTML Documents = Web pages” and “What You Need,” which contextualize the text that follows and aid the reading process. Overall, the site follows a simple formula: it briefly introduces a concept in HTML and then provides a “Try It Yourself” text editor to apply the concept. Although coding jargon is used on other parts of the site, if the user follows the step-by-step process through the tutorials, it explains the terminology well.

Interactivity

First, the most useful and often used interactive component of the HTML tutorial is the “Try It Yourself” in-browser text editor. Once the user clicks the “Try It Yourself” link, he is shown a page such as the one below. The user then edits the text in the left hand box and clicks “Edit and Click Me>>” and the box on the right displays how the markup would look in a browser.

This text editor is extremely useful because it gives the user a tool for the concept in question and see the result. Of course, there could be improvements. For example, there are no recommendations on the page for alternatives or supplements to the simple concept that the user is practicing. In the example image above, it might be useful if the page provided a quick tip on how to make horizontal lines extend only 75 percent across the page. In any event, the ability to see one’s markup instantly rendered is a very useful educational tool.Although the in-browser text editors are the most important interactive component, the Web site also has other useful functions by virtue of its status as a Web site. The functionality of hyperlinks to quickly take the user to another site for information is an important component of a Web page’s interactivity. In addition, the navigation menus mentioned earlier allow the user to jump back and forth to different parts of the tutorial with ease.

Cost

The W3Schools are completely free, because they were created by individuals in the non-profit organization the World Wide Web Consortium (W3C). Because they are free and provide useful tools like the text editor, not to mention that the Schools were created by the governing body for Web standards, this is an invaluable resource that should be at least one part of an educational toolkit.

Resource #2: Castro, E. (2007). HTML, XHTML & CSS. Visual quickstart guide. Berkeley, CA: Peachpit Press.

Quick Evaluation Summary

Pros: The book provides a comprehensive introduction to (X)HTML and CSS in an accessible format and layout at a relatively low price.Cons: Because it is a paper book, it doesn’t have the same interactivity and concomitant benefits as the W3Schools Web site. Also, it will go out of date, whereas Web sites will be updated.

Detailed Evaluation

Resource #3: Online Course, e.g. University of Washington Course – INFX 503

*Note: I am treating this course as an example of a beginning HTML course. There will be variations on course design depending on the instructor and the institution. I am currently enrolled in the course, which provides me access to the resources and the unique perspective of having experienced how the class design unfolds week to week.

Quick Evaluation Summary

Detailed Evaluation

Accessibility

Interactivity

Cost

Sólo tienes que escribir o pegar una URL en el formulario y haz clic en “Check it” para ver la magia. Si deseas afinar tu validación, haz clic en “avanzado” . That’s it!

World Wide Web Foundation Launches Operations and First Projects

Speaking at the Internet Governance Forum in Sharm el Sheikh, Egypt, Tim Berners-Lee announced today that World Wide Web Foundation is open for business. World Wide Web Foundation was created with W3C’s support in September 2008, and focuses on advancing the Web as a medium that empowers people to make positive social and economic change.

Web Foundation’s first two projects will help people to better leverage the Web to support agriculture in near-desert environments in Africa, and empowering youth in inner-city centers by teaching them how to create Web content. Such projects are consistent with W3C’s own work to ensure that One Web is available to all, including work on mobile Web for social development, accessibility, and internationalization. W3C looks forward to collaborating with World Wide Web Foundation to further lower barriers to access and to promote the development of free and open Web standards.

Source w3c

Hi all,

Today is the third day of my trip and the first day off the IGF conference.

Today was full and exciting as expected!

Scroll down to the subject that interests you.

Backdoor  Censorship

In the morning we went to the main opening session of the IGF, where I met (thanks to Dima) Robert Guerra who among other things, did a large evaluation of the policy in freedom of expression around the world. I asked him if the latest Israeli phenomena, where pressure is put on the governments to pass censorship laws for the Internet that are disguised as laws against child pornography. He told me this is terribly common. I am actually quite alarmed, as someone against Internet filtering. It seems the only solution that people can come up with for stopping child pornography and other illegal activity on the net, is to block the Internet in a way that might turn it to just another corporation and government tool.

Open Standards and Microsoft

After the main generic session, a new friend of mine called : Jeremy Malcolm, told me on the #igf chat channel on IRC to come join the open standards workshop. I just walked in time to hear Microsoft’s response about a claim (that I missed) that government document formats need to be open source. Quickly I found that no one was listening to each other: Microsoft said what they think (closed source solutions), Sun said what they thought (They actually coined the term semi-open solutions) and so did the human right person too (they like open source). Here is an  example: There was a mention on the panel that in a certain country there was a voting system that was only working in “some browser”. Microsoft would never support such a claim, they just changed he subject.

Its a shame because the issues raised where interesting, mostly about e-goverment policy – Should they support more than one standard? or should the government impose standards on others. There was also a talk about the fact that a lot of existing solutions are in most cases sing closed protocols because those tools were mostly developed by companies in the private sector.

I am worrid about what is going to happen in 30 years, with no standard how could we open historical documents from the archives if we can’t open them?

Main Session with Tim Berners-Lee, founder of W3C

The opening session had quite an number of important people. the ministry of communication in Egypt, followed my the Prime Minister, this was quite an honor.

The lecture after them was smart and with a nice prospective  - Tim Berners-Lee, the founder of W3C gave this talk. He started talking about how the http protocols were written, and how the count of web pages grew to be about the same amount of brain cells he has (joking that the difference is that the number of web pages is rising, and his brains cells number is going down) . Then he continued to tell how W3C had developed its agenda where everyone should be connected. They started working on multilingualism followed by attending the needs of people with disabilities, who actually find the web a lot easier to use for certain daily things. He continued to talk about the new mobile web and how most of he people I the world today are going to encounter the Internet for the first time in their lives via a cellphone and not a PC. His final statement was that W3C is launching a new organization called W3F, he tweeted this on stage, Sadly I could not re-tweet this because the Internet just crashed at that time.

Israelis in the IGF – ISOC IL and the Embassy

As I exited to the lobby I was approached to my surprise by someone talking to me in Hebrew. This was Oren Marmorstein from the Israeli Embassy in Egypt, who came all the way from Cairo to visit us. Apparently the Ministry of Communication told him about us. At the same time we finally found Rimon Levy, the head of Israeli Internet society (ISOC-IL), and all of a sudden there were 4 of us speaking Hebrew in the lobby.

A talk with Rimon on ISOC-IL and the new localized domain names

One of the hot topic in IGF this year is that they are launching this week what they call international domain names or IDN. This means we will have domain names in unicode supporting not only Latin characters. I asked Rimon if we are going to have those in Israel and how they will work.

He told me that the Israeli domains would actually be right-to-left. So the parsing of the links will go in the opposite direction (even when combining with English). There is also the question of who will be the IDN register in Israel. It seems important that we will make sure in Israel that the IDN control will not fall in to a commercial company hands, because this would mean the money spent on domains would not go back to the community.

Another thing I asked was how the Israeli domains are going to look like, ICANN who is in charge of domain registration requires that the county domains would contain something related to the country, although “. ישראל” Is quite long to be added to every Internet address. ISOC-IL did not come with a solution yet. So I would love to pass ISOC-IL suggestions for Israeli domain names here if you comment!

By the way,  I asked Rimon why a few weeks ago there was a lot of criticism made by bloggers about the management of ISOC-IL and he said he is not really sure himself, so if any of you bloggers are reading I would like you to comment on this (flame responsibly).

The Big Dinner and a talk with one of the founders of the Internet

Dima is among other things trying to compile a biography of Jon Postel, one of the key people during the founding of the Internet, at a certain time he was the person you had to give a phone call to register a domain. At the dinner, we were introduced by Walda (that I met in ITU Telecom 2008) to a person called Robert Kahn, who knew John and actually passed the domain registration work to him after he found it to be too annoying.

Robert told us all along the dinner stories on how the Internet was formed. It was fascinating! I was peculiarly fascinated by the fact that he is the one that invented the format of IP addresses where you have to separate the bytes by a dots (like 127.0.0.1). He did that to distinguish between Internet IPs and the ARPANET addresses. He told us how they tried to implement other communication systems before they Internet that did not work (using radio and satellites among other things), how finally they arrived to Internet and how they got it bridged with other networks that existed at the time. He told us how slowly the world took interest in the Internet and that it became all of a sudden a worldwide network, interesting organizations like the ITU, UN and countries.

Tomorrow is my last day, so I hope I will manage to blog

Dima., Oren from the Israleli embassy, Rimon from ISOC-IL, 'Gbenga from Nigeria and me

Opening Panel

Robert Kahn and me

Natten till fredag den 13:e denna månad sov jag ingenting nästa. Bara massa idéer. En av idéerna var att starta upp mitt bloggande om webbutveckling igen och dela med mig av över 14 års erfarenhet.

Här kommer ni kunna läsa om HTML, XHTML, CSS, CSS-hack, Explorer-problem, webbdesign, Photoshop, klassisk ASP, ASP.NET, ASP.NET MVC, MySQL, SQL Server, W3C, standarder, och mycket annat. Det kommer dels vara upplagt i form av lösningar på mina egna problem som jag berättar om, men även i form av grundläggande och avancerade kurser samt introduktioner.

Stay tuned!

1. Den første regl er læse retning. Tænk øverst til venstre først. Det vil sige, for at rangere højt på Google, så er det vigtigste din url og sidens titel tag. Der næst er det første overskrift og sidens andre overskrifter, så til sidst børdtekst.
2. Navngiv dine sider, varer eller artikler med de ord, som din brugere leder efter. Hvis du vil sælge brugerne vandhaner, så nytter det ikke at du helst vil kalde det amature. Det er der ingen der søger efter. Brug Google Insights til at sammenligne ord og synonymer, så du er sikker på at du bruger dine brugeres ord.
3. Udfyld dine meta-tags. Brug dit description tag med omtanke. Det er nemlig den tekst Google vil vise under linket til din side. Hvis ikke Google mener teksten i description passer til siden, vil søgemaskinen selv finde afsnit på siden, som robotten mener passer bedre. Selv om ingen søgemaskiner bruger keyword tagget til noget som helst. Så udfyld det alligevel. Nogle Social Bookmarking sites bruger dette tag, som guide til søgeord i deres systemet.
4. Få styr på teksten i dine interne links. Et link til en nyhed eller mere information om en varer skal ALDRIG angives med: “Læs mere…”. Hvem er det, der leder efter information om “Læs mere”? Lyder det ikke meget bedre med: “Ny intelligent skruetrækker – Læs mere”. Sådan. Nu er der tekst med der fortæller hvad der er bag linket, og det er klart for brugeren, at der kan findes mere information bag linket.
5. Trafik til din side har betydning for din placering og din PageRank. Skriv letlæselige korte afsnit, og hold øje med din afvisningsgrad. Design siden, artiklen og teksten, så du får en lav afvisningsgrad.
6. Brug Social bookmarking sites som Delicious, Propeller, StumbleUpon og Digg, der alle har god ranking på Google, til at skabe trafik og give dig PageRank Boost. Bookmark dit indhold og brug tid på at lave dine beskrivelse, titler og tags på de forskellige sider forskellige, så der ikke bare er kopier af det samme.
7. Brug Google Analytics og hold styr på dine indgående links. Det som kunderne og andre websites skriver i teksten, på links til din side, fortæller også Google, hvad din side handler om. Så du skal ikke være for genert til at kontakte sider, der linker til dig, og foreslå dem en tekst til linket, til din side, hvis de kun linker med “Læs mere” eller dit firma navn.
8. Brug alt tags på billeder til, at inkludere de mest almindelige stavefejl. På den måde kan du også ligge top 10 på ord, der slet ikke findes, men alligevel ofte søges.
9. Overhold W3C standarderne. Det gør det lettest muligt for Google at læse, forstå og indeksere dit indhold.
10. Brug micro-formats tags til angivelse af adresser. Dem bruger Google Maps til, at placere din virksomhed i verden, og tildele virksomheden kontakt information.

Overhold de 10 regler her, og så er du ikke bare godt på vej op i søgeresultaterne på Google, men du vil også opleve en fin stigning i trafik til din side.

El futuro de las comunicaciones será la web móvil, declaraciones de nuestro compañero Martín Alvárez en el XXV aniversario de la Facultad de Informática de la Universidad de Murcia.

World Wide Web Consortium (W3C)

W3C



I was recently asked to be a Guest Writer for Karmagate – a leading publication on New Media and Digital Marketing. Here is my article.

Guest Post: Debate between Flash vs. JavaScript HTML based websites

Our guest writer today is Aneesh Varma, who is the co-founder of FabriQate, an award-winning international Digital Agency. They do sites and web platforms for startups all the way up to large clients, and we figured who better to ask about this topic.

Flash has taken off as a popular way to show elegant features and fun effects on many brand websites. Especially since the growth of sites like YouTube, most of the people online now have Flash compatible browsers – so its a medium a lot of creative companies often adopt since its also easier to “develop” in.

However, the key element there is that most of the brands are being advised by their creatives – who often don’t want to know the tech aspects behind web dev and choose Flash for its simplicity to build in. While the output is great, there are some issues (like you mentioned):

1. Generally Flash is sealed file – so search engines cannot index the text (ie: site content is not searchable – the Invisible Effect as its locked in an image).
2. Content updates cannot be done by end-user (you) since you need to re-export the source file (think of PDF document vs. Word document)
3. Site often becomes heavier in terms of content and longer to load. And despite the people moving to faster broadband connections – the wait times are quite annoying and you can lose some visitors
4. If no Flash is installed on the browser, you get a blank site (with that annoying blue question mark box)
5. Not compatible with all mobile phone browsers (growing sector as people adopt iPhones and smartphones) – this might change in the near future
6. Cannot run analytics & stats such as Google Analytics which are crucial to monitor and improve customer journey

Now, while some of those can be addressed by using innovative ways of hybrid development like encoding an “Old Style” HTML site under the Flash to give some SEO etc – it does mean you are building a site twice (and then super-imposing on top of each other).

More over, generally speaking – while Flash sites tend to be great visual pieces, from a usability perspective (called W3C standards) – they are quite difficult to use since they have unique buttons and alternate navigation structures that confuse even experienced web users.

You might have an array of clients from various fields of business, and surprisingly a lot of them are novices about web interfaces – and anything different or strange can repel them away. The corporate page you are trying to build is to act as a selling tool for the business as opposed to an interactive feature that can be launched on a second micro-site or slogan-site.

See: http://waterlife.nfb.ca/ and  http://www.marcecko.com/#/ as examples of fun sites for brands that sell themselves or micro-sites for campaigns, but not corporate sites. These are fully in Flash

In the development community (ie: real web developers), there is the concept of using JavaScript nowadays (sometimes called AJAX). It allows you to still build a traditional site that adheres to W3C, has all the SEO features, lighter pages to load, mobile compatible AND has the Jazz and Transitions that a lot of users think are Flash.

For example, if you look at the major sites put out by leading internet companies like Facebook, Google Maps and even Twitter use JavaScript for all the transitions and effects.

Here is a great example this site:  http://www.melissahie.com/ she really used great features of JavaScript (which people often get confused for Flash).
(Easy way to determine Flash site is to right click on site – and you will see a menu on which the last item is “About Adobe Flash…”)

As a company we have always advised our clients to use the right technology for their purposes. While Flash is a great tool for media capsules and animation boxes on web pages, I think full corporate or main websites should not be in Flash.. and rather use HTML (PHP) JavaScript based combinations. Use Flash for elements on a webpage – not the whole thing. And if you still insist that you want a full Flash site, it should be limited to micro-sites and campaign sites rather than main corporate sites.

However, the most important element of any site remains the content, and the rest is just a guise to make it more attractive. So do focus on the content!

Hoy he tenido la oportunidad de asistir al Taller sobre Nuevos Estandarés Web impartido por el W3C en la Facultad de Informatica de la Universidad de Murcia. Ha sido un taller muy interesante donde se ha hablado sobre nuevos lenguajes y me ha parecido de especial atractivo el tema de la Web Semantica o  lo que algunos vienen a denominar Web 3.0.

Para aquellos que desconozcan el termino les dire que la web semantica se basa en la idea de añadir “metadatos semanticos y ontologicos” a la Web. Esos metadatos , describen el contenido, significado y la relacion de dichos datos y permiten a las maquinas interpretarlos y analizarlos y asi poder ofrecer respuestas digamos que de alguna manera “inteligentes”.

Lo que se persigue con esto es por ejemplo conseguir que un buscador tipo Google sea capaz de interpretar nuestras busquedas de manera coherente, busque el significado real de aquello por lo que preguntamos y nos devuelva siempre una respuesta que se corresponda con lo que nosotros realmente le hemos pedido que busque. Seria genial que nosotros hicieramos una busqueda tipo “de que color es el caballo blanco de Santiago” y directamente el respondiera “BLANCO”, cosa evidente para nosotros pero que un buscador no es capaz de resolver actualmente de forma tan efectiva. Google, si haceis la prueba con la pregunta de antes devolveria en sus  primeras respuestas, lo siguiente:

Como veis Google hace una busqueda por palabras, busca aquello que se corresponde con lo que nosotros hemos puestoy nos ofrece resultados que equivalentes, pero no nos ofrece una respuesta acorde a lo que nosotros realmente buscamos, aunque sea tan obvio como esto. Obviamente conseguir un buscador global apoyado en web semantica es algo que tardaremos en ver bastante tiempo.

Para aquellos que este tema les parezca interesante les aqui les dejo enlaces a Wikipedia donde podran ampliar informacion acerca de la web semantica y los estandares en los que se apoya (vease tambien SPARQL, SWRL entre otros), otro enlace al W3C donde podreis encontrar informacion relacionada con el Taller sobre Web Semantica y por ultimo un enlace a una pagina que incorpora un pequeño buscador semantico,EDUCARM.

Espero este articulo pueda ayudar a alguien a comprender algo mejor que es esto de la web semantica y puedan comprender el tremendo potencial que tiene.

Op 2 november is de publieke beoordeling gestart van de voorlopige Nederlandse vertaling van de internationale richtlijnen voor kwaliteit en toegankelijkheid van websites (WCAG) 2.0. Onder leiding van Stichting Accessibility hebben 26 organisaties aan deze vertaling meegewerkt. Zij roepen nu iedereen op om de vertaling op juistheid te controleren. De nieuwe richtlijnen zullen net als in de rest van wereld de komende jaren de basis gaan vormen voor de kwaliteit en toegankelijkheid van websites.

De Richtlijnen voor Toegankelijkheid van Webcontent (WCAG) 2.0 zijn opgesteld door het World Wide Web Consortium (W3C) en omvatten een groot aantal aanbevelingen om webcontent toegankelijker te maken. Velen kennen de vorige versie van deze richtlijnen al omdat die onderdeel uitmaken van de Webrichtlijnen van de overheid. Het volgen van de nieuwe Richtlijnen zal content niet alleen toegankelijker maken voor mensen met functiebeperkingen en senioren, maar ook voor gebruikers in het algemeen. Door toepassing van de richtlijnen worden websites ook beter bereikbaar, beschikbaar, bruikbaar en betrouwbaar voor bezoekers, browsers, zoekmachines en websites worden beter bereikbaar via mobiele telefoons.

Na een beoordelingsperiode van dertig dagen zal de huidige versie waar nodig aangepast worden. In december 2009 zal de definitieve versie klaar zijn voor gebruik. Iedereen kan reageren. Beoordelaars kunnen opmerkingen maken over de juistheid van de concept vertaling. Het is niet mogelijk om inhoudelijke opmerkingen te verwerken. De louter voor deze beoordeling gepubliceerde versie is niet de definitieve versie en kan niet als aanbeveling gebruikt worden worden. De vertaling volgt de // officiële vertaalprocedure van het World Wide Web Consortium (W3C) voor geautoriseerde vertalingen.

Doelgroep voor de vertaling zijn niet alleen de professionele webbouwers en webmasters, maar bijvoorbeeld ook studenten die voor een schoolopdracht of gewoon voor hun plezier een website bouwen. Het traject wordt geleid door stichting Accessibility.

Op public-auth-trans-nl@w3.org kunnen betrokkenen opmerkingen plaatsen. Het originele Engelstalige document is te vinden op http://www.w3.org/TR/2008/REC-WCAG20-20081211/.

Voor een overzicht van de deelnemende organisaties en voor meer informatie kunt u terecht op de website van stichting Accessibility: http://www.accessibility.nl/internet/WCAG20/WCAG20.htm

Todos los que trabajamos haciendo web, o los que de alguna manera estamos relacionados al mundo del internet, sabemos que ver una web en distintos navegadores como Firefox, IEplorer o Safari, tiene resultados distintos. La razón de esto es el cumplimiento o la interpretación que le da cada una de estas aplicaciones a los estandares de la W3C.

Foto por Windows Reference

Si no hemos experimento ver cómo una página se mueve, descuadra o cambia en algo mínimo en algún navegador distinto al que solemos usar, es porque nunca cambiamos de navegador. Muchos son fieles al Firefox, otros al Safari, y la mayoría pobremente al IExplorer, que en su versión 8 no le encuentro nada como para tirarlo al piso.

Aunque parezca raro y quizá no me lo creas, es que hay seres extraños, que viven entre nosotros y pasan desapercibidos, que parecen gente normal pero no lo son, aún no se sabe muy que especie son, ni si son de este planeta, pero queda claro que existen desde muchos años antes de nosotros. Estos seres son los que INEXPLICABLEMENTE USAN IEXPLORER 6, sí, es cierto y si estas viendo este artículo desde IExplorer 6, te pediría que cierres esta página y te largues.

El repudio por estos seres extraños no se debe a su apariencia física, ni a la creencia por sus dioses, sino al hecho de que son los seres que hacen desdichada la vida los que quieren hacer algo bueno en internet, los desarrolladores pueden pasarse vidas enteras trabajando en que las web que crean se vean bien en IExplorer. Es cierto que este navegador es uno de los precursores de los inicios del Internet, pero tuvo su tiempo. La razón es que este navegador es tan antiguo, y con tantas deficiencias y limitaciones, que hacer que una web desarrollada para gente normal (que usan Firefox, Safari o IExplorer en al menos la versión 7) se vea bien corriendo sobre ella, sea una tarea de valientes.

Entonces cuando queremos hacer una web, siempre estamos probando en Firefox que es el mejor navegador para desarrolladores, y seguro que en nuestra PC tenemos al menos la versión 7 de IExplorer. La web nos queda perfecta, para darle un beso, se mueve, se ve bien, suena, y funciona correctamente. De pronto se nos ocurre (por caridad) que algún loco va querer entrar a la página con IExplorer 6 así que tenemos que probarla en ese navegador, como es sabido no podemos instalar más de una versión en nuestra PC, es decir, no podríamos tener IExplorer 6 e IExplorer 7 u 8 instalado en el mismo equipo. Esto es un problema y de alguna manera había que solucionarse. Así que algunos tienen la “gran idea” de instalar una SO Virtual XP en su PC con Windows Vista, gastando espacio y tiempo, todo eso para correr IExplorer 6…que estupides!!!

La solución a los problemas es muy sencilla, y nos la trae un software que adoro, el IETESTER, es una como un navegador que te permite abrir en distintas pestañas, una distinta versión de IEplorer, desde la versión 5!

No hice este post para enseñar a usar el software porque no es nada complicado, solo quise contarles que es muy bueno, que te permite ver como se ve tu página en cualquier versión de IExplorer, y también quise criticar el hecho de que algunas personas (voy a llamarles personas solo por esta vez) usen IEplorer 6, a eso le llamo dejades, poco amor propio  baja autoestima. Por favor, es en serio, no importa qué navegador quieres usar, sea cual sea, pero deja ya de usar IExplorer 6, hay que erradicarlo del mundo.

Espero que algunas personas hayan tomado conciencia de esto y que propaguen lo mismo con más fuerza, porque ya se anda haciendo, pero si no nos unimos todos, nunca podremos estirpar ese cancer del IExplorer 6 en la web.

Últimamente me estoy refiriendo a avances que mis compañeros de la Fundación CTIC y de la Oficina Española de W3C están realizando en cuestiones relacionadas con la Administración Electrónica. En particular, están comenzando a tener mucho trabajo, en relación a la Reutilización de la Información del Sector Público, y todo lo que está relacionado con la Ley 37/2007 de 16 de noviembre.

Recientemente han realizado esta presentación y creo que es muy clara para intentar encontrar respuestas a por qué a pesar de los esfuerzos que se están realizando por implementar la administración electrónica aún se usa de una manera tan escasa.

Madame ou Monsieur,

Je veux aller vers des principes : Créer un monde sans pauvreté pour permettre de financer et améliorer l’éducation, réduire les maladies, réduire la mortalité et améliorer l’espérance de vie humaine (vision sur le long terme)

L’internet compte aujourd’hui plus 1 milliard d’utilisateurs. Il y a une adoption massive des téléphones mobiles. Le prix de la technologie et sa taille diminuent tandis que sa performance et son adoption devient massive. (ex : la RAM & les microprocesseurs) Le coût de l’éducation diminue. (ex : Wikipedia & MIT OpenCourseWare) Le chiffre d’affaire du e-commerce augmente chaque année. L’espérance de vie est passé de 25 ans dans l’Égypte ancienne à plus de 80 ans en Europe en 2008. Selon le scientifique et futurologue Raymond Kurzweil, il existe une accélération des révolutions scientifiques. La prochaine étape vers la singularité technologique est probablement la GNR : la Génétique, la Nanotechnologie, et la Robotique (avec une Intelligence artificielle forte).

Je voudrai développer mes compétences dans le domaine de l’analyse qualitative (marketing), de la sécurité des applications web, dans la finance, et dans un domaine qui tend vers la GNR.

Je suis étudiant en Informatique spécialisé dans le Développement d’ Applications Web actuellement en Master 2 au SUPINFO International Institute of Information Technology de Paris (ex ESI), leader français en 2007 et qui a réussi à développer son modèle à l’international (Londres, Montréal, San Francisco). Mes principaux atouts : La créativité et l’innovation. Je suis efficace seul ou en équipe comme le prouve la réussite des projets qui m’ont été transmis. Je veille à respecter les standards du web (W3C), l’accessibilité du site sur plusieurs navigateurs, et à documenter mon travail.

Mon approche de développement se base sur le bestseller de Steven Covey (The 7 Habits of Highly Effective People) qui appliqué à l’informatique, de mon point de vue, consiste principalement à créer une relation de dépendance avec les API existantes. Par exemple, j’ai développé un système de Trading compatible PayPal (PayBook) pour mettre fin à la pauvreté. Les 4 piliers de mon développement sont : la sagesse, l’orientation, la puissance et la sécurité. Et, j’essaye de prendre en compte les sentiments de la personne avec qui j’ai une relation et aussi de maintenir une augmentation de ma capacité de production à environ 10% par jour.

Mon objectif sur le court terme consiste à trouver un stage conventionné commençant à partir du 02 novembre 2009 au rythme de 2 jours/semaine, ou ; à partir du 01 avril 2009 pour 6 mois à temps plein. La convention de stage peut être établi par l’entreprise ou par mon école. Ma stratégie du business repose sur un accord gagnant-gagnant : un stage me permet de valider mes crédits ECTS nécessaire pour obtenir mon Master of Computer Science (BAC+5) ; et permet à l’entreprise de réduire ses coûts et d’améliorer son profit.

En terme de distance, je préfère les postes situés à moins d’une heure de mon domicile (sur l’île de France). Je pense que nous pouvons gagner mutuellement dans cette relation. Je suis disponible pour un entretien d’embauche dans vos locaux, le plus tôt possible, à l’heure qui vous conviendra, un lundi ou un mardi de préférence.

Cordialement,

Yann Geffrotin
Développeur d’Applications Web (cv.geffrotin.com)
Étudiant en Master 2 (BAC+5) à SUPINFO Paris
Tel : (+33) 01 39 13 16 04 Por : 06 43 84 45 65

VXML or no standards ? I would lean towards standards but a simpler standard. For starters, VXML is the language used by voice solution providers to connect with a voice gateway provider just like IE, FireFox, Chrome are browsers for IIS, PHP, Apache web servers. Now VXML as the name stands is a XML standard with 3 versions ratified by W3C (the third version to be release next year) since its inception in 1999.  The main reason VXML gateways exists is to provide an easy way to switch from one provider to another without breaking solutions or re-writing voice solutions. Very much like changing utilities from one to another provider.

Now, I have worked with VXML gateways (Voxeo, VoiceGenie, NMSsolutions) and also worked with voice solution providers. Then I moved on to architect the HummingBytes VXML gateway, developed it and deployed it for voice solution providers to use. After being in all shoes I think I can confidently assert that standards are good, but making it easy will go a long way in making sure that the standard is enforced.

Now, coming to the part of switching from one gateway to another, the only ones who can make the switch are the voice solution providers. They can move freely from one gateway to another (albeit with some custom code modification so their core technology). End clients who are stuck with voice solution providers still cannot move from one provider to another. Reason being interfacing with the VXML gateway takes a lot more than writing a few lines of code. To communicate via VXML one has to build a sub-system which takes code written in a higher level language like C, PHP, C#, Java and translates it to VXML payloads. Building this subsystem is cost prohibitive. That is why you have smaller gateway players who come out with innovative XML language that completely throws out standards and makes it own wild west standard.

Now, here is another interesting fact the voice solution providers do. They use a sub set of the VXML language capabilities and push logical transitions, state transitions to higher level languages. So now you have a vast and rich language and only 10 percent of the language gets used. And now W3C is going to add SCXML (State Control XML) into the VXML 3.0 standard !!! So now you can do more with an XML language that no is going to use. What the W3C committee expects is developers to develop using XML, but no one codes in XML. XML is only used for the lowermost handshake between systems.

My recommendations :

1. Make the VXML language simple. Do not make it very complex and then have a compliance test to pass so that one can be certified VXML 3.0 complaint. Without a VXML compliance certification you are not considered a serious vendor. Only the big companies who have large development teams can create a compliant gateway and only they are in the business. The smaller ones create their own standard !!

2. Create components which generate simple VXML payloads which can then be easily distributed. If you want more people directly talking in VXML then simple components that you buy off the shelf is good.

TAGS PARA CONSTRUIR O LAYOUT NO HTML 5

Lembrando que nada é mágico e nem deve ser, tudo precisa e continua necessitando de estilização com CSS.

No próximo artigo, irei mostrar alguns exemplos e formas de utilizar essas novas tags.

Abraços!

No início de 2009, o W3C anunciou a primeira especificação do HTML5.

A versão atual do HTML é a 4.0.1, e a versão final do HTML está prometida para 2012.

Foram feitas grandes alterações que favorecem a semântica, que incluem:

• novas API’s
• Elemento <canvas> para desenhos dinâmicos;
• Network status (online/offline);
• Utilização de um plugin gratuito de áudio e vídeo via tags;
• contentEditable – Editor rico de conteúdo;
• Drag and Drop de elementos;
• Cross-document e cross-domain messages;
• Histórico de navegação em Ajax;
• Geolocation API;
• Maior controle de dados sobre formulários;
• Armazenamento de dados no cliente;
• Web worker threads;
• Melhoria na depuração de erros;
• Entre outros avanços.

Esta evolução da linguagem padrão para web pode eliminar a necessidade de plug-ins para aplicações multimídia em navegadores. Diversos críticos consideram a tecnologia como um forte concorrente ao Flash do Adobe, Silverlight, da Microsoft, e o recente JavaFX, da Sun.

Recentemente, Shantanu Narayen, diretor executivo do Adobe, disse que o Flash não irá perder mercado, porem a versão 5 do HTML já está sendo chamado de “Flash-killer”. Estas tecnologias precisarão se adaptar rapidamente para conseguir manter-se no mercado, tão popular quanto hoje.

Na avaliação do co-diretor de ferramentas da Mozilla, Ben Galbraith, as tecnologias viabilizadas pelo HTML 5 como o Canvas para desenhos 2D e o armazenamento de conteúdos no desktop, permitirão que “usemos mais o browser do que nunca”.

Após dez anos sem atualizações, a forma como se escreve páginas na Internet passa por uma boa transformação. O HTML 5 oferece uma experiência web totalmente diferente para usuários e embora exista um longo caminho para ser finalizado, os navegadores mais importantes, como o Opera, Google Chrome, Safari 4, o novo Firefox 3.5 e o Internet Explorer 8 já implementaram partes da linguagem, incluindo tags de vídeo e suporte à tecnologia Canvas.

Na versão 4 do HTML, a atual, o navegador não distingue o que é topo, conteúdo, rodapé e menu, mas com o HTML 5 isso irá mudar, veja:

Estrutura de código com o HTML 4:

<body>
  <div id="topo">...</div>
   <div id="menu">...</div>
   <div class="content">...</div>
   <div id="barralateral">...</div>
   <div id="rodape">...</div>
  </div>
</body>

Estrutura de código com o HTML 5:

<body>
  <header>...</header>
  <nav>...</nav>
  <section>
    <header>...</header>
    <article>...</article>
    <footer>...</footer>
  </section>
  <aside>...</aside>
  <footer>...</footer>
</body>

Ou seja, agora o navegador terá um conhecimento real de como o layout está sendo renderizado, o que é o rodapé, o conteúdo, a barra lateral da direita e etc. E claro, isto irá auxiliar muito os mecânismos de busca a filtrar informações úteis ou não. Talvez o que está em “header” não interesse muito, talvez o mais importante será o que está dentro de “article”, e por ai vai as possibilidades de mudanças que a nova tecnologia nos dará.

Repare pela imagem representando o layout que os elementos header e footer não são exclusivos da página, mas pode ser usado para representar o topo e o rodapé de qualquer conteúdo (ou article).

Bom, não vamos extender muito o tópico, resumi bem e de forma simples o que é o novo HTML.

Nos próximos artigos sobre o HTML 5 eu vou mostrar detalhadamente sobre as novas TAGs e atributos e quais são suas funcionalidades. Também irei mostrar um exemplo prático de como desenvolver o HTML 5.

Abraços!

OWL 2 Connects the Web of Knowledge with the Web of Data

Today W3C announces a new version of a standard for representing knowledge on the Web. OWL 2, part of W3C’s Semantic Web toolkit, allows people to capture their knowledge about a particular domain (say, energy or medicine) and then use tools to manage information, search through it, and learn more from it. Furthermore, as an open standard based on Web technology, it lowers the cost of merging knowledge from multiple domains.