nim_websitecreator

nim_websitecreator copied to clipboard

At the moment NimWC is full featured website package. We defined the main routes (/frontpage, /blog) and html pages (login, etc.), but we allow for plugins, where the user can add additional features. If the user only wants to use NimWC backend and customize everything else, we are currently blocking it. So, it's a kind of a framework (many definitions..).

Scenario

A user does not want to do the programming of user administration, managing files, server monitoring, routes to check loginforms etc. But they want full control of all routes and the HTML for the end user. This is not possible at the moment.

Idea

A compile-flag is introduced: framework

This flag will:

• Remove all default routes
• Remove all include of end-user nimf-files
• Add all routes in /framework/routes
• Include all nimf in /framework/nimf
• Give access to framework proc's - such as proc checkLoginDetails(xxx)

But this is kinda similar to not running any --insertdata command, so is not too far. :slightly_smiling_face:

But this is kinda similar to not running any --insertdata command, so is not too far.

You'r right! But even then we still ship NimWC with standard routes - so the user will have our base URL's such as /blogs, /login, etc. It was to avoid these.

EDIT: Ahh, misread your post. Yeah - we are not far from the goal :)