Skeleton Implementation

[Ishimwe7]

Description
This PR introduces skeleton loading components throughout the application to improve user experience by providing visual feedback during data fetching. These skeleton loaders mimic the structure of the final content, making the interface more intuitive and responsive while the content is loading.

Description of Task Completed

• Implemented skeleton loading components across key areas of the application.
• Skeleton loaders are designed to represent the final structure of the content, enhancing the visual feedback to users during loading times.
• Integrated loaders with existing features to ensure a smooth transition when content is being fetched from the backend.

How to Preview Changes using this Link

• Log in using the provided admin credentials.
• Navigate through sections like Applications or Trainees.
• Ensure that skeleton loaders are displayed whenever there is a delay in content loading, and that they reflect the structure of the final content.

Related Issue
#161

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
atlp-devpulse-fn	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 10, 2024 11:22pm

[mugishaj092]

There are some page is which you didn't implements it's skeleton you can like job posts, trash, application cycles and application form

[Ishimwe7]

There are some page is which you didn't implements it's skeleton you can like job posts, trash, application cycles and application form

Done

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
7140290	Triggered	Generic High Entropy Secret	5e3f3a3	src/components/tinymce/Tinymce.tsx	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[codeclimate]

Code Climate has analyzed commit 5e3f3a3 and detected 5 issues on this pull request.

Here's the issue category breakdown:

Category	Count
Complexity	5

View more on Code Climate.