To create static web pages - webforms/xsd needed?

[guhann]

Hi,

I need to manage the static contents(30 pages) of an existing website.
That means i need to create 30 webforms with 30 xsd files?

so that it will deliver 30 xml files and in jsp i need to grab the details for display?pls clarify..

Thanks,
Guhan N

[kvc]

We're looking into for our updated Community build, RC2, due end of this week.  Will keep you posted.

Kevin

[guhann]

Hi kevin,

Seems like this advance tools(table,viewsource) is not included in alfresco-community-tomcat-2.1.0 final version also.
(to be frank without that we can't work anything).


Its already not available in alfresco-community-tomcat-2.1.0R1 , i thought this will be fixed in final version, but its not.

[kvc]

Guhann:


We added support for greater TinyMCE configurability, including support for tables, in our 2.1 Enterprise BETA 2 (currently available for subscribing customers).

Additionally, since BETA 2, we've opened up support for any TinyMCE plug-in you should wish to use and enable you to selectively define different instances of TinyMCE using different plug-ins for different elements within a web form.  All are configured via web-cllient-config-wcm.xml.  This new support will be made available mid-week as 2.1 Enterprise BETA 3 and is currently available for checkout from the v2.1.0 branch.

Hope that helps.  These changes will also migrated their way into an updated Community release after ship of 2.1.0 Enterprise.


Kevin

[guhann]

After two months of time, still the updated community version(with additional support to text editor) is not released!!.

Text editor plays an important role in content management, but the editor which you have provided is not that much sophisticated/user friendly to use with, generally the width and height needs to be altered so that it can display long sentence, it should be available as a default one.

[jagruti]

Your web forms should be for distinct content types and page types. If you have a dynamic site, you may only have one content type (an article) and two page types (a home page and a section page). In this case, you'd have just tjhree output templates (either XSL or Freemarker) to generate you home, section, and details pages (the details pages generated from you distinct content items). The pages you generate would be JSP pages, so that your headers, footers, and navbars can be dynamically sourced or generated, and so that your home and section pages can dynamic generate links to your details pages.

You can also generate the entire site statically, and use standard SSIs for common headers, footers, and navbars. You can also have three additional forms and three additional templates associated with those forms so that end-users (and not developers) can change headers, footers, and navbars via Forms as they need. And although the site is static, since they are standard includes, they would immediately update all relevant pages.

Even the largest of sites typically don't have 30 web forms. Rule of thumb is if you are building more than 10 web forms for a site, think hard about how individual page variations can be captured in a single form that is more representative of a general model.
for this reply can u help more  how to do it step by step
Thanks
Jagruti