ASP Template/Plugin portal project... http://www.asptree.com

Here is the imaginary end goal/ideas of the site....

- Standard core fileset that will allow ASP developers to create any plugin they wish (plugin being defined as *any* piece of functionality, from pure content display / CMS, to calendars, to security, to DB access, to shopping carts, to menu's, etc. etc. etc.), and web designers to create templates that can simply be downloaded, and thrown into a folder structure to use.

- Completely open source, and free to download / customize the core asptree files.

- Thousands of templates and plugins available for download on multiple sites (one may be yours eventually), of which were built by any/all ASP devs who have the time to build them within the asptree set of standards (not yet available, but getting close)

- End users being able to simply choose templates and plugins, download them, move into a folder, and simply add content to create a complete professional and functioning website... with only basic configuration required.


Remember, the above statements are just the fictional "hopes", in reality we are maybe 50% done with the core structure. Now for anyone that can imagine that end goal, here is the link to the site currently in progress...

http://www.asptree.com

I am looking for any feedback (especially dev) at all about about the idea or about the site, so that I can make sure this stays on the right path. Thanks a bunch!

Also, if you would like to be put on an email list for the latest info, please post or PM me.

__________________________________________________ _______
http://www.asptree.com developer

After a short look I must say that this look's good, I'm programming in ASP myself and must admit that I haven't thought of solving things like you have done.

But (there is always a but), I'm also concerned about webstandard's and SEO.

You are missing DOCTYPE and uses non-valid code:
http://www.alistapart.com/articles/doctype/

Your solution isn't very search engine friendly:

1. Your url's will most probably give you problem with the search engines
2. Link to the javascript instead of have it inside the page
3. Use H-tag's for heading's
4. The title-tag doesn't change, important for SEO

I guess this could make thing's more complicated, but it will also create more possibilities: Tables are for tabular data, not for design and creates uneccessary HTML-code. Take a look at CSSZengarden to see the power in CSS-design. Using CSS you can create several menus with the same template, and you don't need javascript for rollovers. Take a look here:
http://css.maxdesign.com.au/index.htm

My five cent.

EDIT: I saw that you also are using HTMLArea 2.03, if you need more functions I have a version here:
http://www.savio.no/htmlarea/example.asp
There are some messy code used, but there are functions there who I haven't seen anywhere else. But if you don't need so many functions, I would take a look at HTMLArea 3.0, creates better code, almost perfect XHTML, and also work's in Mozilla. Unfortunately there isn't so many add-ons yet.

Very valid points, and thanks for bringing them up. You are right that I have not yet taken many of these into careful consideration *yet*, but the project is early on in development. As for the DOCTYPE and non valid codes... those are actually defined within each template, so since this project really just parses and displays the template, it is up to the creator of thus mentioned template to keep their tags in check As for the templates up there right now, they have just been thrown up really quick to get something up there to test/work with, and will definitely be revisited and optimized before release.


Your not the first person to bring up CSS as a way to accomplish most of the menu or site structure. The beauty of ASPTree, is that again, that will be completely up to whomever creates the site template, or menu plug-ins as to how they function/work. Think of ASPTree as just a core engine, that processes templates, and fits custom plugins into pre-defined locations by the template. With that being said, each plugin or template can be designed however the author sees fit, and besides some basic standards to actually make them worth with ASPTree, the author is free to use whatever techniques they so choose. Some people really like Javascript, some really like CSS, some just like plain tables and graphics... its not going to be us to make them use one or the other, it'll be built to handle any.


Thanks, I will check into this as well when I get to that point in the project

Until then, I appreciate the response and feedback and has definitely pointed out a few things I need to get around to correcting before we make a release.

Actually - having a correct doctype should be the FIRST thing you do, when you start writing the code. Without it, you'll end up with the various browsers interpreting your code differently. Because they won't know what DTD is being used, they'll guess, and this can have disastrous results - try it with IE5.x

Disaster is my middle name!

I've got somebody working on a solution for this right now, whether or not we set a single standard for the whole site, or leave the standard up to template authors hasen't been decided just yet... its not an easy decision since people are welcome to create any type of site they want, with any type of method etc.