You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add a linked quick reference for setup ordering and file paths #53
Split from #14's still-current documentation discoverability suggestions.
Reader task
A new consumer author should be able to find the required CMake version, dependency/setup ordering, public entry points, and file-resolution conventions without scanning the entire README.
Dependency tracking is already explained in examples and prose (README.md:118-122, README.md:274-286); the file conventions appear later (README.md:601-608). Improve navigation rather than treating those explanations as absent.
Scope and acceptance
Add a compact, linked quick reference for the required CMake version and principal public functions.
Give cpp_library_enable_dependency_tracking() an API-reference entry explaining its required position before the literal project() call.
Link the HEADERS, SOURCES, TESTS, and EXAMPLES resolution rules near the first setup example.
Link existing detailed sections instead of maintaining duplicate instructions.
Activity
Clarify setup ordering, PowerShell scaffolding, and header portability