• http://grok-server/your-flint-app/ is the management UI
• http://grok-server/your-flint-app/public is the root of the public site

This makes it easy to configure a rewrite rule in a front-end web server to hide the managamente UI from outsiders ( a rewrite rule would be needed anyway to omit the your-flint-app part).

Inside the management UI, we would have:

• http://grok-server/your-flint-app/content: the UI where content is created, edited etc.
• http://grok-server/your-flint-app/categories: where tags are managed
• http://grok-server/your-flint-app/navigation: where the site map is built by configuring sections and pages
• http://grok-server/your-flint-app/users: user and permissions management

Possibly some users would not have access to all of those management features. For exemple, a news contributor could be allowed to see only the content/ area, while a news editor could see content/, categories/ and navigation/ but not users/.