Google Fonts VS Visual Studio Code

I first checking out any good fonts on Google font that fits the theme of the website. I select the Nunito as I could feel the playful vibe behind it.

Visit Google Fonts and search for Lusitana to see what options are available.

Next I spruced up my form's visuals a bit by heading to Google Fonts and finding one that had camping vibes - eventually landing on Amatic SC. Then I had the wild idea of making the form look like a piece of paper, so that I could make the submit button fold the paper up into an envelope or paper airplane and fly off screen if it was submitted successfully (This was EXTREMELY high hopes and I didn't even get around to trying to start this animation in the time I allotted myself 😂). I started by trying to find a crumpled paper look on sites like Hero Patterns, but eventually found myself on this codepen:

BeerCSS supports Material Fonts by default, here is the list of all icons: https://fonts.google.com/

Google Fonts (https://fonts.google.com/)

Google Fonts

==>Click here to access Google Fonts!

==> Click here to visit Google Fonts! ==> Click here to visit Adobe Fonts!

I was doing it all wrong, designing and developing on the fly, using the same tool - VScode; Making one step forward and ten back when I mess up with good code while trying to get rid of the bad. I had gotten away with it for three pages, but it had finally caught up with me.

VSCode

IDE: Many IDES can be used with Flutter but the two most common ones are; Android Studio and Visual Studio Code (VS code). We will work through the setup of VS Code in this article. To download VS Code, just click on Visual Studio Code if you are on Windows or Visual Studio Code for iOS

Excellent!

FWIW, here's the link to troubleshooting vs code performance issues from the project's GitHub Wiki:

https://github.com/Microsoft/vscode/wiki/Performance-Issues

IDE of choice (e.g. Visual Studio Code)

When working in Visual Studio Code (VS Code), start by creating a new Python file for your registration form project. It's helpful to have separate files for different parts of your project.

TIP: Depending on the length of your README, including a table of contents here would be a great addition. You can do this manually, or if you are using VSCode, you can add a TOC that automatically updates as you edit the file using the Markdown All-In-One plugin.

https://github.com/Microsoft/vscode/issues/60#issuecomment-161792005