web
Using Google Analytics to track the user visit
Tracking the user visit of our website can be done in a nice, simple, and easy way using Google Analytics.
1. Go to http://www.google.com/analytics/
2. You need a Google account to enter. Create one (sign up) if you do not have any Google account yet.
3. Click "Add Website Profile" and provide the url of your website (and the other necessary information, such as: timezone).
4. Choose the appropriate option in "What are you tracking"
5. Copy and paste the code in the box into every page that you would like to track. Paste the code immediately before the closing </head> tag.
6. Click "Save and Finish"
Usually you have to wait for 24 hours to see the report. Once your report appear, you can also create a customize report using the link in the left hand side (after you clicked "View report"). Location, time, source, how long the user visit the page, etc can be observed easily using Google Analytics.
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.
Taggings:
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.
Taggings:
Don't surf the web. Command it.
<p>You’re writing an email to invite a friend to meet at a local restaurant in Vienna that neither of you has been to. You’d like to include a map. Today, this involves the disjointed tasks of message composition on a web-mail service, mapping the address on a map site, searching for reviews on the restaurant on a search engine, and finally copying all links into the message being composed. This familiar sequence is an awful lot of clicking, typing, searching, copying, and pasting in order to do a very simple task. And you haven’t even really sent a map or useful reviews—only links to them.</p> <p>This kind of clunky, time-consuming interaction is common on the Web. Mashups help in some cases but they are static, require Web development skills, and are largely <em>site-centric</em> rather than <em>user-centric</em>.</p> <p>It’s even worse on mobile devices, where limited capability and fidelity makes this onerous or nearly impossible.</p> <p>Most people do not have an easy way to manage the vast resources of the Web to simplify their task at hand. For the most part they are left trundling between web sites, performing common tasks resulting in frustration and wasted time.</p>
opera unite
if you use the opera browser (newest version), you could also use opera unite, which is a browser with added web server capabilities t through an extensible plug in model. opera unite allows for several services to be hosted from the user's computer, including a web server for sharing files.
http://unite.opera.com/
http://unite.opera.com/support/userguide/
http://unite.opera.com/application/132/
Taggings:
web-stream management for events.
<p><span style="line-height: 19px; white-space: pre-wrap;">Software for handling multiple digital video streams and integrating them into a website. A director should be able to select one out of different camera positions and post the video stream to a website together with some inserted text (either overlaid on the video or as a text on the webpage itself) </span></p>
Extend Typo3 with custom functionality
Typo3 is a powerful content management system with a rich framework for extensions. However for simple tasks it can be too much work to write a fully-fledged extention. The goal is to integrate small server-side programs into a typo3 managed website with less work.
Taggings:
Correctly configuring a Jetty Java Servlet container to be used through an Apache Web server via mod_jk
When deploying a JVM-based Web app usually so-called Java Servlet containers resp. application servers are used for the produciton system/environment. Probably the most popular and common Java server in this field is Apache Tomcat (and other even more feature-rich ones like JBoss or GlassFish). Apart from that, there's also Jetty which can be seen as a somewhat lightweight alternative. Nevertheless, there are some subtle differences to be taken into consideration when configuring it as opposed to Tomcat. The usual way to setup such a production system for a Java Web app is to use the Servlet container to serve the Web app and put so to speak in front of it an Apache Web server which handles the requests, hands them over to the container instance (e.g., Jetty or Tomcat) and receives its responses then (to say it in an a bit simplified way). Usually this is done via Apache's mod_jk module which enables communication between app server and Web server through the AJP13 protocol. What should be described and explained now is how to setup such a Java Web app production system ready for deployment in detail (mainly from a configuration perspective). The main focus shall be put at differences which are to be taken into account here between Jetty and Apache Tomcat.
Pages
- « first
- ‹ previous
- 1
- 2
- 3
- 4
