1. Project management

This week I worked on defining my final project idea and started to getting used to the documentation process.

Learning Git- Documentation

Learning (the core concepts) of Git- I get too excited once I learn the bare minimum of something to get things happening and am very impatient. So now that I have learned how to Git add, git commit, and git push (thanks to the lovely and patient Claire)- Git and I are friends. I will take what I've learned to build a (Crude) website, hoping that I will have more time down the line to come back and make this better.

The first thep was to download GIT and generate an SSH-Key, so that my PC can talk to git.

BY THE WAY, I'm wirting this straight into VS code without a spelling corrector and I can't spell, sorry.

1. Install Git for Windows
2. git config –-global user.name “LISAMEINESZ”
3. git config -–global user.email “lisameinesz@gmail.com”
4. ssh-keygen -t rsa -C "lisameinesz@gmail.com"
5. cat ~/.ssh/id_rsa.pub
6. Then copied the key and added it to the web verstion of Git, accessed through Fab Clouds.

The second step was to sign the student agreement and bring it into my repo:

Issue 01 - preview not working

The Run > Start Debugging tool stopped working. To get around this I installed an extension called 'open in Browser'

Issue 02 - untracked files

When adding images to the site, I uploaded them into my repo folder, with GIT Hub open + did a 'git add .' - as well as a git commit -m ""' but sometimes (randomly it seems) they come up green or 'unlisted' in VS code. I tried googling the issue with no answer. So I asked chat GPT: Why is this happening and how can I fix it?  

Chat Said:
this happens because Git tracks changes based on your .gitignore file and repository settings. Here are a few things to check and fix the issue:
Check if the images are ignored
Open your .gitignore file (found in the root of your repo).
Look for rules that might exclude images, such as *.png, *.jpg, or a folder like /assets/.
If you find such a rule and want to track images, remove or modify it.
Ensure the images are in a tracked directory
If you add images to a folder that isn't already committed, Git may not detect the new files.
Try running git status in the terminal to see if Git recognizes them as new files.
Manually add the images
In VS Code, go to the Source Control panel (Ctrl+Shift+G or Cmd+Shift+G on Mac).
If your images appear untracked, click the + (stage) button next to them or run:
git add path/to/your/image.jpg
Then commit and push as usual.
Check file permissions
Sometimes, Git may not track files properly due to permission issues. Running git add -f path/to/image.jpg forces Git to track the file.
Refresh VS Code
Restart VS Code to refresh the file tree. Sometimes, it doesn’t immediately recognize new files.
If the problem persists, let me know what Git says when you run git status, and I can help troubleshoot further!

I tried the above still with no luck so I sent Chat my git status:

$ git status
On branch main
Your branch is up to date with 'origin/main'.
Changes to be committed:
(use "git restore --staged ..." to unstage)
modified: public/final-project.html
Untracked files:
(use "git add ..." to include in what will be committed)
public/images/fp_rejectedconcept1.png
public/images/fp_rejectedconcept2.png
public/images/fp_rejectedconcept3.png
public/images/fp_rejectedconcept5.png

Chat replied:
Your images are currently untracked, meaning Git is not including them in commits yet. To fix this, follow these steps:
Add the images to Git
Run the following command in your terminal to track the new images:
git add public/images/*.png
Commit the changes
After adding, commit the images with a message:
git commit -m "Added rejected concept images"
Push the changes to GitHub
git push origin main
If git add doesn't work:
Check if they are ignored:
Run:
git check-ignore -v public/images/fp_rejectedconcept1.png
If the image is listed, it's being ignored by .gitignore. You’ll need to edit .gitignore and remove or modify the rule blocking it.
Force add if necessary:
If you suspect Git is ignoring the files incorrectly, you can try:
git add -f public/images/*.png

And this worked! thank you chat :)

Issue 02 - BLOCKED PIPE (sorry)

I broke a pipe on Git by trying to commit over 10mb. It caused a bit of Havoc and I spent half a day trying to get things back to normal! After speaking to Claire, she found a solution- but it's not something I'd do again. Sorry Git! If you don't feel like reading through the below, the solution ended up being, to undo commits: git reset --hard origin/master

  Hi Chat- I added/committed a large file to my repo. I deleted it shortly after.. though fear I broke something? keep getting this error,
    if you could help:

    

  $ git push
  Enumerating objects: 28, done.
  Counting objects: 100% (28/28), done.
  Delta compression using up to 32 threads
  Compressing objects: 100% (19/19), done.
  remote: fatal: pack exceeds maximum allowed size
  fatal: sha1 file '' write error: Broken pipe
  error: remote unpack failed: unpack-objects abnormal exit
  ### ****To gitlab.fabcloud.org:academany/fabacademy/2025/labs/lakemac/students/lisa-meinesz.git
  ###  ! [remote rejected] main -> main (unpacker error)
  ### error: failed to push some refs to 'gitlab.fabcloud.org:academany/fabacademy/2025/labs/lakemac/students/lisa-meinesz.git'****
  

  I've tried doing a hard cleanup : git gc --prune=now
  git repack -a -d --max-pack-size=50m --but this didn't work
  ChatGPT said:
  It seems like the large file you committed and deleted might still be lingering in your Git history or pack files, which is why you're encountering the "unpacker error" and "broken pipe" issues. Even if the file is deleted in the latest commit, Git stores previous versions of files in its history, and pushing those could exceed GitLab’s size limits.
  
  Here’s a focused solution to thoroughly remove the large file and fix the issue:
  
  1. Clean Up Git History Using git filter-repo
  Since you’ve already done a cleanup with git gc and git repack, the best next step is to completely remove the large file from your repo history. You’ll use git filter-repo, which is a more advanced tool for this purpose.
  
  Install git-filter-repo (if you don’t have it yet):
  sh
  Copy
  Edit
  pip install --user git-filter-repo
  Remove the Large File from History:
  Identify the file you want to remove from the history. You might already know the file path. If not, use:
  
  sh
  Copy
  Edit
  git log --all -- path/to/large-file
  Run git filter-repo to remove the file:
  
  sh
  Copy
  Edit
  git filter-repo --path path/to/large-file --invert-paths
  This command will remove the file from all commits in the history.
  
  2. Run Garbage Collection and Repack Again
  After removing the file from history, you need to clean up the repository once more:
  
  sh
  Copy
  Edit
  git gc --prune=now
  git repack -a -d --max-pack-size=50m
  3. Force Push the Changes
  Since you've rewritten the history, you need to force push the changes to GitLab:
  
  sh
  Copy
  Edit
  git push origin main --force
  This should successfully push the clean repo without the large file.
  
  4. Push Smaller Commits (Optional)
  If you're still encountering issues, try pushing a smaller subset of your commits. This can be done by pushing in chunks:
  
  sh
  Copy
  Edit
  git push origin HEAD~5:main
  This will push the last 5 commits at once, reducing the size of the push.
  
  5. Try Git Large File Storage (LFS) (For Future Large Files)
  If you plan to work with large files in the future, consider using Git LFS to prevent this from happening again. Git LFS manages large files outside of the main Git history.
  
  Install Git LFS:
  
  sh
  Copy
  Edit
  git lfs install
  Track Large Files:
  
  sh
  Copy
  Edit
  git lfs track "*.yourfiletype"
  git add .gitattributes
  git commit -m "Track large files with LFS"
  git push origin main
  
  

  
Thanks Chat, none of this worked. (this went on for many hours, I even deleted my local repo and re linked a new one)

I reached out to Claire- and she found a solution than finally worked. It was simply the command, to undo commits:
  git reset --hard origin/master

>
  

CSS

I made the following updates to the CSS. My main issue was playing around with the magrins so that the text didn't stretch out. Going to keep it simple. I don't want to use a theme, since I have to live in this thing for the text few months, I would be nice if It wasn't filled with a bunch of code, where I have no idea what that code does. I'll keep updating this ass the css updates.

    body {
      font-family: monospace;
      margin: 0;
      
    }
    p {
      margin-top: 40px;
      margin-bottom: 30px;
      margin-right: 400px;
      margin-left: 80px;
      font-size: 18;
    }
    .navbar {
      text-align: left;
      width: 100%;
      background-color: #313236;
      border-radius: 1px;
    }
    
    .navbar-inner {
      max-width: 1280px;
      text-indent: 50px;
      margin: 50px auto;
      padding: 30px 0;
    }
    
    .navbar a {
      color: #aaa;
      display: inline-block;
      font-size: 15px;
      padding: 20px;
      text-decoration: none;
    }
    
    .navbar a:hover {
      color: #ffffff;
    }
    
    .content {
      max-width: 5280px;
      margin: auto;
      padding-left: 50px;;
      padding: 50px;
      inline-size: 960px;
      overflow-wrap: break-word;
    
    
    footer {
      font-size: 14px;
      color: #999;
      text-align: center;
      padding: 50px 0 30px 0;
    }
    footer p, footer a {
      font-size: 12px;
      color: #999;
    }