web dev and digital artist making [email protected]

  • 3 Posts
  • 22 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle


  • For a static site, I would personally choose Astro or SvelteKit—both of those are highly optimized for static sites. In my opinion the syntax of these frameworks feels closer to plain HTML/CSS/JS than React and will naturally teach you more about the fundamentals as you go.

    If you’re just starting out, the most important thing is to really make sure you learn your JavaScript Web APIs and other HTML and CSS fundamentals as you go. The better you know these, the better your websites will be regardless of which framework or tools you choose. These fundamental skills will have the highest reward for you in the long term.

    And ask a ton of questions here too!





  • Definitely take this all with a grain of salt—I am by no means a legal expert, this is just my advice.

    Privacy Policy

    Required by law in Germany if you are collecting any sort of data about your users (even if it is being collected by a third party through your app, or if it is entirely anonymous data).

    Data Processing Agreement

    Required by law in Germany for the same reasons as the Privacy Policy. This agreement makes it clear how your users’ data is used.

    Cookie Policy

    Required by law in Germany if your application uses cookies of any kind (mostly applies to web app and web technologies)

    Terms of Service

    Highly recommended. This may protect you immensely if and when you end up in a legal situation down the road.

    Other

    Otherwise, you should look into these as well if applicable:

    • EULA (if distributing your app to be run on someone else’s device)
    • DCMA Policy (if you host and share any user-generated content)
    • Return Policy (if you are selling anything)

    These documents matter most if (1) there is money involved or (2) when you are receiving, processing, storing, or sharing user-submitted content or any data about your users. This is because you are less likely to end up in a legal mess if you’re not taking people’s money or data.

    Starting out, you can find templates for these online. A template will be better than nothing at all. Then, if you are able down the road, you can hire a legal professional to write and review your documents for you. A legal professional might recommend more specific documents or different versions of the same document as well.

    Not sure about Germany, but in the United States it’s fairly inexpensive to start an LLC. You can then put legal documents under that new entity instead of your own personal name. This can protect you and your own belongings from any unfortunate financial or legal situations.

    Again, if you’re not receiving money or any user data, you don’t have to worry quite as much. However, it never hurts to play it safe. Mistakes happen and anyone can get sued.













  • Like others have said, these are Card components. Usually you’d create an empty low-level Card component that has basic props for different styles (rounded, flat, error, etc.), slots for the content inside, and event handlers for interaction. Then, if you wish, you could make another CardGroup component that can contain Card components and position them using flexbox or grid like the example you provided.

    Another possible name for these components would be List or ListItem