Skip to content

Instantly share code, notes, and snippets.

View nabily4e-dev's full-sized avatar
🤤
🧠 Codeddict 🤤

NabiL Ashbat nabily4e-dev

🤤
🧠 Codeddict 🤤
View GitHub Profile
const numbers = [1, 2, 3, 4, 5];
const words = ['Call', 'me', 'to', 'the', 'moon'];
const doubledNumbers = numbers.map(function(number) {
return number * 2;
});
console.log(doubledNumbers);
const newWords = ['hello', 'world', 'goodbye', 'moon'];
const uppercaseWords = newWords.map(function(word) {
@nabily4e-dev
nabily4e-dev / index.html
Last active February 3, 2023 16:19
An attempt: HTML TailwinCSS nav
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<link rel="stylesheet" href="https://stackpath.bootstrapcdn.com/bootstrap/4.4.1/css/bootstrap.min.css"
integrity="sha384-Vkoo8x4CGsO3+Hhxv8T/Q5PaXtkKtu6ug5TOeNV6gBiFeWPGFN9MuhOf23Q9Ifjh" crossorigin="anonymous" />
<link rel="stylesheet" href="https://unpkg.com/tailwindcss@^1.0/dist/tailwind.min.css" />
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8" />
<title>Sparrow Photography</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<style>
body {
@nabily4e-dev
nabily4e-dev / footer.html
Last active February 3, 2023 16:16
An attempt: HTML TailwinCSS footer
## Conventional Commits 1.0.0
Summary:
The Conventional Commits specification is a convention for writing commit messages on top of commit messages. It provides a lightweight set of rules to make an explicit commit history that makes it easier to write automated tools. This convention is aligned with Semantic Versioning and describes the features, fixes, and breaking changes made in commit messages.
The commit message structure should be as follows:
cppCopy code
"Git commit --amend" is a command in Git that allows you to edit the latest commit without creating a new one. It is useful for correcting mistakes such as forgotten files or formatting errors.
To change the most recent commit message, use "git commit --amend -m "new message"". To add forgotten files, stage the file and then run "git commit --amend --no-edit".
However, it's important to note that amending public commits can cause problems for collaboration. Therefore, it's best to avoid amending a commit that is being developed by other team members.
Implementing git-flow in your project:
1. Install git-flow on your computer. Depending on your operating system, you can use different commands or tools to do this.
2. Go to your project folder and run `git flow init`. This will create the `main` and `develop` branches for you and set up some options.
3. Whenever you want to work on a new feature, run `git flow feature start feature_name`. This will create a new branch from `develop` for your feature.
4. Work on your feature and commit your changes as usual. You can test your changes locally or on a preview server if you have one.
5. When your feature is done, run `git flow feature finish feature_name`. This will merge your feature branch to `develop` and delete it.
6. Repeat steps 3-5 for each feature you want to add.
7. When you are ready to make a new release, run `git flow release start version_number`. This will create a new branch from `develop` for your release.
8. Make any final changes or fixes on your release branch and update the version number if
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8" />
<title>Sparrow Photography</title>
<meta
name="viewport"
content="width=device-width, initial-scale=1.0"
/>

Q1: What is React?

  • A) A programming language
  • B) A JavaScript library for building user interfaces
  • C) A front-end framework for CSS
  • D) A back-end framework for database management

Q2: What problems does React solve?

  • A) Slow rendering of web pages
  • B) Complex manipulation of the DOM
  • C) Error-prone UI development