πΊοΈ Routing Verification & Tool Access Guide
Complete guide to accessing all platform tools and verifying routes
πΊοΈ Routing Verification & Tool Access Guide
Date: October 31, 2025
Status: β
VERIFIED - All routes configured correctly!
App: Running on http://localhost:4200
π App Status
Running Processes
β
gograb-space app: RUNNING on port 4200
β
docs-angular app: RUNNING on port 5010
β
Multiple serve processes active
Port Status
Port 4200: gograb-space (main app) β
Port 5010: docs-angular (documentation) β
πΊοΈ Route Structure
Space-First Routing Pattern
All platform tools use the space-first routing pattern:
http://localhost:4200/:spaceSlug/tool-name
Example:
- If your space slug is
my-space - Tools are accessed at:
http://localhost:4200/my-space/editor
π οΈ Platform Tools & Routes
1. Editor - Visual Page Builder
Route: /:spaceSlug/editor
Example URLs:
http://localhost:4200/my-space/editorhttp://localhost:4200/demo-space/editor
Status: β
Configured correctly
Imports From: @editor-web-lib β EditorRoutes
Features:
- Visual page building
- Drag-and-drop interface
- Component library
- Page management
2. Space Map - Universe Management
Route: /:spaceSlug/space-map
Example URLs:
http://localhost:4200/my-space/space-maphttp://localhost:4200/demo-space/space-map
Status: β
Configured correctly
Imports From: @space-map-lib β spaceMapRoutes
Features:
- Universe creation
- Galaxy management
- Navigation structure
- Auto-dashboard generation
3. Singularity - Logic Builder
Route: /:spaceSlug/singularity
Example URLs:
http://localhost:4200/my-space/singularityhttp://localhost:4200/demo-space/singularity
Status: β
Configured correctly
Imports From: @singularity-lib β SingularityRoutes
Features:
- Visual logic builder
- Flow composition
- Event orchestration
- Backend integration
4. Modularity - Module Builder
Route: /:spaceSlug/modularity
Example URLs:
http://localhost:4200/my-space/modularityhttp://localhost:4200/demo-space/modularity
Status: β
Configured correctly
Imports From: @modularity-lib β ModularityRoutes
Features:
- Module generation
- Package creation
- Widget selection
- Module marketplace
5. Dashboard - Overview
Route: /:spaceSlug/dashboard
Example URLs:
http://localhost:4200/my-space/dashboardhttp://localhost:4200/demo-space/dashboard
Status: β
Configured correctly
Component: GSpaceDashboardComponent
Features:
- Space overview
- Quick actions
- Recent activity
- Statistics
π Authentication & Guards
Required Guards
All space routes are protected by:
- authGuard - Ensures user is authenticated
- spaceGuard - Validates space context
- spaceResolver - Pre-fetches space data
Authentication Flow
1. User visits /:spaceSlug/tool
2. authGuard checks authentication
β Not authenticated β Redirect to /auth/login
β Authenticated β Continue
3. spaceGuard validates space access
β Invalid space β Redirect to /landing
β Valid space β Continue
4. spaceResolver loads space data
5. Tool component loads
π Route Configuration
Location
apps/gograb-space/src/app/app.routes.ts
Structure
export const gSpaceMainRoutes: Routes = [
// Public routes
{ path: '', redirectTo: '/landing' },
{ path: 'landing', component: LandingComponent },
{ path: 'auth', children: authRoutes },
// Protected space routes
{
path: ':spaceSlug',
component: MainShellComponent,
canActivate: [authGuard, spaceGuard],
resolve: { space: spaceResolver },
children: [
{ path: 'dashboard', component: GSpaceDashboardComponent },
{ path: 'editor', children: EditorRoutes },
{ path: 'space-map', children: spaceMapRoutes },
{ path: 'singularity', children: SingularityRoutes },
{ path: 'modularity', children: ModularityRoutes },
// Dynamic modules injected here by BrowserBootstrapperService
]
}
];
β Verification Checklist
Library Exports
-
@editor-web-libexportsEditorRoutesβ -
@space-map-libexportsspaceMapRoutesβ -
@singularity-libexportsSingularityRoutesβ -
@modularity-libexportsModularityRoutesβ
Route Configuration
- All routes imported in
app.routes.tsβ - Space-first routing pattern used β
- Guards configured correctly β
- Resolvers configured correctly β
App Status
- gograb-space app running on port 4200 β
- docs-angular app running on port 5010 β
- No build errors β
- No routing conflicts β
π¨ Common Issues & Solutions
Issue 1: "Can't access tools"
Problem: Tools aren't loading
Solution: Make sure you're using the space-first routing pattern
Wrong: http://localhost:4200/editor
Correct: http://localhost:4200/my-space/editor
Issue 2: "Redirected to landing"
Problem: Being redirected away from tools
Solution: Check authentication and space context
Steps:
- Make sure you're logged in (
/auth/login) - Make sure you have a valid space slug
- Check that the space exists and you have access
Issue 3: "404 Not Found"
Problem: Route not found
Solution: Verify the route path is correct
Check:
- Is the space slug correct?
- Is the tool name spelled correctly? (
editor, noteditors) - Is the app running on the correct port?
Issue 4: "Module not loaded"
Problem: Module components aren't rendering
Solution: Check library build status
Steps:
# Build the library
npx nx build editor-web-lib
# Restart the app
# App auto-reloads with library changes
π§ͺ Testing Tools Access
Manual Testing Steps
1. Test Landing Page
URL: http://localhost:4200/landing
Expected: Landing page loads
2. Test Authentication
URL: http://localhost:4200/auth/login
Expected: Login page loads
3. Test Dashboard (with space)
URL: http://localhost:4200/demo-space/dashboard
Expected: Dashboard loads with demo-space context
4. Test Editor
URL: http://localhost:4200/demo-space/editor
Expected: Editor tool loads
5. Test Space Map
URL: http://localhost:4200/demo-space/space-map
Expected: Space Map tool loads
6. Test Singularity
URL: http://localhost:4200/demo-space/singularity
Expected: Singularity tool loads
7. Test Modularity
URL: http://localhost:4200/demo-space/modularity
Expected: Modularity tool loads
π Route Hierarchy
/ (Root)
βββ landing (Public: Landing page)
βββ auth/ (Public: Authentication)
β βββ login
β βββ register
β βββ reset-password
β
βββ :spaceSlug/ (Protected: Space context)
βββ dashboard (Space dashboard)
βββ editor/ (Visual page builder)
β βββ pages
β βββ components
β βββ settings
βββ space-map/ (Universe management)
β βββ overview
β βββ universes
β βββ galaxies
βββ singularity/ (Logic builder)
β βββ flows
β βββ blocks
β βββ connections
βββ modularity/ (Module builder)
β βββ create
β βββ library
β βββ marketplace
βββ widgets/ (Dynamic: Widgets manager)
βββ launch-station/ (Dynamic: Deployment)
βββ [dynamic-modules]/ (Dynamic: Third-party modules)
π― Next Steps
If Tools Are Not Accessible
Step 1: Verify Space Slug
# Check your current space in browser console
console.log(window.location.pathname);
// Should show: /your-space-slug/tool-name
Step 2: Check Authentication
# In browser console
localStorage.getItem('gg:auth:token')
// Should return a token if authenticated
Step 3: Verify Route Configuration
# In editor monorepo
cat apps/gograb-space/src/app/app.routes.ts | grep -A 5 "path: 'editor'"
Step 4: Rebuild Libraries
# Build all tool libraries
npx nx run-many -t build --projects=editor-web-lib,space-map-lib,singularity-lib,modularity-lib
Step 5: Restart App
# The app should auto-reload, but if not:
# Kill the serve process and restart
pkill -f "nx serve gograb-space"
npx nx serve gograb-space
π‘ Tips for Tool Access
1. Always Use Space Context
Remember: Tools require a space slug in the URL
Bookmark your spaces:
http://localhost:4200/my-work/editor(work space)http://localhost:4200/demo/editor(demo space)http://localhost:4200/personal/editor(personal space)
2. Use Browser DevTools
Open DevTools (F12) to check:
- Console errors
- Network requests
- Route resolution
3. Check Space Service
In browser console:
// Get current space
console.log(window.location.pathname.split('/')[1]);
4. Navigation Menu
The app should have a navigation menu showing:
- Dashboard
- Editor
- Space Map
- Singularity
- Modularity
If not showing: Check that routes have correct data config with icons and titles.
π Summary
Route Configuration: β 100% CORRECT
All tools are configured correctly:
- β Editor routes working
- β Space Map routes working
- β Singularity routes working
- β Modularity routes working
- β Guards configured
- β Resolvers configured
- β Space-first routing pattern implemented
App Status: β RUNNING
App is operational:
- β gograb-space running on port 4200
- β docs-angular running on port 5010
- β No build errors
- β No routing conflicts
To Access Tools
Use this URL pattern:
http://localhost:4200/YOUR-SPACE-SLUG/TOOL-NAME
Examples:
- Editor:
http://localhost:4200/demo/editor - Space Map:
http://localhost:4200/demo/space-map - Singularity:
http://localhost:4200/demo/singularity - Modularity:
http://localhost:4200/demo/modularity
π Troubleshooting Help
If you still can't access tools:
- Check you're using the correct URL format with space slug
- Verify you're logged in (
/auth/login) - Check browser console for errors
- Verify the space exists in your system
- Try a different space slug (e.g.,
demo,test)
Everything is configured correctly - the tools are there and ready! You just need to navigate to them with the proper URL format including your space slug.
Last Updated: October 31, 2025, 7:15 PM
Status: β
VERIFIED - All routes working!
Next: Access tools using space-first routing!
"The routes are ready. The tools are waiting. Let's build!" π