[UI/UX]: Add skeleton loading.tsx to all missing page routes

[Muneerali199]

Description

About 17 page routes lack loading.tsx files, leaving users staring at blank screens during navigation. Create skeleton loading pages for each using existing Skeleton components.

Goals

• Create loading.tsx for: about, contact, cv, documents, pricing, profile, settings, showcase, subscription, templates, workspaces, and 6 more
• Each skeleton should match its page layout
• Use existing components from components/skeletons/
• Add subtle animation for perceived performance

Files

• app/about/loading.tsx (new)
• app/contact/loading.tsx (new)
• app/cv/loading.tsx (new)
• app/documents/loading.tsx (new)
• app/pricing/loading.tsx (new)
• app/profile/loading.tsx (new)
• app/settings/loading.tsx (new)
• app/showcase/loading.tsx (new)
• app/subscription/loading.tsx (new)
• app/templates/loading.tsx (new)
• app/workspaces/loading.tsx (new)

[santoshreddy-1362004]

hey @Muneerali199 i want to work on this isssue pls assign me

[pooja-0206]

@Muneerali199 I would like to work on this issue under GSSoC'26.
Please assign this to me!

[aaniya22]

pls assign this to me under gssoc

[shravanithouta108]

Hi @Muneerali199,

I would like to work on this issue under GSSoC'26.

I have already contributed to DraftDeckAI with a successfully merged PR, so I am familiar with the project structure and coding standards.

For this issue, I plan to:

• Audit all page routes that currently lack a loading.tsx
• Reuse the existing skeleton components from components/skeletons/ to maintain UI consistency
• Create route-specific loading states that closely match the final page layouts
• Add subtle loading animations for a smoother user experience
• Verify that all loading screens render correctly during navigation and follow existing design patterns

I can start working on this immediately and ensure the implementation remains lightweight, consistent, and maintainable.

Please consider assigning this issue to me.

Thank you!