Do My Homework / Homework Help Answers / Computer Science Homework Help / Computer science help with java, html, css

Computer science help with java, html, css

Need help with this question or any other Computer Science assignment help task?

Following the three attached files. I also need this assistance: Milestone Two For milestone two, each student will need to import their HTML pages from assignments 2, 3, and 4 (code to fetch fake photos can be left out, but can be used as reference later) into their Express JS applications. Each Student will also need to implement the remaining portions of their pages. This will include but is not limited to comment section for posts, navigation bars, banners, footers and so on. The Front-end of your application does not need to be completely done by this milestone but the layout and structure and navigation should be close to complete. Please make sure to put the files in the correct folders. For our term project we are going to be using a front-end framework called Handlebars. Handlebars is a templating engine that allows us to easily write dynamic HTML. This is similar to frameworks like React, Vue, Angular, and so on but handlebars is simpler but it is also not as powerful. Since we are using Handlebars, each student will need to convert their HTML pages into handlebars templates. This process will also require breaking your HTML pages down into small chunks called partials (like the idea of components in React). You can think of partials as small components in your application that are reusable for multiple pages of your application. Banners, nav bars and footers are good examples. Partials (and components in react) allow developers to write code once and reuse it multiple times on different pages of your application (See functions in any language). Once imported, please note that it is expected that your application has a theme (color wise). This means all the pages should contain a similar look and feel. It should not be the case that going from page to page the colors are very different. The imported HTML, CSS, and JS files should be stored in the correct folders. The CSS and JS files need to be correctly linked to the HTML file as well. Absolute paths to files ARE NOT ALLOWED. See the express JS slides for a sample file structure. The completed pages need to be pushed to your term project repository. Milestone Three For milestone three, you will begin to implement the remaining portions of your application. This will include creating routes for the functionality of your application. During this milestone, students should focus on completing the log in / log out and registration features of their application. This will give your application the following functionality: • Allow users to enter information to register a new account on your application • Allow users to log in with their credentials on your application • Allow users to log out of your application. The code used to implement the above features need to be pushed to the student’s repository. Note that to complete these features, your database and the database tables will need to be created as well. Not having Sessions completed for this milestone is OK. Milestone Four For milestone four, you will begin to implement the remaining portions of your application. This will include creating routes for handling posts in your applications. Students should focus on completing the following remaining features: creating a post, searching for posts, viewing a post, displaying posts on the home page, and commenting on a post. This will give you application the following functionality: • Allow registered users to create a new image post • Allow users to view many posts on the home(index) page. o The images shown here should be thumbnails and not the original image. • Allow users to search for images on your post. • Allow users to view an individual image post. • Allow registered users to comment on a post.
Additional Instructions:
San Francisco State University CSC 317 – Introduction to Web Development Software Assignment Four Introduction For assignment four, you will be adding JavaScript to your registration form and working with a fake API to populate a home page with fake data. Use of bootstrap and jQuery is NOT ALLOWED. This assignment will get you started working with JavaScript. We will mostly work with the DOM API for this assignment. During the Term Project you will get more experience with the advance features of JavaScript. You must write the additional HTML, CSS, and JavaScript needed for this assignment yourself. PLEASE NOTE, YOU ARE FORBIDDEN TO USE ANY JAVASCRIPT LIBRARY OR HTML5 Tag Attributes THAT DO INPUT VALIDATION UNLESS STATED OTHERWISE. For your HTML files to know what JavaScript code you will be calling, we need to link our JavaScript files to our HTML files. You may link your JavaScript files to your HTML pages by adding the following to the head tag of each HTML page: The type attribute will define the MIME type of the file which tells the browser this is a JavaScript file. The src attribute specifies the URL of an external script file. If you need your JavaScript file to load AFTER the HTML is loaded, you may add the defer attribute to the HTML tag. This will cause the file to load after the html is parsed and the DOM is loaded. Setup Please create a new branch in your repository named “assignment4”. This branch should be created off the main branch. When the assignment is completed, you will merge the assignment4 branch back onto main. Please DO NOT delete branches when assignments are completed. Make sure you are on the main branch of your repository. git checkout main While on the main branch, create a new branch named assignment4 git checkout -b assignment4 Requirements Form Validation ALL forms should be in tags. If your form is built using tags this needs to be removed. FORM VALIDATION DONE VIA HTML5 IS NOT ALLOWED UNLESS OTHERWISE STATED, LATER WE CAN ADD THEM IN TO SIMPLIFY THE VALIDATION. Students are required to add JavaScript to their registration form per the specifications below: ❖ registration.html – for guests to register accounts o require the user to enter a username that begins with a character ([a-zA-Z]). o require the user to enter a username that is 3 or more alphanumeric characters. o require the user to enter a password that is 8 or more characters AND contains at least 1 upper case letter AND 1 number and 1 of the following special characters: / * - + ! @ # $ ^ & ~ [ ] o require that the password and confirm password inputs are the same. o require the user to enter an email that is valid. ▪ This one CAN BE done with the type attribute set to “email” o require the user to select that they are 13+ years of age. ▪ This one CAN BE done with the HTML attribute “required” o require the user to select TOS and Privacy rules. ▪ This one CAN BE done with the HTML attribute “required” When implementing the above requirements think about what happens when these requirements are not met. Some of these requirements can be verified as the user types and some can be verified when the user clicks the submit button. These design choices I leave up to you. If the data is invalid the form SHOULD NOT BE submitted. If the data is valid, simply let the page refresh or show a message saying the form was submitted. [More Content Below] Fetching Posts from an API route For this portion of the assignment, you will need to modify you HTML page named index.html. This page will be used to show results from an AJAX call made to a fake API. We will use the following API route for this assignment: https://jsonplaceholder.typicode.com/albums/2/photos This API route will return an array of JavaScript objects that represent photos. Here is an example of such an object: { "albumId": 2, "id": 51, "title": "non sunt voluptatem placeat consequuntur rem incidunt", "url": "https://via.placeholder.com/300/8e973b", "thumbnailUrl": "https://via.placeholder.com/150/8e973b" } With this object we are going to use the title and url to show a series of photos on our newly created HTML page. These photos will need to be organized neatly onto the page. Please make sure to use the proper CSS and HTML to correctly display the photos. DO NOT STORE THESE PHOTOS IN A HTML TABLE. CANNOT USE THE tag. Please show all photos on your index.html page with the following specifications: • No more than 5 photos per row but must have at least 3. • All photos shown should be the same size. • Each individual object should show the photo and title. How these are organized is up to you. • Photos can either be fetched with a button press or when the html page is loaded. • You may use either the XMLHTTPRequest object, fetch API or axios to retrieve the photos. • Page should be able to handle any number of posts. • At the bottom or top of the page (just after the photos) display the number of photos being displayed • Add an onclick event to each photo container that when clicked, the photo fades out over time. You may choose the speed of the fade out. Once the fadeout is complete, remove the element from the DOM. • After removing the faded out div from the DOM, decrement the photo count by 1 to show the correct current number of photos being shown. [More Content Below] https://jsonplaceholder.typicode.com/albums/2/photos https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest/Using_XMLHttpRequest https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API/Using_Fetch https://github.com/axios/axios Submission When you are done with the assignment, please do the following: ❖ Save all work done. ❖ Commit all HTML, CSS, and JavaScript files to the assignment4 branch. ❖ Push new commits to GitHub (these should be on the assignment4 branch NOT main, assignment2, or assignment3 branch). ❖ Verify the commits are pushed to GitHub by browsing your repo in your favorite browser. ❖ Once verified, merge all the work done from your assignment4 branch to main. Grading Your assignment we be graded on the following criteria’s: ❖ Correctness of required form validation. ❖ Correctness of fetching and displaying results from fake API. GitHub Submission When you have completed the assignment, please commit all code to the assignment4 branch and then merge the changes back into the main branch. You may use the following commands. Committing Changes git adds. git commit -m “some message” git push origin main Merge Changes into Main While on the assignment4 branch, please verify all your changes are on GitHub. You can do this by going to your repository on GitHub and browsing your repository looking for the files. Once you have verified your changes are present on GitHub, switch to the main branch on your local repository (this is on your computer). Once switched execute the following command: git merge assignment4 This will most likely produce a fast-forward, meaning no new commits will be made. Once the merge is completed, push the updated branch to GitHub with the following commands: git push origin main
San Francisco State University CSC 317 – Introduction to Web Development Software Assignment Three Introduction For assignment three, you will be adding CSS to your forms from assignment two. You are not allowed to include any JavaScript with your submission. Use of bootstrap is NOT OK. This will come later. The purpose of only adding CSS and nothing else is to focus on the style and look of your forms. When styling your forms think about the presentation, the colors and layout. Colors used are very important (you will be graded on this as well). The styling of the forms in Assignment three will be used in your final project. The forms that will be styled are index.html, login.html, registration.html, postimage.html and viewpost.html. When styling your forms, try to see that a lot of the styling for one page will and can be used for your other forms. Because of this, we will be storing the CSS rules in a separate file and linking this file to our HTML pages. This will allow for re-use of CSS rules across multiple pages. You may link your CSS files to your HTML pages by adding the following to the head tag of each HTML page: You will need to supply the correct file path for the href attribute. The rel attribute is used to define the relationship with the linked file. We are saying the linked file is an external CSS file. The type attribute tells the browser this is a CSS file. The href attribute stores the path to the CSS file. Setup Please create a new branch in your repo named “assignment3”. This branch should be created off the main branch. When the assignment is completed, you will merge the assignment3 branch back onto main. Please DO NOT delete branches when assignments are completed. Make sure you are on the main branch of your repository. Git checkout main While on the main branch, create a new branch named assignment3 git checkout -b assignment3 [More Content Below] Requirements Students are required to style these five pages in CSS ONLY per the specifications below: ❖ Store CSS rules in a separate file. You may choose the name of the file. ❖ Style index.html – act as landing page for your website ❖ Style login.html – for users to log in ❖ Style registration.html – for guests to register accounts ❖ Style postimage.html – for registered users to post images ❖ Style viewpost.html – for viewing an individual post. ❖ Do your best to use little to no inline CSS. That is CSS stored in HTML files. Submission When you are done with the assignment, please do the following: ❖ Save all work done. ❖ Commit all html and CSS files to the assignment3 branch. ❖ Push new commits to GitHub (these should be on the assignment3 branch NOT main or assignment2). ❖ Verify the commits are pushed to GitHub by browsing your repo in your favorite browser. ❖ Once verified, merge all the work done from your assignment3 branch to main. Grading Your assignment we be graded on the following criteria’s: ❖ Styling: Color Scheme, Layout and Fonts used ❖ Correct usage of CSS id, class, etc. ❖ Amount of inline vs external CSS used. HINT: no inline should be used. ❖ Completion of all requirements. ❖ Completed merge from assignment3 branch to main branch. Note that points will be deducted if small amounts of CSS are submitted. Please try to add more than just background colors and borders. [More Content Below] GitHub Submission When you have completed the assignment, please commit all code to the assignment3 branch and the merge the changes back into the main branch. You may use the following commands. Committing Changes git add . git commit -m “some message” git push origin assignment3 Merge Changes into Main While on the assignment3 branch, please verify all your changes are on GitHub. You can do this by going to your repository on GitHub and browsing your repository looking for the files. Once you have verified your changes are present on GitHub, switch to the main branch on your local repository (this is on your computer). Once switched execute the following command: git merge assignment3 This will most likely produce a fast-forward, meaning no new commits will be made. Once the merge is completed, push the updated branch to GitHub with the following commands: git push origin main
San Francisco State University CSC 317 – Introduction to Web Development Software Assignment Two Introduction For assignment two, you will be implementing a few pages in HTML ONLY. No other languages or technologies can be used. This will come later. The purpose of doing only HTML is to get familiar with HTML and its syntax and to focus only on structure and semantic meaning, HTML’s main purpose. When designing these pages, more specifically, the ones that contain forms, think about the required data is and how they are related. The HTML pages that are being implemented in Assignment two will be used in your final project. The pages that will be implemented are index.html, login.html, registration.html, postimage.html and viewpost.html. Naming of files can differ. Setup Please use the link on iLearn to create your repository for the next few assignments. Please create a new branch in your repo named “assignment2”. This branch should be created off the main branch. When the assignment is completed you will merge the assignment2 branch back onto main. Please DO NOT delete branches when assignments are completed. A new branch can be created with the following command: git checkout -b assignment2 If you want to publish the branch to GitHub, you can do the following command: git push origin assignment2 Requirements Students are required to implement five pages in HTML ONLY per the specifications below: ❖ Index.html – Landing page for application o Must have a banner (pager header, doesn’t need to be an image can be just text) o Must have a nav bar. ▪ Must have nav bar ON EVERY page ▪ Must have each link working on each page. No dead-end pages. o Must have a section for showing main page content o Must have a footer. [ More content below ] ❖ login.html – for users to log in o Must have document title o Must have a section heading introducing the form o Must have a nav bar. o Input fields are REQUIRED to be in form tags. o Must ask user to input a username o Must ask user to input a password. ▪ Password input must be correct input type (i.e. when I type I should not see the password) o Must have the user click a submit button to submit login form. ❖ registration.html – for guests to register accounts o Must have a document title o Must have a section heading introducing the form o Must have a nav bar o Input fields are REQUIRED to be in form tags. o Must ask user to input a username o Must ask user to input an email. o Must ask user to input a password ▪ Password input must be correct input type (i.e. when I type I should not see the password) o Must ask user to input a confirm password ▪ Password input must be correct input type (i.e. when I type I should not see the password) o Must ask user to accept they are 13+ years of age. o Must ask users to accept TOS and Privacy rules ▪ Simply make a link that goes nowhere, but the text says TOS and Privacy Rules. o Must have the user click a submit button to submit registration form. ❖ postimage.html – for registered users to post images o Must have document title o Must have a section heading introducing the form o Must have nav bar o Input fields are REQUIRED to be in form tags. o Must ask user to input a post Title o Must ask user to input a post Description o Must ask user to input an image (or images, this is your choice) o Must ask user to accept Acceptable Use Policy for uploading images. o Must ask user to submit image post via a button. ❖ viewpost.html – for viewing an individual image post o Must have a nav bar o Must have a section for the post’s post title. o Must have a section for the post’s post author o Must have a section for the post’s post creation time. o Must have a section for the post’s image Committing Changes git add . git commit -m “some message” git push origin assignment2 Note if you are not on the main branch then replace main in the above push command with the correct branch name. You can see the branch name using the git status command. Merge Changes into Main While on the assignment2 branch, please verify all your changes are on GitHub. You can do this by going to your repository on GitHub and browsing your repository looking for the files. Once you have verified your changes are present on GitHub, switch to the main branch on your local repository (this is on your computer). git checkout main Once switched execute the following command: git merge assignment2 This will most likely produce a fast-forward, meaning no new commits will be made. Once the merge is completed, push the updated branch to GitHub with the following commands: git push origin main Submission When you are done with the assignment please do the following: ❖ Save all work done. ❖ Commit all html pages to the assignment2 branch. ❖ Push new commits to GitHub (these should be on the assignment2 branch NOT main). ❖ Verify the commits are pushed to GitHub by browsing your repo in your favorite browser. ❖ Once verified, merge all the work done from your assignment2 branch to main. ❖ Then push your main branch to GitHub. Grading Your assignment we be graded on the following criteria’s: ❖ Structure, how we organized are your forms. o Note since these are HTML only pages the visual look won’t be appealing but this is OK. ❖ Correct usage of HTML tags. ❖ Completion of all requirements. ❖ Completed merge from assignment2 branch to main branch.
There are no answers to this question.
Login to buy an answer or post yours. You can also vote on other others

Get Help With a similar task to - Computer science help with java, html, css

Related Questions

Similar orders to Computer science help with java, html, css
Popular Services
Tutlance Experts offer help in a wide range of topics. Here are some of our top services: