Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Code conventions opstellen #381

Open
Nazneen05x opened this issue Feb 3, 2025 · 3 comments
Open

Code conventions opstellen #381

Nazneen05x opened this issue Feb 3, 2025 · 3 comments
Assignees

Comments

@Nazneen05x
Copy link
Collaborator

Nazneen05x commented Feb 3, 2025

4.1.2 Combineert principes, standaarden, best-practices en conventies op het gebied van frontend design en development en zet deze flexibel en onderbouwd in om een passende oplossing voor een opdrachtgever te realiseren.

FDND Agency

Ik loop stage bij FDND Agency. FDND Agency heeft hun eigen lijst met code conventies waaraan we moeten houden om de website van de opdrachtgever te ontwikkelen.

Code conventions

Bron

Image

CSS conventions

Bron

Image

Custom properties:

  • Pseudo-Private Custom Properties
  • Rijk kleurenpalet met custom properties

Responsive:

  • Container queries (idth-based breakpoints,)
  • Media queries (type, user-preferences, color, etc)

HTML conventions

Bron

Image

SvelteKit conventions

Bron

Image

JavaScript conventions

Bron

@Nazneen05x Nazneen05x self-assigned this Feb 3, 2025
@Nazneen05x
Copy link
Collaborator Author

Nazneen05x commented Feb 4, 2025

Workflow conventions

Write a good README.md

The Girl / Boy Scout Rule

  • Refactoring: Verbeter de duidelijkheid en efficiëntie van code.
  • Redundantie verwijderen: ongebruikte of redundante codesegmenten verwijderen.
  • Hernoemen: Duidelijkere namen voor variabelen en functies.
  • Logica vereenvoudigen: complexe logica of functies stroomlijnen.
  • Documentatie: Opmerkingen of documentatie toevoegen om de leesbaarheid te verbeteren.

Bron

Image

@Nazneen05x
Copy link
Collaborator Author

Nazneen05x commented Feb 4, 2025

Commit strategy

Commit early and often, push once a day
"Committing often is very useful. It’s useful to commit every time you write code that you want to keep. You can even use temporary commits with messages such as "wip" (work in progress)."

Git emoji: https://gitmoji.dev/

Image

@Nazneen05x
Copy link
Collaborator Author

Change log

Bron

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

No branches or pull requests

1 participant