Directory & Naming Overhaul #221
Labels
🔥Critical
Must be addressed immediately; blocking core functionality or major bug
Frontend
Frontend Related Issue
New Feature
New feature to be implemented
Refactor
Code Improvement
Milestone
Goal
Migrate from the old
/links/[linkId]
layout to a cleaner/documentAccess/[linkId]
, ensuring all files are renamed and ephemeral styled components are removed or replaced. The new structure must accommodate dynamic, JSON‐based visitor fields alongside future expansions (e.g., more sub‐routes, analytics tracking).Detailed Guidelines
Directory Structure:
Remove ephemeral styled components (e.g.,
styled(Box)(...)
) unless absolutely needed. If a layout style is used multiple times, create a small local component (e.g.,<RowBox />
) or use inlinesx
props:JSON‐Based Fields:
visitorFields
. The actual labels or “required” logic come from the shared config.Use Global Components:
<FormInput>
,<ModalWrapper>
, or similar (insrc/components/
).Tasks
/links/[linkId]
→/documentAccess/[linkId]
and fix references in imports/routes.[linkId]/components
:FileAccessContainer.tsx
→AccessPage.tsx
FileAccessFormModal.tsx
→VisitorInfoModal.tsx
FileAccessMessage.tsx
→AccessError.tsx
sx
or a small local<RowBox />
if reused frequently within the code.page.tsx
for disclaimers/entry flow.<ModalWrapper>
,<FormInput>
, etc.) with minor tweaks, if needed.The text was updated successfully, but these errors were encountered: