
Hey @Clement, thanks for the input. :-) The problem I have is this : I as a site developer can use the tools and code to create the pages and layouts etc thus creating the pages and links is not a problem at all. I simply add the page IDs to an XMl file as elements which can be read from and displayed as normal links. In some cases I can use GUID too. The problem comes in when an end user has to create a page and because they cannot publish this page on the site unless they had the site creation tools, permissions. The classic example is a Wiki. The end user does not require any special tools or coding to achieve this. They just have a WYSIWYG portion where they type in whatever they want to do, click on SAVE and the page is automatically published within the site. I hope you have the overall picture now of what am trying to do. :-) As recommended by @Rad, I've had a look at some asp dot net CMS wiki deployments and am checking under the hood further to understand the publishing part. Am also trying to find out what makes up a WYSIWYG editor, because I'd hate to depend on external code for this. And a special thanks to @Rad for sending me down the road of looking under the hood to see how others implemented such a system. Wish some programmer in KE had also done a Wiki CMS from scratch and could share how they got it to work, then there was no need to use google. Rgds. On Tue, Jan 17, 2012 at 3:51 PM, Clement Ongera <cnongera@gmail.com> wrote:
@Aki My solution would be to create a table where there's an auto incremental field ~ ID(or something). when a new page is created, that ID(in my case) will be a page and this ID will be associated with whatever is added to the Page(s). to take your example www.nokplcpowerexample.whatever = ID_1 www.nokplcpowerexamaple.whatever/centralarea = ID_1_1 www.npkplcpowerexample.whatever/coastalarea = ID_1_2
www.nokplcpowerexample.whatevers = ID_2 www.nokplcpowerexamaple.whatevers/centralareas = ID_2_1 ...
I believe this can be done using ASP.NET/SQL
-- Many Thanks.
Regards, http://about.me/cnongera Clement Ongera.