Deepchand Pati deepchand11

Best Practices for AstroJS, React, Tailwind CSS, and Nanostores

Application Structure

Project Organization

src/
├── components/
│   ├── ui/              # Reusable UI components
│   └── features/        # Feature-specific components

Project Requirements Document: The Urlist Website

The following table outlines the detailed functional requirements of The Urlist website.

Requirement ID	Description	User Story	Expected Behavior/Outcome
FR001	Creating a New URL List	As a user, I want to be able to start a new, empty list so I can begin adding URLs.	The system should provide a clear way for the user to initiate the creation of a new list, potentially presenting an empty list view or an "add new list" button.
FR002	A

Git Commit Best Practices

Basic Rules

Commit Related Changes

A commit should be a wrapper for related changes. For example, fixing two different bugs should produce two separate commits. Small commits make it easier for other developers to understand the changes and roll them back if something went wrong. With tools like the staging area and the ability to stage only parts of a file, Git makes it easy to create very granular commits.

Commit Often

Committing often keeps your commits small and, again, helps you commit only related changes. Moreover, it allows you to share your code more frequently with others. That way it‘s easier for everyone to integrate changes regularly and avoid having merge conflicts. Having large commits and sharing them infrequently, in contrast, makes it hard to solve conflicts.

Installing `nodenv` on ubuntu

nodenv is a great tool, but its installation on Ubuntu is never smooth for me. Here are instructions to install nodenv along with node-build and node-aliases plugins.

ℹ️ note - nodenv recommands updating the PATH though not all programs run in a shell. i prefer adding symlinks to the nodenv binary and shims to make it available everywhere.

The script can be pasted into a terminal as is

# install the base app

The repository for the assignment is public and Github does not allow the creation of private forks for public repositories.

The correct way of creating a private frok by duplicating the repo is documented here.

For this assignment the commands are:

Create a bare clone of the repository. (This is temporary and will be removed so just do it wherever.)

git clone --bare [email protected]:usi-systems/easytrace.git

This tutorial is about setting up a Github account to commit (via SSH) to an existing/new repository and common commands to handle that repository.

1. Setting up git

globally (recommended for one github account / OS user)

git config --global user.email "[email protected]"
git config --global user.name "Your Name"

locally (recommended for multiple github accounts / OS user)

VSCode italic font settings

Add this to settings.json (cmd ,):

{
  "workbench.iconTheme": "material-icon-theme",
  "window.zoomLevel": 0,
  "editor.formatOnSave": true,
  "workbench.colorTheme": "Shades of Purple",
  "files.autoSave": "onWindowChange",

	type(scope): subject

	<body>
	<footer>

	Subject
	Short description of the applied changes.

	Limit the subject line to 50 characters
	Your commit message should not contain any whitespace errors or punctuation marks

	Squashing Commits history
	git checkout my_branch
	git rebase -i HEAD~4
	// Change the pick to fixup for the commits you want to squash
	// If any conflicts occur git rebase --skip
	// Reset the rebase rm -fr ".git/rebase-merge"
	git push --force origin my_branch