Category: Html / CSS

Mountain High RV Sales
Background
UI Design
CIT-461 System Analysis and Design Lab
Lab Assignment #9
Mountain High RV Sales offers new and used recreational vehicles and campers. The
company has a dealer network, but also maintains a Web site where prospective buyers and
sellers can browse through the inventory of new and used vehicles. Mountain High has
grown, and needs a new information system to manage the inventory, dealer operations, and
information about prospective customers. Reed Perry, the owner, asked you to design sample
computer screens and reports that the new system might produce.
Tasks
Design a Home page for the above company.
Prospective buyers might want to search for RVs and campers by features, size, price
range, or manufacturer. Develop a screen design that would permit those choices.
You can use the below link as a sample.
https://www.rvtrader.com/
You can use your imagination but be sure to apply the principles discussed in the chapter.
(A data entry screen design should follow the principles discussed in the chapter, and can
include menu bars, toolbars, dialog boxes, text boxes, toggle buttons, list boxes, scroll bars,
drop-down list boxes, option buttons, check boxes, command buttons, and calendar controls,
among others. It would be a good idea to include a system-generated member number)

html/css I need the code also please. Please use visual studio and use a file I can open please use and read the instructions please

1. Go to GitHub, sign in, and click new to start creating a new repository.
Login Amarquette33
Marlo2124#
o Name your repository m1-hw1-marquette-austin using your name.
o When creating the repository, elect the following options:
 For license, select the MIT license.
 Add a README.md file.
 Add a .gitignore, use the “Node” template.
2. After the repository is created, click clone on the repository page.
o Copy the SSH URL to your clipboard.
o Open your terminal and navigate to the folder you use for development.
o Run git clone  Right-click will allow you to paste into the terminal.
3. After cloning, cd into your repository folder.
4. Open the folder in VS Code by running code . inside the repository directory.
5. Using VS Code, make the following changes:
o Add an entry for .DS_Store to the top of the .gitignore file.
 DS_Store is a MacOS filesystem file that you should not track with Git.
6. Push your changes to GitHub.
o In the integrated terminal (ctrl+` on Windows or ^` on MacOS) execute the following commands:
 Run git add -A to add all files in the project to be committed.
 Run git commit -m “modify gitignore” to commit your changes and add a commit message describing the changes.
 Run git push to push the changes to GitHub.
o Verify your changes by visiting your repository on GitHub.
7. Create a branch and use that branch to modify the README.md file.
o Create a branch by opening the integrated terminal and running git checkout -b modify-readme
o Add the following to README.md using a markdown cheatsheet for reference:
 (NOTE: Use ctrl-shift-v or cmd-shift-v to preview your markdown file in VS Code.)
 Change the main heading (#) to “My First Coding Assignment”
 Under the main heading, add a gif or image that describes/represents you or your personality.
 Please keep the image size to less than 1 MB.
 Add a subheading (##) titled “About Me”, then under it write a few sentences about yourself.
 Add a subheading (##) titled “Past Coding Experience”, then under it describe your past coding experience.
 Add a subheading (##) titled “Career Goals”, then under it make a numbered list of your career goals.
8. Push your branch and make a pull request.
o Follow the same git steps as before:
 Run git add -A
 Run git commit -m “update README.md”
After committing and before pushing, if you were working with other developers you would typically run a git pull origin main to get the latest changes from the main branch before creating a PR. However, since we’re working solo for this assignment we can skip this step.
 Run git push
This will throw an error which will contain a message for setting the “upstream”. Copy the command given and paste it into the terminal and run it.
o After pushing your code, you should see a message with a link for creating a “pull request”. Open that link which will take you to GitHub’s site. Once there, click the button to open a pull request for your changes.
o After opening a pull request, navigate to the newly created pull request’s page in GitHub and click the green button to merge the code into main.

You will need the Google API Book For the Google Map Assignments, we will be treating the book like a lab manual/tutorial and will be going through the exercises in the book. It can be a bit tedious at times, but it will allow you to understand the code better. Do not wait until the last minute to start working on these or you will not be able to finish
1. Be sure to read over chapters 1 and 2 first. Going through Chapter 3 is a good starting point if this is new to you by going through and coding the examples. —————————————————————————————————————————————————————-
2. Google Assignment 1 will consist of the following:
Read carefully through chapters 4 and 5 to complete the map codes presented. For each map, you will end up with 3 files: an html file (.html), a JavaScript file (.js) file and a css file (.css). You can use any text editor (like notepad++) to create the files. Your map should show up generally like the book if everything is correct for each map. And be sure to code each map separately, don’t try to combine them all together. I’m attaching the files for chapter 3 (in the content tab) so you can get an idea. Be careful with file and directory names! That causes the most problems with this assignment. With Chapter 4 you will end up with 1 Map, and should have at least 3 for chapter 5.It is possible to have a few more, depending on how you go through the examples. You will need to submit all of the code for the maps in Chapters 4 and 5 (html, js and css files) (in the Labs & Projects tab). You may want to zip them all in one file to make it easier to attach.
we are treating the Google API 3 book as a tutorial. 3.We will continue working through the google Map files for the other chapters. You should end up with at least 3 maps for chapter 6 and 3 for chapter 7. Try you best on these. There are some sample image files if you need them for chapter 6 located below. Google Assignment 2 will consist of submitting the code for Chapters 6 and 7.
——————————————————-
Ok. Now for the code fix
About three semesters ago Google’s MAP API was updated which will cause the map codes from the book to show with an error. Google now requires a special API Key for all maps. So, when working and testing your maps
Replace the code the book has listed in the HTML file as:
http://maps.google.com/maps/api/js?sensor=false”>
With the following:
https://maps.googleapis.com/maps/api/js?key=AIzaSyB3gseP6Jv4lIPGwUK_CbKJClQpVj2ehzw&callback=myMap “>
That should do the trick I also added some sample files