Multi-Profile Architecture
Many developers want different README designs for different contexts:- A rich, comprehensive dashboard for their primary personal GitHub profile (
default). - A sleek, minimal monochrome widget for technical project READMEs (
minimal). - A specialized metrics-only card for client proposals or portfolio embeds (
stats).
1. Embed URL Structure & Slug Routing
Each profile is identified by a URL slug (e.g.default, minimal, dark-mode, compact).
URL Formats:
2. Segregated Telemetry & Redis Keys
Every view, unique visitor, error event, and dimension metric is scoped by bothusername and slug:
Global vs. Scoped Analytics
In the GitAscii Pro dashboard (/pro/analytics):
- “All Profiles” Scope: Combines metrics across all your profiles to give an aggregated overview of your developer reach.
- Specific Profile Scope: Filters charts, heatmaps, and error logs exclusively for the selected profile slug.
3. Managing Profiles in the Dashboard
In/pro/profiles, you can:
- Create New Profile: Assign a custom slug, friendly name, and description.
- Copy Embed Markdown: Instantly copy formatted
markdown snippets with one click. - Set Default Profile: Choose which configuration is returned when someone accesses the root endpoint
/api/username. - Dynamic Rules & Scheduling: Configure automated rule switching (time-of-day, day-of-week, event dates) with the visual Rule Simulator.
- Version History & Rollback: Browse automated revision snapshots, view widget counts and timestamps, and rollback with one click.
- Duplicate Profiles: Clone an existing profile structure to iterate safely on new design experiments.
- Safe Deletion: Delete obsolete profiles (retaining data safety safeguards for active default profiles).