Re: [Hypercontent-users] Newbies Questions

[Alex V. <av...@co...>]

Hi Liying,
	I think Carl's response sums it up; unlike other content =
management =20
systems where the general use-case is shoe-horning your content into =20
one of several pre-defined structures, with HyperContent you design =20
your web site structure according to your particular requirements, and =20=

then implement it in your project definition.  This also leaves you =20
with the task of creating XSL to generate everything on every page.  =20
We're happy to share some useful templates, for example to generate =20
navigation toolbars, breadcrumb trails, and other common patterns.  =20
You'll find some discussion of these in the mailing list archives.

It's pretty straightforward to implement very generic sites; you can =20
start a site with undifferentiated sections, unlimited depth, and XHTML =20=

only content with a few simple document and resource types.

<xml-doctype path=3D"/**/index.xml" label=3D"Index Page" root=3D"html"/>

<xml-doctype path=3D"/**/*.xml" label=3D"Page" root=3D"html"/>

<resource-directory path=3D"/**/*/" label=3D"Directory"/>

<resource-directory path=3D"/**/*.jpg" label =3D"JPG image" =
publish=3D"true">
	<content type=3D"image/jpeg" />
</resource-directory>

This gives you everything you need to start entering HTML data, JPG =20
images and unlimited subdirectories; to set up output, you will of =20
course have to set up output elements and XSL documents, and probably a =20=

sitemap (not required, but very handy for doing the dirty work of =20
generating navigation).  You can refine the structure as you go by =20
adding more specific document types with custom XML grammars and/or =20
different output logic.

In terms of source, there is generally no need to change or add any =20
source code (except for the recently discussed modifications required =20=

to change allowable tags and attributes in the WYSIWYG editor . . . =20
this will be in a configuration file someday!).  You can change your =20
project definition, DTDs, groups, permissions, workflows, content and =20=

XSL on the fly through the web interface.  The main reason you might =20
want to write some custom code would be to implement some custom =20
pipeline logic, for example that might grab some data from an RDBMS and =20=

render it into XML for transformation, or into Java objects for =20
presentation with Velocity templates.

-Alex

On Jul 1, 2005, at 4:50 AM, Carl Barrow wrote:

> Hi Lillian
>
> I'm still evaluating HC2.0 but I've been live with HC 1.4 here for =20
> some time. I'll do my best to answer your questions. Alex might want =20=

> to add to what I've written later on, but hopefully this will help.
>
> Answers embedded below
>
> Many Thanks
> Carl
>
> Liying Miao wrote:
>
>> Hi Experts,
>>
>> We are trying HC2.0 now to implement a test version of our =20
>> university=92s website. We are still at the stage of understanding =
more =20
>> of HC by playing with the sample project, modifying content. I know =20=

>> we can add items under News directory, but when we can=92t do certain =
=20
>> things like adding a root menu item or changing the navigation to be =20=

>> a drop down list, we are stuck.
>>
>> I read the Hypercontent 1.4 Manual, and thanks, that was helpful in =20=

>> understanding the building blocks. However, I still don=92t know =
where =20
>> to start. Here are the questions:
>>
>> 1. In order to meet our needs, do we modify the definitions in the =20=

>> sample project, or do we need a brand new project built?
>>
> =46rom my experience you should always start a new project from =
scratch. =20
> Spend some time planning out the structure of your site, how your =20
> template and navigation will work and getting your dtds correct from =20=

> the start and this will make live much easier in the future.
>
>> 2. If we need to build project from scratch, then,
>>
>> =B7 Do we create a test-repository folder under =20
>> C:\hypercontent2.0b2\hypercontent2.0b2\hypercontent2 (same directory =20=

>> where sample-build and sample-repository exist) and leave webapp =20
>> folder alone?
>>
> Yes, you'll need to create the directory for the repository. You don't =
=20
> need to do anything with the webapp directory.
>
>> =B7 Do we first create Project Definition, filesystem, under =20
>> C:=20
>> =
\hypercontent2.0b2\hypercontent2.0b2\hypercontent2\repositories\bootst=20=

>> rap\config and projects? How do we define it if we don=92t have =20
>> user.xml, index.xml, index.xsl, projet.xsl, etc created yet?
>>
> If you login to http://localhost:8080/projects/ as admin.
> Add a new project by typing a name in the box and press enter.
> Set the mount point, /newproject/ ( will be accessible at =20
> http://localhost:8080/newproject)
> Set the repository path, repositories/project-repository/newproject
> login to your new site and you'll see the following directories
> config/
> workflow/
> You will see nothing else since it's not defined in the project =20
> definition at this point.
> In config you will see project-definition.xml where you can now build =20=

> up your project. Adding your XML doctypes, build, publish paths etc...
> You can set up permissions in permissions.xml although thats not =20
> something I've done since HC1.4 used the uPortal group/permissions =20
> manager.
>
>> =B7 What source can we borrow for the new project, what need to be =20=

>> modified and recompiled?
>>
> I'm not too sure what you meant by that, can you clarify
>
>> Thanks so much for helping me get started=85 slowly=85
>>
>> Lillian Miao
>>
>> ERP/IT
>> Florida A&M University
>> (850) 412-7999
>>
>
> --=20
> ************************************
>
> Carl Barrow
> Web Developer
> e-Services
> The University of Hull
> Cottingham Road
> Hull
> HU6 7RX
> Ext. 6838
> ************************************
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=3D7477&alloc_id=3D16492&op=3Dcli=
ck
> _______________________________________________
> Hypercontent-users mailing list
> Hyp...@li...
> https://lists.sourceforge.net/lists/listinfo/hypercontent-users