Update features section (closes #649)

[christian-carey]

Update text on the landing page

[netlify]

✅ Deploy Preview for drips-app-v2 ready!

Name	Link
🔨 Latest commit	1d84a49
🔍 Latest deploy log	https://app.netlify.com/sites/drips-app-v2/deploys/650b0f719d2322000893d98a
😎 Deploy Preview	https://deploy-preview-669--drips-app-v2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[evvvritt]

Thanks for your help!! 💙

[evvvritt]

Ah wait sorry, can you please update your commit messages to our required formatting (Does it not flag when you try to commit locally?)

Also, please remove the unused CSS indicated when running npm run check

[evvvritt]

(see prev comment in the PR on required changes)

[christian-carey]

Hi @evvvritt.
I was having issues cloning with the github desktop app

, so I forked the repo on the github browser, copied the local changes I made in pages.svelte into the code editor in the github browser and committed from the browser UI and also initiated a pull request there.
I can't find a way to update the commit message from the github browser, and I'm not sure how to run npm check on the browser github repo.

Do you have any advice? :)

Should I make a new fork and try cloning again on github desktop?

[christian-carey]

@evvvritt I added a commit with a message with the required formatting on top of the previous commit. Does that satisfy the requirements?

Also, would you mind sending me a screenshot of the unused CSS when running npm run check so I can remove it?

I tried cloning again, but I seem to have an issue with the emojis in the filenames of the icons that causes an error, so I'm working from the github website.

Thank you for your patience. This is my first contribution to an open source project, and I am trying to learn my way through it.

[evvvritt]

Hi, I would recommend trying to contribute by using tools like Visual Studio Code and git in the command line. I expect using the Github website is very limiting and it's not an effective use of our time to send screenshots of tests you can see if you setup a conventional dev environment, which I encourage you to try :)

[christian-carey]

Fair enough. I did try to clone from VSCode, but all attempts to checkout from git haven't worked. I looked into it more, and it seems to be a MacOS illegal byte sequence issue. I will try it again on windows.

[evvvritt]

Strange, I use MacOS + VS Code. Can you screenshot this byte sequence error please? It's probably these emoji-named files which we can rename

[christian-carey]

I believe it is the emoji-name files. I was able to successfully clone the repo on Windows through VSCode, so I'm working on setting up my dev environment there

[christian-carey]

I deleted the fork I made, remade it, and intend to reinitiate a PR once I get my windows dev env setup, the proper changes made + proper commit msg and an npm run check done.

[christian-carey]

I had problems with windows npm, so I went back to mac. I am having issues with the files with emoji names.

Would this be an issue when I redo the pull request?