I have followed the plugin Development crash course till the "Page Routing" sub-heading in the  tutorial 

 and checked on live oxwall website, but the contact page is not visible, I don't know why

 please check below link-

http://dgkashi.com/oxwall/contactus/contact/index

I had found this fourm thread by searching on google and I have exactly same problem

please check it

I am new to oxwall.

Thanks 

Dhananjay

OW::getRouter()->addRoute(new OW_Route('contactus.index', 'contact', "CONTACTUS_CTRL_Contact", 'index'));

The name of the class and action (function) is way similar, so it's hard to make out what to put where.

So, I'm trying to understand what each of these things do. As I understand (and seen in other plugins) it is working like this:

OW::getRuoter(): Tells the systems Routher there is something going oun with the routing

->addRoute (new Ow Route): Here you go system, create a new route!

So what will the new route be? A bit tricky to understand. Where does the 'contactus.index' come from? 

As I get it it is a made-up name, just an internal name to keep track of the route within the system. You could actually use any name you want, as long as there is no other route with the same name, but the standard is that you give it the name of the plugin and then add the view or action name. But if you want to you could name it whatever you want. (is this a correct assumption by me?)

Then there is a the 'contact' part. What do we put in there?

Okay, here I'm guessing that you mean the shortened url, eg. http://yourdomain/{url} that is supposed to be defined. 

CONTACTUS_CTRL_Contact: is the controller, or class that is going to be used. The class should be within the ./pluginname/controllers/ folder and have te same name as the class within it.

index: is the defined action, in this case the function within the controller (class).

This is how I understand the line, but I'm quite shure I've missunderstood it, because I can't get it to work:P

Yes, there are the doc pages, but I can't seem to find a signup page, and the email i sent to the person taking care of the docs hasen't responded.

There are quite a few questions I see here in the forum that probably could be solved once and for all with a open wiki or such.

Comming from a background making my own scrips, with no rules in how my code should look, behave as standard, intentions with it etc. I find it hard to manoeuvre a whole community-scritp without clear, simple and understandeble explenations. 

I am pretty much in the same spot and I do not see much support from Oxwall team either. 

instead I see a lot of "we do not do this, so hire a dev" 

ok, I understand you do not write custom code, but please provide the necessary information about how the system is designed and works so we the community can take it farther with small steps.

oxwall if you want a community then please help it out.

otherwise just spell it out clear you do not want a community to grow so people coming here will know what oxwall is all about from the beginning. 

Quote from Joey The long term success of an open source software depends on the number of contributors it can get.If we have learnt anything from the wordpress community it is the fact that clear documentation and tutorials enable more developers to participate. Oxwall needs more tutorials in plugin development, this would take a lot of pressure from the core developers. A WIKI is a great idea and also some youtube tutorials would be great too.

https://developers.oxwall.com/forum/topic/48472

you should watch both, but i think what you will find is in part 2