website

Tracking the source of visit of our website

As a company or the owner of a website, it is necessary to understand the characteristics of our visitors. The information could be useful to enhance the website itself, or even to create a targeted advertisement. These information including the location and the source of the user visit. In the other hand, the statistics of each page in our website are also important. For example: how often user visit the particular page, which page is the most visited page, where the user usually navigate from one page to another. Then the question remain: how can we gain these information in a nice, simple and easy way?

Easy maintainable static website

A static website shall be built, where all pages use the same layout. The layout may divide a page into several regions, like: footer, header, a menu, and maybe a region for displaying news. There may be other parts which all of the pages have in common (e.g. included resources like css, ...) The goal is that information shared by all pages shall not be duplicated, as this would complicate the maintainance of the website.

Adding generated pages to a website which uses relative paths and a layout template

There is website for a conference using relative paths to reference resources. The content of existing pages are maintained as XML files (containing HTML formatted text) There is one main template that defines the basic layout: header, footer, and a menu. Links defined here use relative paths. This template, an XSL file, is applied to all content pages to transform them into HTML-files. Until now all pages of the website have been located in the same folder. The challenge: A foto gallery shall be integrated into the website. It was generated with an arbitrary tool (e.g. Adobe Lightroom) that organises images and referencing pages in a folder hierarchy of multiple levels. An example: A foto gallery with an album overview, and two alums: Reception and Dinner - Album Overview | . index.html :with a link to each album, thumbnail L Reception | . index.html (with thumbnails of all fotos, linked to detailed view) | L detailed | | . IMG_001.html | | . IMG_012.html | | . IMG_... | L fotos | | . IMG_001.jpg | | . IMG_012.jpg | | . IMG_... L Dinner | . index.html (with thumbnails of all fotos, linked to detailed view) | L detailed | | . IMG_011.html | | . IMG_015.html | | . IMG_... | L fotos | | . IMG_011.jpg | | . IMG_015.jpg | | . IMG_... <ul> Problems: <li>These pages should follow the general layout</li> <li>These pages depend on the generated folder structure, so they can't be moved</li> <li>When the layout template is applied to the files of the gallery, the links (menu!) defined in there are <em>broken</em> (as they are relative references)</li> </ul> Find a way to integrate these pages, so they use the same layout template, and links with relative paths are still working.

Use wikimapia.org for embedding google maps

With wikimapia.org it is possible to embed google maps on your webpage without the need for an api key. You just need to view the region you like to show on your webpage, select 'Login' at the top navigation bar and click on 'Map on your page'. Now a popup shows a one line HTML code to copy/paste to your page. You have finished!

Embed Google Maps to Website

<p>Embed Google Maps to a Website. Show website visitor where Vienna UT is.</p>

Displaying Websites on IE Browsers correctly

As most non-flash sites use xhtml and css only, webdesigner (or those who realize such tricky designs) must face with issues that in the end this website has to be displayed correctly — some kind of platform/browser independency. Indeed, (X)HTML is standardized by the W3C, but web-browser render websites totally differently — caused by bugs mostly (IE). This becomes quite cruical, as for ex. designs require precisely fitting their components.

Providing contact to website users

How to provide the possiblity to contact a certain entity is difficult for many companies and organizations. Especially for small NGOs, it is not possible to have a big mailing infrastructure and to maintain server-side spam filtering. Therefore, email addresses should not be published as plaintext. Nevertheless, the website of the NGO should somehow offer the possibility to contact the NGO. It is important that the technology used is widespread and cheap, since NGOs do not have a large amount of money to spend on specialized technology. If possible, open source software should be used. As the existing infrastructure (apache server, msql server) is offered for free, it should be used to solve this problem. The only important thing is that spamming should not be possible and the tool should guarantee that a human being is trying to make contact, not an (evil) software program.

Checking websites for updates

Lots of websites get updated on an irregular basis. Some may get updated every week, others get updated every hour; some may not get updated for month and users are bored looking up the website regulary and they do not find any new content. In addition, checking websites manually is not very efficient and costs a lot of time. The solution for this problem should provide an easy way to check websites and stay updated. It would be helpful if the tool is able to highlight changes. In addition, the tool should be able to exclude several areas of a website from checking, for example the current time or the "who's online" section of the website. These changes might not be interesting for the user. The tool should of course work on HTML files; it also would be good if changes in images can be detected using a tool. The Solution should also cover non-HTML content, especially flash. Flash is used a lot in the www and this technology should not be left out. However, a solution for HTML at least would work for most websites. CSS changes do not need to be included as CSS should not contain any content but just formatting information.

Pages

Subscribe to website