Permalink
Cannot retrieve contributors at this time
Name already in use
A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Lab-2/Lab2_thoots.html
Go to fileThis commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
161 lines (146 sloc)
8.81 KB
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<!DOCTYPE html> | |
<html lang="en-US"> | |
<head> | |
<style> | |
h1 {text-align: center;} | |
h2 {font-size: 30px; text-align: center;} | |
h3 {font-size: 30px; font-weight: bold;} | |
h4 {font-size: 20px;} | |
p {text-align: center;} | |
nav {text-align: center;} | |
</style> | |
<!-- Comments from https://developer.mozilla.org/en-US/docs/Learn/HTML/Introduction_to_HTML/Document_and_website_structure --> | |
<meta charset = "utf-8"> | |
<title> | |
Ebony's Resume | |
<!-- | |
TODO (1 pt): Provide a title to your page. For example: Jane's Resume. Try to be brief. | |
--> | |
</title> | |
</head> | |
<body> | |
<header role = "banner"> | |
<!-- Usually a big strip across the top with a big heading, logo, and perhaps a tagline. This usually stays the same from one webpage to another. --> | |
<!-- | |
TODO (1 pt): Provide a header to your web page. | |
1. Use the highest level heading to present the page title (E.g. Your Name). | |
2. Use a paragraph to showcase how you position yourself on the job market. E.g. your professional title, domain, accomplishments, etc. | |
--> | |
<h1>Ebony Moore</h1> | |
<h2>Seattle, WA | (123) 456-7891 | emoore@email.com</h2> | |
<a name="summary"></a><h2>Summary</h2> | |
<p> | |
With over 15 years of experience, I am a highly skilled and results-oriented Software Engineer. | |
My professional journey has encompassed diverse environments, allowing me to adeptly navigate a wide range of programs and technologies. | |
Throughout my career, I have consistently demonstrated a commitment to delivering high-quality outcomes, showcasing both my expertise and versatility | |
in the dynamic field of software engineering. | |
</p> | |
</header> | |
<nav> | |
<!-- Links to the site's main sections; usually represented by menu buttons, links, or tabs. Like the header, this content usually remains consistent from one webpage to another — having inconsistent navigation on your website will just lead to confused, frustrated users. Many web designers consider the navigation bar to be part of the header rather than an individual component, but that's not a requirement; in fact, some also argue that having the two separate is better for accessibility, as screen readers can read the two features better if they are separate. --> | |
<!-- | |
TODO (2 pts): Create an unordered list of the key section name of your resume. For example: | |
- Profile Summary | |
- Work Experience | |
- Educaiton | |
- Skill | |
- ... | |
Your resume should at least contain three sections: Work Experience, Education, Skills (you can rename the section titles.) | |
--> | |
<a href="#summary">Summary</a> | |
<a href="#experience">Experience</a> | |
<a href="#education">Education</a> | |
<a href="#skills">Skills</a> | |
<a href="#contact">Contact</a> | |
</nav> | |
<main> | |
<!-- for content unique to this page. Use <main> only once per page, and put it directly inside <body>. Ideally this shouldn't be nested within other elements. --> | |
<section> | |
<!-- for grouping together a single part of the page that constitutes one single piece of functionality (e.g., a mini map, or a set of article headlines and summaries), or a theme. It's considered best practice to begin each section with a heading; also note that you can break <article>s up into different <section>s, or <section>s up into different <article>s, depending on the context. --> | |
<article> | |
<!-- encloses a block of related content that makes sense on its own without the rest of the page (e.g., a single blog post). --> | |
<a name="experience"></a><h3>Work Experience</h3> | |
<div> | |
<!-- | |
TODO (4 pts): Fill out your most work experience below. Include a bullet list to describe your key achievements. | |
--> | |
<h4>Senior Software Engineer</h4> | |
<div><span>River Tech</span> | <span>Seattle, WA</span> | <span>Jul '19 - Current</span></div> | |
<div> | |
<ul> | |
<li>Identify and solve software issues in C++ and SQL in Unix and Linux environments</li> | |
<li>Integrate code changes, test code changes, and document code changes</li> | |
<li>Develop automation scripts to test storage appliances in Python</li> | |
<li>Develop base framework with Java, JSP, Struts, CSS, HTML, JavaScript, Oracle, and MS SQL Server</li> | |
<li>Practice agile development methodologies and work with current networking technologies</li> | |
</ul> | |
</div> | |
</div> | |
<div> | |
<h4>Software Tech Lead</h4> | |
<div><span>Tradelot</span> | <span>Seattle, WA</span> | <span>Aug '15 - Jul '19</span></div> | |
<div> | |
<ul> | |
<li>Developed Perl and PHP scripts to translate data between applications</li> | |
<li>Wrote, modified, and debugged software for clients</li> | |
<li>Created and deployed web pages with HTML, JSP, JavaScript, and CSS</li> | |
<li>Wrote Python scripts to load data and parse XML documents</li> | |
</ul> | |
</div> | |
</div> | |
<div> | |
<h4>Software Engineer</h4> | |
<div><span>Retail Ocean</span> | <span>Bellingham, WA</span> | <span>Jan '13 - Aug '15</span></div> | |
<div> | |
<ul> | |
<li>Developed code to complete assigned project by deadline</li> | |
<li>Used Hadoop to build a scalable distributed data solution</li> | |
<li>Utilized Python on Django web framework with Git to develop various front-end and back-end modules</li> | |
</ul> | |
</div> | |
</div> | |
<!-- | |
TODO (4 pts): Add information about another job that you have had, following the same structure as the example above. | |
--> | |
</article> | |
</section> | |
<section> | |
<a name="education"></a><h3>Education</h3> | |
<div> | |
<span>Green Valley State</span><br><span>Aug '99 - Dec '02</span><br><span>Bachelor of Science in Computer Science</span> | |
</div> | |
</section> | |
<section> | |
<a name="skills"></a><h3>Skills</h3> | |
<div> | |
<ul> | |
<li>U.S. Dept. of Defence Top Secret Clearance</li> | |
<li>Certified Scrum Master</li> | |
<li>Cisco Certified Network Professional Routing and Switching</li> | |
<li>Cisco Certified Network Professional Security</li> | |
</ul> | |
</div> | |
</section> | |
<section> | |
<a name="contact"></a><h3>Contact Information</h3> | |
<div> | |
<a href="https://github.itap.purdue.edu/thoots">Personal Github Page</a><br> | |
<a href="https://www.purdue.edu">Education Page</a> | |
</div> | |
</section> | |
<!-- | |
TODO (30 pts): Add the other sections (that is, Education, Skills, and more sections that you listed in the navigation bar). In each section, include a header, and choose the most suitable structure for the corresponding content. | |
Please include at least 3 different sections. Each sections will count as 10 points. | |
--> | |
<aside> | |
<!-- <aside> contains content that is not directly related to the main content but can provide additional information indirectly related to it (glossary entries, author biography, related links, etc.). --> | |
<div><pre>The cat sat on the mat.</pre></div> | |
<!-- Using the <pre> tag, the text above is preserved in that its spaces and line breaks are displayed just as they are written in the source code. | |
A fixed-width font is used to preserve the appearance of the text.--> | |
</aside> | |
</main> | |
<footer> | |
<br><small>© Copyright 2022, Trevor Hoots</small> | |
</footer> | |
</body> | |
</html> |