That's the big conclusion!

These pages are still based on the frontpage design that needs somehow to be fixed or updated.

While people can still watch the pages, the navigation is no longer coherent right now.

That's what needs to be either dropped (not worry about it as it only slightly affects the quality of the visitor's experience) or be put back on track.

Labels: website impact

Conclusion????

That's not much!

This part represents probably 500 pages of content

This means that this part of the site could

• Be transfered to the new channels created
• Republished in blog format
• Not do anything! - Simply not worry about it as it gets very little traffic
• Republished with anew system or site structure (ASP or Dynamic site template)
• Other?

Labels: website impact

These are the estimations for the last month

• Home 4% (3000 pages/month?)
• HTM 77% (37000 ?)
• HTML (blogs) 7% (3000 ?)
• PHP (forum) 12% (5500 ?)

• Total pages 100% (48000 pages views/month)

----------------------------------------------

• MP3 Estimation (45000 downloads/month)

----------------------------------------------

Other traffic

• youtube 2000 views/day (60000/month)
• other video channels 2500 views/day (75000/month)

----------------------------------------------

Total page views + downloads - 228000/month

• site pages 21%
• Mp3 20%
• youtube 26%
• other video channels 32%

----------------------------

On this picture, the low traffic HTM pages (realtionships, life skills, etc) = 1% of overall traffic!

Labels: website impact

To attach pages to a Dynamic Web Template
In the Folder List task pane, select the file(s) that you want to attach to the Dynamic Web Template. To select multiple files, press CTRL and hold, and then click the files that you want to attach.
On the Format menu, point to Dynamic Web Template, and then click Attach Dynamic Web Template.
Locate and click the Dynamic Web Template you want to attach, and then click Open. If the body of a selected web page contains content, the Choose Editable Regions for Content dialog box appears. The dialog box displays the default settings for mapping content from the body of the web page to editable regions specified by the Dynamic Web Template. The Old column lists content in the body of the web page. The New column lists editable regions specified by the template.
In the Choose Editable Regions for Content dialog box, do one of the following:
To move all of the content in the body of the web page to the default editable region, click OK. If the default editable region contains content, that content is replaced with the content in the web page.
To move all of the content in the body of the web page to a specific editable region, click (Body), and then click Modify. In the New Region list, click the editable region you want to move the content to. If you click (none), the content is removed from the web page.
To maintain all of the content and structure of the web page, click Skip Current Page. The template is not attached to the page.

Labels: website impact

A Dynamic Web Template is an HTML-based master copy of a web page that you can create to contain settings, formatting, and page elements such as text, graphics, page layout, styles, and regions of a web page that can be modified.

You attach a Dynamic Web Template to the pages in a website, and that template defines the layout for those pages.

You can use any number of Dynamic Web Templates in a website, and you can attach a Dynamic Web Template to as many pages as you like.


----------------------

By using Dynamic Web Templates, you can create HTML pages that share the same layout. In addition to providing a shared layout, you can make some regions in a template available for editing while preventing changes to other regions in that template.

This means that you can allow others to add and edit content, yet still preserve the layout of the pages and the template itself.

Labels: website impact

That's good potential news

How easy is it to set it up, with database, etc.

Labels: website impact

Of course, the present site is still HTM.

What is the future and what is easiets to create on the long term?

What gives the site the most energy and dynamism?

What do I need to go for on the long term? ASP or HTM?

Labels: website impact

If yes, that would allow me to progressively shift some part of the content to ASP.NET pages.

That's an option

Labels: website impact

• cascading style sheet
• Dynamic web template
• ASP.NET master pages

At this stage, I tested the ASP.NET master pages adn it seems to work.

That sounds like an easy to use solution.

I was not able to publish it properly yet. The content was published but the matser page are does not.

Don't know why, yet

Labels: website impact

That's now the first step to make the site future friendly.

The only element that needs somewho to be "converted" to function properly is the

"page include"feature which is extensively used on the site

For the rest, everything gets published via FTP and it works

Labels: website impact