Skip to content

(documentation) Updated README and added MIT License#70

Merged
Fagerdahl merged 4 commits intomainfrom
69-readmemd
Jun 5, 2025
Merged

(documentation) Updated README and added MIT License#70
Fagerdahl merged 4 commits intomainfrom
69-readmemd

Conversation

@Fagerdahl
Copy link
Collaborator

@Fagerdahl Fagerdahl commented Jun 3, 2025

Pull Request Type

Please check the type of change your PR introduces:

  • Feature (a new feature for the project)
  • Fix (a bug fix)
  • Chore (updating grunt tasks etc; no production code change)
  • Refactor (refactoring production code)
  • Docs (changes to the documentation)
  • Style (formatting, missing semi colons, etc; no production code change)
  • Test (adding missing tests, refactoring tests; no production code change)

Description

[Updated our documentation using this as a tool https://dillinger.io/
I also added a License]

Motivation and Context

[Professional and trustworthy!
Why MIT License you might wonder? My answer is:

  • I want to learn how to do things the PRO level way
  • Allows anyone to use, modify, and share our code — even commercially
  • Ensures we always get credit as the original authors
  • Protects us from being held responsible for what others do with our code
  • It`s an extremely popular and trusted license in the open source community

Screenshots (if appropriate):

[image]

Checklist:

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have named this PR according to following naming convention: #[issue-number] PR description

Additional Information:

[Add any other information about the PR here]

Related Issues:

[Link any related issues here]

@Fagerdahl Fagerdahl linked an issue Jun 3, 2025 that may be closed by this pull request
@vercel
Copy link

vercel bot commented Jun 3, 2025

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

Name Status Preview Comments Updated (UTC)
kino-next-js ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 5, 2025 7:49pm

Copy link
Collaborator

@Deansie Deansie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I really like this readme - well written with detailed descriptions! Nicely done Ronja! :-)

I will approve this PR but the link to the vercel-deployment needs correction as it redirects to the wrong site.

Copy link
Collaborator

@Kalu32k Kalu32k left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Other then what Deansie said it looks great, if we wanna be picky I can remark on one thing and name the SCSS section to Sass and mention that it uses SCSS modules in the description to give it some justice.

Fixed a miss
@Fagerdahl Fagerdahl merged commit 8d38797 into main Jun 5, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ReadMe.Md

3 participants