AOSSIE-Org / AOSSIE-Org/OrgExplorer

[BUG]: Asset Folder Typo (`assests` -> `assets`)

Offen Anfängerfreundlich
#233 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
bug
Vorherrschende Sprache
JavaScript
Sterne
34
Forks
92
Ø Merge
8 T. 7 Std.
Gemergte PRs (30 T.)
12

Beschreibung

### Bug Description

The `src/assests` directory is misspelled. The correct spelling should be `src/assets`.

This typo is also reflected in multiple import paths, making the project structure inconsistent and potentially causing confusion when adding or referencing assets.

**Proposed Fix**

Rename:

```text
src/assests/
```

to:

```text
src/assets/
```

and update all references from `assests` to `assets`.

Known affected files:

* `src/components/Navbar.jsx`
* `src/components/layout/Footer.jsx`
* `src/pages/Support.jsx`

### Steps to Reproduce

1. Open the `src` directory.
2. Observe the `assests` directory.
3. Check asset imports in `Navbar.jsx`, `Footer.jsx`, and `Support.jsx`.
4. Notice that they reference the misspelled `assests` path.

### Logs and Screenshots

No runtime error is required to reproduce this issue. The problem is visible in the directory structure and import paths.

### Environment Details

* OS: Windows / Linux / macOS
* Project: OrgExplorer
* Frontend: React + Vite

### Impact

Low - Minor inconvenience

### Code of Conduct

- [x] I have joined the [Discord server](https://discord.gg/hjUhu33uAn) and will post updates there
- [x] I have searched existing issues to avoid duplicates

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

Start by locating src/assests and searching the repository for every occurrence of "assests". Inspect the imports in src/components/Navbar.jsx, src/components/layout/Footer.jsx, and src/pages/Support.jsx, then update references alongside the directory rename. Done means the directory is src/assets and no project references use the misspelled path.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
javascript, react, vite
Bereich
frontend
Issue-Typ
Bug
Schwierigkeit
2/5
Geschätzter Aufwand
1-3 Stunden
Aktivitätsstatus
Aktiv
Klarheit
Klar beschrieben
Anfängerfreundlichkeit
85/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.