This course covers essential steps to creating professional resumes that get hiring managers' attention. Learn how to become a resume writer and join the ranks of those who are making a difference by helping others achieve their career goals.

English

This lesson covers:
•The importance of a resume
•Why resumes must be written effectively
•Characteristics of great resumes

Writing with Purpose

This lesson covers the key steps of planning and preparation for resume content development.
Course material included with this lesson:
Resume writing checklist
Resume worksheet - questionnaire for clients to complete

Getting Prepared

This lesson covers each step in the resume building process, including:
<ul>
 <li>Format selection</li>
 <li>Best practices for developing the resume in a timely and efficient manner</li>
 <li>Developing work experience and accomplishments</li>
 <li>Creating a winning performance summary</li>
 <li>Proofreading and polishing</li>
</ul>
Course material included in this lesson:
Resume templates

Building the Resume

This lesson will cover tips and strategies for launching your resume writing service.

Starting Your Own Resume-Writing Business

How to Create Job-Winning Resumes

Certified Professional Resume Writer

Tier 4

Learning how to be successful is a process. This Course is designed to guide you in this process. We begin with the development of an effective mindset and concludes with a plan for living the best years of your life.<div></div><div>The Course can be viewed as a library of strategies and tools to be used in creating a highly successful version of your brain.&nbsp; &nbsp;</div><div></div><div>The Success Mindset Course - 36 lessons contained within 5 ​modules.</div><div></div><div>Each lesson concludes with a required task that will help you build momentum from the very first lesson.</div><div></div><div>It all begins with the mindset and learning how to be comfortable with success. You will Learn to Unlearn the negative beliefs that stand in your way. You will develop a systematic approach to creating and realizing goals. </div><div></div><div>Healthy and unhealthy habits can make or break your success journey. Finally, you will put all the information together and create a plan for living the best years you’ve ever had.</div><div></div><div>In this Course, you’ll learn how to:&nbsp;&nbsp;</div><div></div><div>• Create a mindset that pursues success and isn’t afraid of failure&nbsp;&nbsp;</div><div></div><div>• Attack limiting beliefs</div><div></div><div>• Eliminate self-limiting thought patterns</div><div></div><div>• Create intentions and goals that match your personal version of success</div><div></div><div>• Defeat negative habits and create new, empowering habits</div><div></div><div>• Create a plan for living the best year of your life</div><div></div><div>And much More!</div><div></div><div></div><div>This Course is open to anyone, with the desire to live a more satisfying, exciting and successful life. YOUR SUCCESS in this course depends on your ability to put the information into action. The information is simple, but understanding the information is insufficient. The application of the information is all that matters in the end.</div><div></div><div></div><div>What benefits will I receive from this Course?&nbsp;&nbsp;</div><div></div><div>You’ll create a mindset that is naturally attracted to success.</div><div></div><div>You’ll come to know your own, personal version of success.</div><div></div><div>You’ll learn how to create effective goals and how to make them a reality.</div><div></div><div>You’ll understand how to eliminate negative habits.</div><div></div><div>You’ll learn how to install new habits that support your goals.</div><div></div><div>You’ll have a strategy for putting all the information together to create the best years you’ve ever had.</div><div></div><div></div><div>Is there a particular audience that this Course is geared toward? </div><div></div><div>This Course is geared towards anyone with a desire to be more successful and create the life of their dreams. Anyone that wants to learn how to be a more effective version of him/herself will benefit greatly from this course.</div>

THE SUCCESS BRAIN COURSE

Personal Development Law of Attraction Coach

Tier 7

Coaching

Personal Development

Error

Tier 1

Tier 21

Motivation

If we look at the source of the Scrum, the Scrum Guide (the most up-to-date source), here is how the sprint review is qualified:

A Sprint Review is held at the end of the Sprint to inspect the increment performed and adapt the Product Backlog if necessary. During the Sprint review, the Scrum team and stakeholders discuss what was done during the Sprint.

On this first sentence of the Scrum Guide, it is clear that the idea is based on an inspection of the "Done". However, is a list enough for stakeholders or key users (sometimes themselves stakeholders) to present the rendering in order to improve the exchange between the team and stakeholders?

Based on this and any changes to the Product Backlog that occurred during the sprint, participants collaborate on future work that could be done to optimize value. This meeting is intended to be informal, not a steering meeting, and the presentation of the increment is intended to generate feedback and encourage collaboration.

The Scrum Guide is clear that the Sprint Review is intended to elicit reactions such as feedback; key users, stakeholders and sponsors would be best placed to provide these feedbacks.

This is a maximum of four hours for one-month sprints. For shorter sprints, the event is generally shorter. The Scrum Master ensures that the event takes place and that participants understand its purpose. The Scrum Master teaches everyone involved in it to keep it in the time box.

This part of the Scrum Guide is generally well understood by all the teams I meet. However, I still see some teams that are not very mature, extending the time of the sprint review for no major reason: an attempt to fix a cable problem on site, an unprepared demo, no facilitator, a Product Owner who doesn't know his subject...

The Sprint Review includes the following elements:

Participants include the Scrum team and key stakeholders invited by the Product Owner;

The Product Owner indicates which elements of the Product Backlog have been "Done" and which have not been "Done";

The development team discusses what went well during the Sprint, what problems were encountered, and how these problems were solved;

The development team demonstrates the "Done" work and answers questions about the increment;

The Product Owner discusses the current status of the Product Backlog as it is. He or she projects the projected and delivery dates based on the progress made to date (if necessary);

The whole group agrees on what to do next, so that the sprint review provides valuable input to the next Sprint Planning meeting;

Review of how market conditions or potential use of the product may have dictated what should be done in the future; and,

Review of deadlines, budget, potential functionalities and market conditions for future planned versions of product functionality.

Indeed, contrary to many preconceived ideas, we can talk about items that have not been completed. However, in some contexts where the idea of a deadline is strong, I advise the team to avoid this in order to avoid reactions such as "ah ba it's delivered tomorrow then".

The reminder of the problems encountered is done well during the Review and not during the retrospective; this often makes it possible to justify to the various people present the reasons for possible delays or even to find important supports for the resolution of problems.

"The result of the sprint review is a revised Product Backlog that defines the probable elements for the next Sprint. The Product Backlog can also be globally adjusted to respond to new business opportunities."

As indicated in the last sentence, the purpose of the review is to collect feedback to improve the product. Not inviting your key users, as we still see too often, considerably reduces the interest of this review.

Conclusion: the sprint review is not a demo

Indeed, copying methods without thinking makes no sense but this article was just to remove some beliefs that I still hear today in Scrum teams that the Sprint Demo is an essential ceremony defined by the Scrum Guide...

If the demo is interesting during the review, it is in order to have a better visibility of the product; this should not replace the primary purpose of the sprint review: to review the progress of the product and to collect as much constructive feedback as possible.

The Scrum Guide is available online free of charge in many different languages, if you wish to read it.

There is nothing to prevent you from adapting a ceremony, but it is interesting to know its origins in order to better understand the methodology as a whole.

What is the sprint review?
If we look at the source of the Scrum, the Scrum Guide (the most up-to-date source), here is how the sprint review is qualified:
<blockquote>A Sprint Review is held at the end of the Sprint to inspect the increment performed and adapt the Product Backlog if necessary. During the Sprint review, the Scrum team and stakeholders discuss what was done during the Sprint.</blockquote>
On this first sentence of the Scrum Guide, it is clear that the idea is based on an inspection of the "Done". However, is a list enough for stakeholders or key users (sometimes themselves stakeholders) to present the rendering in order to improve the exchange between the team and stakeholders?
<blockquote>Based on this and any changes to the Product Backlog that occurred during the sprint, participants collaborate on future work that could be done to optimize value. This meeting is intended to be informal, not a steering meeting, and the presentation of the increment is intended to generate feedback and encourage collaboration.</blockquote>
The Scrum Guide is clear that the Sprint Review is intended to elicit reactions such as feedback; key users, stakeholders and sponsors would be best placed to provide these feedbacks.
<blockquote>This is a maximum of four hours for one-month sprints. For shorter sprints, the event is generally shorter. The Scrum Master ensures that the event takes place and that participants understand its purpose. The Scrum Master teaches everyone involved in it to keep it in the time box.</blockquote>
This part of the Scrum Guide is generally well understood by all the teams I meet. However, I still see some teams that are not very mature, extending the time of the sprint review for no major reason: an attempt to fix a cable problem on site, an unprepared demo, no facilitator, a Product Owner who doesn't know his subject...
 
The Sprint Review includes the following elements:
<ul>
 <li>Participants include the Scrum team and key stakeholders invited by the Product Owner;</li>
 <li>The Product Owner indicates which elements of the Product Backlog have been "Done" and which have not been "Done";</li>
 <li>The development team discusses what went well during the Sprint, what problems were encountered, and how these problems were solved;</li>
 <li>The development team demonstrates the "Done" work and answers questions about the increment;</li>
 <li>The Product Owner discusses the current status of the Product Backlog as it is. He or she projects the projected and delivery dates based on the progress made to date (if necessary);</li>
 <li>The whole group agrees on what to do next, so that the sprint review provides valuable input to the next Sprint Planning meeting;</li>
 <li>Review of how market conditions or potential use of the product may have dictated what should be done in the future; and,</li>
 <li>Review of deadlines, budget, potential functionalities and market conditions for future planned versions of product functionality.</li>
</ul>
Indeed, contrary to many preconceived ideas, we can talk about items that have not been completed. However, in some contexts where the idea of a deadline is strong, I advise the team to avoid this in order to avoid reactions such as "ah ba it's delivered tomorrow then".
The reminder of the problems encountered is done well during the Review and not during the retrospective; this often makes it possible to justify to the various people present the reasons for possible delays or even to find important supports for the resolution of problems.
<blockquote>"The result of the sprint review is a revised Product Backlog that defines the probable elements for the next Sprint. The Product Backlog can also be globally adjusted to respond to new business opportunities."</blockquote>
As indicated in the last sentence, the purpose of the review is to collect feedback to improve the product. Not inviting your key users, as we still see too often, considerably reduces the interest of this review.
 
Conclusion: the sprint review is not a demo
Indeed, copying methods without thinking makes no sense but this article was just to remove some beliefs that I still hear today in Scrum teams that the Sprint Demo is an essential ceremony defined by the Scrum Guide...
If the demo is interesting during the review, it is in order to have a better visibility of the product; this should not replace the primary purpose of the sprint review: to review the progress of the product and to collect as much constructive feedback as possible.
The Scrum Guide is available online free of charge in many different languages, if you wish to read it.
There is nothing to prevent you from adapting a ceremony, but it is interesting to know its origins in order to better understand the methodology as a whole.

Agile Leadership Trainer

Many people have hijacked the original purpose of the sprint review but you have to accept it, the sprint review is not a demo. 

THE SPRINT REVIEW IS NOT A DEMO!

Now is the time to learn HTML. Most technology blogs go into the latest changes and tips. They assume you already know the fundamentals. I have some tricks to make your learning process easy and effective. The first trick is to make learning fun, and then it becomes easy to remember.

You’ll learn more if you engage in the material I present hands-on. Don’t just read about HTML and web pages. Pick a topic you enjoy and your retention will go up. A physical therapist taught me to attach new learning to something old and familiar to make it easier to retrieve the information. You can follow the well-worn path and then branch off to the new fork. Try to pick a topic for your practice website pages that you care about, and then you’ll find it much easier to remember what you learn about HTML.

If you are ready to learn, you’re ready to dive in and give coding a try. Trust me, HTML codes make a lot more sense when you are making them work rather than just reading about them. You won’t believe how easy it will be.

HTML is the primary building block of every page, it defines its structure and contains your content. If you are interested in developing web pages, blogs, apps, or email marketing, then it’s essential to learn HTML. HTML is the foundation the other languages build onto, like iron beams holding up a building. CSS controls the design and formatting, like the granite skin of the building and the color of the paint and carpeting. Javascript would be the electrical and plumbing systems, adding interactivity to the building–making it do things.

HTML is so fundamental that even though things change rapidly and constantly as new technologies evolve, I’m confident HTML will still be around. It’s a good starting point–after you learn HTML codes you can move on to CSS for design and visual presentation, and javascript to add interactivity to your pages.

What does HTML stand for? Hypertext Markup Language

HTML stands for HyperText Markup Language. It is a Language, with its own grammar, called Syntax. Markup Language refers to the idea of marking up your content with tags that surround your content and indicate what kind of information it is. For example, a plain paragraph can be surrounded by tags, and an important heading can be wrapped in <h1> tags. The HTML tags mark up the content to indicate a hierarchy of information. HyperText refers to hyperlinking-links-you know when you click on something and you go to a new page.

So now you know and can take geek pride in saying that HTML stands for HyperText Markup Language.

Now is the time to learn HTML. Most technology blogs go into the latest changes and tips. They assume you already know the fundamentals. I have some tricks to make your learning process easy and effective. The first trick is to make learning fun, and then it becomes easy to remember.
You’ll learn more if you engage in the material I present hands-on. Don’t just read about HTML and web pages. Pick a topic you enjoy and your retention will go up. A physical therapist taught me to attach new learning to something old and familiar to make it easier to retrieve the information. You can follow the well-worn path and then branch off to the new fork. Try to pick a topic for your practice website pages that you care about, and then you’ll find it much easier to remember what you learn about HTML.
 
If you are ready to learn, you’re ready to dive in and give coding a try. Trust me, HTML codes make a lot more sense when you are making them work rather than just reading about them. You won’t believe how easy it will be.
 
What is HTML and why should I care?
 
HTML is the primary building block of every page, it defines its structure and contains your content. If you are interested in developing web pages, blogs, apps, or email marketing, then it’s essential to learn HTML. HTML is the foundation the other languages build onto, like iron beams holding up a building. CSS controls the design and formatting, like the granite skin of the building and the color of the paint and carpeting. Javascript would be the electrical and plumbing systems, adding interactivity to the building–making it do things.
HTML is so fundamental that even though things change rapidly and constantly as new technologies evolve, I’m confident HTML will still be around. It’s a good starting point–after you learn HTML codes you can move on to CSS for design and visual presentation, and javascript to add interactivity to your pages.
 
What does HTML stand for? Hypertext Markup Language
 
HTML stands for HyperText Markup Language. It is a Language, with its own grammar, called Syntax. Markup Language refers to the idea of marking up your content with tags that surround your content and indicate what kind of information it is. For example, a plain paragraph can be surrounded by &lt;p&gt; tags, and an important heading can be wrapped in &lt;h1&gt; tags. The HTML tags mark up the content to indicate a hierarchy of information. HyperText refers to hyperlinking-links-you know when you click on something and you go to a new page.
 
So now you know and can take geek pride in saying that HTML stands for HyperText Markup Language.

Programmer

Now is the time to learn HTML, and you can dive into this blog and learn HTML codes. Want to code HTML? Get your hands dirty!



Is HTML easy to learn?

I’ll use them as examples of how HTML is structured, and you’ll learn where to put these tags in your code, and why they’re on every web page.

The Head and Body tags divide your page into sections. The first and most basic HTML tags you need to learn to code are the Head and Body. The head tag and body tag are how we break every web page into two sections.

Each section has an open and closing tag that surrounds the section, like this:

<title>This is the page title : my name : important keywords

These most basic HTML tags will teach you the rules of all HTML code. Note that it’s important you close every tag. Closing tags in HTML always contain a slash. Note also that none of the letters are capitalized, that is standard in HTML.

FYI: element and tag are interchangeable words, they mean the same thing. I like the word tag because it's shorter and easier to say. But you should know that “head tag” and “head element” mean exactly the same thing.

The <head> section contains elements that are needed by the browser to render our web page, but not something that the person viewing the web page needs to be aware of. Generally, it is for stuff that is about the webpage, i.e. meta stuff…much of it is even called “metadata.”

For example, the <head> section contains the title of the web page (which is visible at the top of the window, or tab, in the web browser).

The title is important: you see it (rather than the file name) if you save a bookmark or favorite in your browser. It’s also a good place to insert keywords to help search engines understand the content on your site. Paying attention to your page title can help you improve your search results.

Surround your page title with <title> tags, and make sure it is inside the <head> section of your web page, like this:

<title>This is the page title :: my name :: important

Notice how the <title> is nested inside the <head> tags. This is another thing that’s not only true of basic HTML code, but is also true of almost ALL HTML tags. When you start a tag inside another tag, it’s important that you close it before you close the first tag. That’s what all this talk about proper nesting is about. For example, if you’d written:

…your code would be all messed up, because the <title> is inside the <head> tag, but ends outside its parent tag. If you are finding errors in your code, check to see that everything is nested properly.

All of the page content falls in the <body> section, surrounded by opening and closing <body> tags. You could think of the body tag as being your “page” tag; it defines the visible page, like this:

ALL THE THINGS go in the BODY tag! If you grabbed embed code from YouTube or you’re writing your manifesto, or you have a chart of all the one-hit wonders from 1872 to the present, it all goes in the <body> tag. Remember: ALL THE THINGS go in the <body> tag. Everything that is, erm, not a thing (i.e. no one will see or interact with it) goes in the <head> tag. Much like on your typical human, the <body> tag is usually much bigger and has more stuff. The body tag has more content because it contains the entire visible page.

There’s one more tag that defines the page and appears in nearly every web page: the <html> tag. This tag surrounds the entire page source including both the head and body sections. Its purpose is to identify the language for the browser’s sake. Web pages are written with more than one markup and scripting language. HTML, CSS, PHP, and JavaScript might all be used on one web page. Each language has a different role. For example, HTML defines the structure and contains your content, CSS describes the visual presentation of the objects, and JavaScript provides the interactivity. So, the <html> tag simply helps the browser know that what is coming next is in HTML language. Remember to properly nest all the tags inside the HTML tag.

Basic HTML Codes: Putting it all together

Let’s put all four tags we’ve learned together to make our first web page. It looks like this:

I’ll use them as examples of how HTML is structured, and you’ll learn where to put these tags in your code, and why they’re on every web page.
The Head and Body tags divide your page into sections. The first and most basic HTML tags you need to learn to code are the Head and Body. The head tag and body tag are how we break every web page into two sections.
 
The Body Tag
 
Each section has an open and closing tag that surrounds the section, like this:
 
&lt;head&gt;
&lt;title&gt;This is the page title : my name : important keywords
&lt;/title&gt;
&lt;/head&gt;
&lt;body&gt;
This is the page content
&lt;/body&gt;
&lt;head&gt;
&lt;title&gt;This is the page title : my name : important keywords
&lt;/title&gt;
&lt;/head&gt;
&lt;body&gt;
This is the page content
&lt;/body&gt;
 
These most basic HTML tags will teach you the rules of all HTML code. Note that it’s important you close every tag. Closing tags in HTML always contain a slash. Note also that none of the letters are capitalized, that is standard in HTML.
 
FYI: element and tag are interchangeable words, they mean the same thing. I like the word tag because it's shorter and easier to say. But you should know that “head tag” and “head element” mean exactly the same thing.
 
Basic HTML code: the Head tag &lt;head&gt;
 
The &lt;head&gt; section contains elements that are needed by the browser to render our web page, but not something that the person viewing the web page needs to be aware of. Generally, it is for stuff that is about the webpage, i.e. meta stuff…much of it is even called “metadata.”
 
The Head Tag
 
For example, the &lt;head&gt; section contains the title of the web page (which is visible at the top of the window, or tab, in the web browser).
The title is important: you see it (rather than the file name) if you save a bookmark or favorite in your browser. It’s also a good place to insert keywords to help search engines understand the content on your site. Paying attention to your page title can help you improve your search results.
 
Surround your page title with &lt;title&gt; tags, and make sure it is inside the &lt;head&gt; section of your web page, like this:
 
&lt;head&gt;
&lt;title&gt;This is the page title :: my name :: important
keywords&lt;/title&gt;
&lt;/head&gt;
&lt;head&gt;
&lt;title&gt;This is the page title :: my name :: important
keywords&lt;/title&gt;
&lt;/head&gt;
Notice how the &lt;title&gt; is nested inside the &lt;head&gt; tags. This is another thing that’s not only true of basic HTML code, but is also true of almost ALL HTML tags. When you start a tag inside another tag, it’s important that you close it before you close the first tag. That’s what all this talk about proper nesting is about. For example, if you’d written:
&lt;head&gt;
&lt;title&gt;This is the page title :: my name :: important
keywords
&lt;/head&gt;
&lt;/title&gt;
&lt;head&gt;
&lt;title&gt;This is the page title :: my name :: important
keywords
&lt;/head&gt;
&lt;/title&gt;
…your code would be all messed up, because the &lt;title&gt; is inside the &lt;head&gt; tag, but ends outside its parent tag. If you are finding errors in your code, check to see that everything is nested properly.
 
The Body &lt;body&gt;
 
All of the page content falls in the &lt;body&gt; section, surrounded by opening and closing &lt;body&gt; tags. You could think of the body tag as being your “page” tag; it defines the visible page, like this:
 
&lt;body&gt;Your content here
logos and pictures
videos and text
all of your page content
&lt;/body&gt;
&lt;body&gt;Your content here
logos and pictures
videos and text
all of your page content
&lt;/body&gt;
 
ALL THE THINGS go in the BODY tag! If you grabbed embed code from YouTube or you’re writing your manifesto, or you have a chart of all the one-hit wonders from 1872 to the present, it all goes in the &lt;body&gt; tag. Remember: ALL THE THINGS go in the &lt;body&gt; tag. Everything that is, erm, not a thing (i.e. no one will see or interact with it) goes in the &lt;head&gt; tag. Much like on your typical human, the &lt;body&gt; tag is usually much bigger and has more stuff. The body tag has more content because it contains the entire visible page.
 
The most basic HTML tag: HTML
 
There’s one more tag that defines the page and appears in nearly every web page: the &lt;html&gt; tag. This tag surrounds the entire page source including both the head and body sections. Its purpose is to identify the language for the browser’s sake. Web pages are written with more than one markup and scripting language. HTML, CSS, PHP, and JavaScript might all be used on one web page. Each language has a different role. For example, HTML defines the structure and contains your content, CSS describes the visual presentation of the objects, and JavaScript provides the interactivity. So, the &lt;html&gt; tag simply helps the browser know that what is coming next is in HTML language. Remember to properly nest all the tags inside the HTML tag.
 
Basic HTML Codes: Putting it all together
 
Let’s put all four tags we’ve learned together to make our first web page. It looks like this:
 
&lt;html&gt;
&lt;head&gt;
&lt;title&gt;This is the page title :: my name :: important
keywords&lt;/title&gt;
&lt;/head&gt;
&lt;body&gt;
Your content here
logos and pictures
videos and text
all of your page content
&lt;/body&gt;
&lt;/html&gt;
&lt;html&gt;
&lt;head&gt;
&lt;title&gt;This is the page title :: my name :: important
keywords&lt;/title&gt;
&lt;/head&gt;
&lt;body&gt;
Your content here
logos and pictures
videos and text
all of your page content
&lt;/body&gt;
&lt;/html&gt;

You’ll learn the basics of HTML by getting to know the most basic tags that make up every web page: the head tag and the body tag.

Learn the basics of HTML and become a pro!

Once you learn HTML syntax, you’ll know the basic building blocks of hundreds of HTML codes!

I used to think HTML was difficult and hard to memorize. Now I think HTML is simple and elegant. I’d like to share the breakthrough lightbulb moment that changed my opinion about HTML syntax and made it all simple.

My main problem was that I was trying to memorize everything and I thought everything was equally important and it seemed like hundreds of things to learn and remember.

The turning point was realizing that I should be memorizing the general structure of the code, the part that repeats over and over again, and then I can just look up individual tags, much like learning patterns in the English language helps you read English. You know that a capital letter means a new sentence is beginning, and that a period signifies the sentence is ending. If you know the structure of a language, then it’s not too hard to look up new words and use them in your sentences. HTML is also a language, and if you learn it’s grammar, called syntax, then it is not hard to look up a word you’ve forgotten (a tag) and know just how to type it in your code.

So, the day I learned to memorize the syntax of HTML only, and look up tags changed my view of the HTML language: suddenly it seemed simple.

Here’s the syntax of the entire HTML language:

It’s all about tags, attributes & values

You might already know we often mark up content with HTML tags (also called elements) to indicate to the web browser what kind of content it is. If it is a plain paragraph, then surround it with an open and closing tag. For important content, mark up with <h1> or <h2> heading tags.

It gets a little more complex when we need to add more information to the tags, using a combination of Attributes and Values. Let’s turn something complex into simplicity by learning this pattern of attributes and values.

Attributes and values are inserted into the opening tag. The basic pattern of all HTML tags, called syntax, looks like this:

Here we have a heading and its paragraph, marked up with <h1> HTML tags for the important heading, and the HTML paragraph tag to indicate the beginning and end of the paragraph.

Cat videos have taken over YouTube, causing some to consider it CatTV.

The first thing to notice is that the attributes we are going to add to the tag always go onto the opening tag. The closing tags never have attributes or values added to them. Try to think of Attributes as defining the category I am describing, and the Value - the specific description for that category. For example, if there were a tag to describe hair in HTML, I might add attributes to describe the texture, length, or color of hair.

HTML Syntax using an imaginary tag as an example

Of course, HTML doesn’t actually include a hair tag, or allow you to make up tags, so here’s an example using the paragraph tag that we used above to mark up our important paragraph. Normally paragraph tags are aligned on the left by default. Let’s add an attribute to change that default alignment to be centered.

Within the opening tag, the name of the attribute will be followed by an equal sign. There should be a space after the tag name, to separate the attribute from the tag.

Cat videos have taken over YouTube, causing some to consider it CatTV.

Align is our attribute, but you’ll need the value too whenever you add an attribute. Can you guess what the value is? I’ll not let you shiver in anticipation.

The align attribute can cause text to be left-aligned, centered, right-aligned or justified (aligned on both sides). Always put the value in quotes. In this case, to center the paragraph, add align=”center” inside the opening tag.

When you think of the attribute=”value” pair as a single item, it makes sense that there is a space before the attribute but not after the value is attached to its attribute, so there are never any spaces in the attribute=”value” pair.

Sometimes there is more than one attribute needed by a tag. For example, the <img> tag for images often specifies the height and width of the image. When you need multiple attributes, separate each attribute=”value” pair with one space.

For example, the image tag looks like this:

That’s a lot of attributes! Look carefully at the spaces and you’ll see they are only used to separate each attribute=”value” pair from the tag name and each other.

You might wonder about the order of attributes when you have so many. Does it matter? No!  When using multiple attributes the order does not matter at all. Sweet! One less thing to memorize. So, the following examples are all correct, even though they each place the attributes in a different order.

Once you learn HTML syntax, you’ll know the basic building blocks of hundreds of HTML codes!
 
<h2>HTML syntax</h2>
I used to think HTML was difficult and hard to memorize. Now I think HTML is simple and elegant. I’d like to share the breakthrough lightbulb moment that changed my opinion about HTML syntax and made it all simple.
My main problem was that I was trying to memorize everything and I thought everything was equally important and it seemed like hundreds of things to learn and remember.
The turning point was realizing that I should be memorizing the general structure of the code, the part that repeats over and over again, and then I can just look up individual tags, much like learning patterns in the English language helps you read English. You know that a capital letter means a new sentence is beginning, and that a period signifies the sentence is ending. If you know the structure of a language, then it’s not too hard to look up new words and use them in your sentences. HTML is also a language, and if you learn it’s grammar, called syntax, then it is not hard to look up a word you’ve forgotten (a tag) and know just how to type it in your code.
So, the day I learned to memorize the syntax of HTML only, and look up tags changed my view of the HTML language: suddenly it seemed simple.
 
<h2>Here’s the syntax of the entire HTML language:</h2>
<h3>It’s all about tags, attributes &amp; values</h3>
You might already know we often mark up content with HTML tags (also called elements) to indicate to the web browser what kind of content it is. If it is a plain paragraph, then surround it with an open and closing &lt;p&gt; tag. For important content, mark up with &lt;h1&gt; or &lt;h2&gt; heading tags.
It gets a little more complex when we need to add more information to the tags, using a combination of Attributes and Values. Let’s turn something complex into simplicity by learning this pattern of attributes and values.
Attributes and values are inserted into the opening tag. The basic pattern of all HTML tags, called syntax, looks like this:
&lt;tag attribute=”value”&gt;content&lt;/tag&gt;
 
HTML syntax
<h3>First, the tag</h3>
Here we have a heading and its paragraph, marked up with &lt;h1&gt; HTML tags for the important heading, and the HTML &lt;p&gt; paragraph tag to indicate the beginning and end of the paragraph.
&lt;h1&gt;Do you love or hate cat videos?&lt;/h1&gt;
&lt;p&gt;Cat videos have taken over YouTube, causing some to consider it CatTV.&lt;/p&gt;
<h3>Then, add attributes</h3>
The first thing to notice is that the attributes we are going to add to the tag always go onto the opening tag. The closing tags never have attributes or values added to them. Try to think of Attributes as defining the category I am describing, and the Value - the specific description for that category. For example, if there were a tag to describe hair in HTML, I might add attributes to describe the texture, length, or color of hair.
&lt;hair length=”short” texture=”curly” color=”scarlet”&gt;
 
HTML Syntax using an imaginary tag as an example
 
Of course, HTML doesn’t actually include a hair tag, or allow you to make up tags, so here’s an example using the &lt;p&gt; paragraph tag that we used above to mark up our important paragraph. Normally paragraph tags are aligned on the left by default. Let’s add an attribute to change that default alignment to be centered.
Within the opening tag, the name of the attribute will be followed by an equal sign. There should be a space after the tag name, to separate the attribute from the tag.
&lt;p align=”center”&gt;Cat videos have taken over YouTube, causing some to consider it CatTV.&lt;/p&gt;
Align is our attribute, but you’ll need the value too whenever you add an attribute. Can you guess what the value is? I’ll not let you shiver in anticipation.
<h3>Lastly, add a “value”</h3>
The align attribute can cause text to be left-aligned, centered, right-aligned or justified (aligned on both sides). Always put the value in quotes. In this case, to center the &lt;p&gt; paragraph, add align=”center” inside the opening &lt;p&gt; tag.
&lt;p align=”center”&gt;Cat videos have taken over YouTube, causing some to consider it CatTV.&lt;/p&gt;
When you think of the attribute=”value” pair as a single item, it makes sense that there is a space before the attribute but not after the value is attached to its attribute, so there are never any spaces in the attribute=”value” pair.
<h3>Multiple attributes</h3>
Sometimes there is more than one attribute needed by a tag. For example, the &lt;img&gt; tag for images often specifies the height and width of the image. When you need multiple attributes, separate each attribute=”value” pair with one space.
For example, the image tag looks like this:
&lt;img src=”path-to-my-picture.jpg” alt=”alternative text description of the picture” height=”250” width=”350” /&gt;
That’s a lot of attributes! Look carefully at the spaces and you’ll see they are only used to separate each attribute=”value” pair from the tag name and each other.
You might wonder about the order of attributes when you have so many. Does it matter? No! &nbsp;When using multiple attributes the order does not matter at all. Sweet! One less thing to memorize. So, the following examples are all correct, even though they each place the attributes in a different order.
&lt;img src=”path-to-my-picture.jpg” height=”250” width=”350” alt=”alternative text description of the picture” /&gt;
&lt;img src=”path-to-my-picture.jpg” width=”350” height=”250” alt=”alternative text description of the picture” /&gt;
&lt;img src=”path-to-my-picture.jpg” alt=”alternative text description of the picture” width=”350” height=”250” /&gt;

Learning about HTML syntax and its structure is very important. Focusing on the pattern of HTML will make remembering the code a breeze!

HTML syntax is the grammar of the language

You may want to use an image editing software program to adjust the size, crop, and compress your picture before placing it into your web page with the HTML image tag (<img>).

Compressed File Types: .jpg, .gif, .png, or .svg

Use RGB for web photos, and save CMYK for print

Images are created in various color systems, called “color modes.” An image scanned to black and white only is considered a grayscale image. Images prepared for high-quality press printing may be in CMYK color mode, which is designed for four-color process printing with cyan, magenta, yellow, and black ink. Monitors and devices like phones and tablets use light to create color, not ink. Images prepared for screens should be in RGB color mode, which is an image made out of Red, Green, and Blue light.

You can see the red, green, and blue lights that create your TV screen image. All devices that use light to display images use RGB light combined to create millions of colors. This photo is zoomed in so close to the TV screen that you can actually see the individual red green and blue lights.

If your image is not already RGB color mode, then open any image editing program, like Adobe Photoshop or GIMP, and change the color mode to RGB. In Adobe Photoshop, you can change the color mode by going to the Image menu, select Mode, and then choose RGB.

It is a good idea to crop your image and save it at your intended size. This is good for both your site and for the people using it. The bigger your image is, the more bandwidth it takes for web visitors to download it. As you develop bigger and more popular websites, the costs of keeping bandwidth down become important, and not uploading oversized images is a big part of that. Moreover, bigger images take longer to download. Slow-loading pages frustrate readers, and this, in turn, increases the number of people who leave your site (called “bounce rate”). Finally, if you upload a huge image and use HTML to resize it smaller, this small complication can sometimes lead to code problems later.

You should measure the size of your image in pixels since devices and monitors display in pixels. Some print designers might be used to measuring in inches or centimeters—it’s time to switch to thinking in pixels. You may want to save a copy of your image at twice the pixel size you need, based on your intended display size. The double-size image can be useful when adapting your web page appearance to higher resolution devices, like modern phones and tablets, which can be double the resolution of desktop monitors.

There are three different compression formats you may use for images: JPG, GIF, or PNG. All three formats help reduce the file size of your image for faster downloading on your web page. There are advantages to each format. JPG is usually the best choice for photography, giving you good full color and a fairly small file size. JPG is the most commonly used format on the web. GIF is an older format that doesn’t support as many colors as JPG. The chief advantage of the GIF format is that it supports animation, without needing any plug-in or special software to play it. The PNG format is good when you need transparency — something the JPG doesn’t support. So, if you have clear areas in your photo, choose PNG to retain the transparency. The most common format used for pictures on the web is JPG. Photography compresses very well (small file sizes) using the JPG format, which was created specifically for photos.

You may want to use an image editing software program to adjust the size, crop, and compress your picture before placing it into your web page with the HTML image tag (&lt;img&gt;).
 
Web images should be:
 
<ul>
 <li>RGB Color Mode</li>
 <li>Cropped and Sized</li>
 <li>Low Resolution</li>
 <li>Compressed File Types: .jpg, .gif, .png, or .svg</li>
 <li>Use RGB for web photos, and save CMYK for print</li>
</ul>
Images are created in various color systems, called “color modes.” An image scanned to black and white only is considered a grayscale image. Images prepared for high-quality press printing may be in CMYK color mode, which is designed for four-color process printing with cyan, magenta, yellow, and black ink. Monitors and devices like phones and tablets use light to create color, not ink. Images prepared for screens should be in RGB color mode, which is an image made out of Red, Green, and Blue light.
 
RGB Color TV Screen
 
You can see the red, green, and blue lights that create your TV screen image. All devices that use light to display images use RGB light combined to create millions of colors. This photo is zoomed in so close to the TV screen that you can actually see the individual red green and blue lights.
If your image is not already RGB color mode, then open any image editing program, like Adobe Photoshop or GIMP, and change the color mode to RGB. In Adobe Photoshop, you can change the color mode by going to the Image menu, select Mode, and then choose RGB.
 
Choose RGB color mode in Photoshop
Size and Resolution
 
It is a good idea to crop your image and save it at your intended size. This is good for both your site and for the people using it. The bigger your image is, the more bandwidth it takes for web visitors to download it. As you develop bigger and more popular websites, the costs of keeping bandwidth down become important, and not uploading oversized images is a big part of that. Moreover, bigger images take longer to download. Slow-loading pages frustrate readers, and this, in turn, increases the number of people who leave your site (called “bounce rate”). Finally, if you upload a huge image and use HTML to resize it smaller, this small complication can sometimes lead to code problems later.
You should measure the size of your image in pixels since devices and monitors display in pixels. Some print designers might be used to measuring in inches or centimeters—it’s time to switch to thinking in pixels. You may want to save a copy of your image at twice the pixel size you need, based on your intended display size. The double-size image can be useful when adapting your web page appearance to higher resolution devices, like modern phones and tablets, which can be double the resolution of desktop monitors.
 
Compressing images for the web
Compression formats
 
There are three different compression formats you may use for images: JPG, GIF, or PNG. All three formats help reduce the file size of your image for faster downloading on your web page. There are advantages to each format. JPG is usually the best choice for photography, giving you good full color and a fairly small file size. JPG is the most commonly used format on the web. GIF is an older format that doesn’t support as many colors as JPG. The chief advantage of the GIF format is that it supports animation, without needing any plug-in or special software to play it. The PNG format is good when you need transparency — something the JPG doesn’t support. So, if you have clear areas in your photo, choose PNG to retain the transparency. The most common format used for pictures on the web is JPG. Photography compresses very well (small file sizes) using the JPG format, which was created specifically for photos.


You will learn how to prepare an image for use on your web page. 

Preparing images for the web page

The Product Manager (PM) has a broad vision of the product unlike the Product Owner who is rather on a closed vision (backlog management, vision shared internally within the company...).

The PM will focus on product strategy and trends over time. He will have to analyse the market regularly in order to ensure a good strategy adapted to this product.

He will therefore need to know the market volume, the penetration rate, the competition and everything that will influence the future of the product.

Thanks to all this knowledge, he will master the product's Business Plan (or even create it) and define all the KPIs that the product should try to achieve.

The product manager is far from the development

Unlike the Product Owner, the Product Manager does not work directly with the development teams. Instead, he works with the business teams and the PO (or several when he manages x products).

If the Product Owner can sell the product within the structure, the PM will rather sell the product beyond the structure; for this reason he will not hesitate to go to different events to promote it.

The product manager, closer to the customer

On some products, the Product Owner does not have access to customers. Although agile coaches are increasingly bringing POs to bring customers directly to Review for direct feedback, this role of collecting feedback was more associated with the Product Manager before.

He is the voice of the customers on the product and will have the tough task of having a product that is able to align customers, sponsors and stakeholders.

Difference between Chief Product Owner (CPO) and Product Manager?

Indeed, the role described here is very similar to that of the CPO that I described some time ago in a previous article. In fact, the term CPO was linked to the Scrum of Scrum but it is very close to a role of Product Manager in a very specific context.

If we want to go into detail, the role of the CPO is to lead a Product Owner community while the Product Manager does not really have to do so; however, we are in detail because nothing would prevent it either.

On the other hand, it is quite possible to have a Product Manager for a single product or even a single Product Owner.

A Product Owner who takes on the role of Product Manager?

It is not uncommon to see Product Owners taking on some of the roles of Product Managers; this may seem interesting, but we must be careful about two things that seem complicated to me to respect:

I have difficulty seeing how a PO can correctly assume both roles when external communication is essential.

An essential general vision
The Product Manager (PM) has a broad vision of the product unlike the <a href="https://agileo.teachable.com/p/being-a-great-product-owner" target="_blank">Product Owner</a> who is rather on a closed vision (backlog management, vision shared internally within the company...).
The PM will focus on product strategy and trends over time. He will have to analyse the market regularly in order to ensure a good strategy adapted to this product.
He will therefore need to know the market volume, the penetration rate, the competition and everything that will influence the future of the product.
Thanks to all this knowledge, he will master the product's Business Plan (or even create it) and define all the KPIs that the product should try to achieve.
 
The product manager is far from the development
Unlike the <a href="https://agileo.teachable.com/p/being-a-great-product-owner" target="_blank">Product Owner</a>, the Product Manager does not work directly with the development teams. Instead, he works with the business teams and the PO (or several when he manages x products).
If the <a href="https://agileo.teachable.com/p/being-a-great-product-owner" target="_blank">Product Owner</a> can sell the product within the structure, the PM will rather sell the product beyond the structure; for this reason he will not hesitate to go to different events to promote it.
 
The product manager, closer to the customer
On some products, the <a href="https://agileo.teachable.com/p/being-a-great-product-owner" target="_blank">Product Owner</a> does not have access to customers. Although agile coaches are increasingly bringing POs to bring customers directly to Review for direct feedback, this role of collecting feedback was more associated with the Product Manager before.
He is the voice of the customers on the product and will have the tough task of having a product that is able to align customers, sponsors and stakeholders.
 
Difference between Chief Product Owner (CPO) and Product Manager?
Indeed, the role described here is very similar to that of the CPO that I described some time ago in a previous article. In fact, the term CPO was linked to the Scrum of Scrum but it is very close to a role of Product Manager in a very specific context.
If we want to go into detail, the role of the CPO is to lead a <a href="https://agileo.teachable.com/p/being-a-great-product-owner" target="_blank">Product Owner</a> community while the Product Manager does not really have to do so; however, we are in detail because nothing would prevent it either.
On the other hand, it is quite possible to have a Product Manager for a single product or even a single <a href="https://agileo.teachable.com/p/being-a-great-product-owner" target="_blank">Product Owner</a>.
 
A Product Owner who takes on the role of Product Manager?
It is not uncommon to see <a href="https://agileo.teachable.com/p/being-a-great-product-owner" target="_blank">Product Owners</a> taking on some of the roles of Product Managers; this may seem interesting, but we must be careful about two things that seem complicated to me to respect:
<ul>
 <li>Stay close to the development team</li>
 <li>Don't forget outdoor communication</li>
</ul>
I have difficulty seeing how a PO can correctly assume both roles when external communication is essential.

In agile methods, we always talk about the Product Owner with the popularization of the Scrum. But the role of Product Manager can be very useful in agile organizations.

WHAT IS AN AGILE PRODUCT MANAGER?

Learn everything about beauty creation — from hair styling and nail art to skincare and face yoga. Browse our online courses, dedicated tutors, or stories on any beauty-related topic you want to learn better.

Sharlene Forbes

Sharlene Forbes

THE SUCCESS BRAIN COURSE

Recommended instructors

More Courses You May Like

Katrina Zawawi

Asperger's guide to Emotional Freedom, Health and Wellbeing

Nina Vangerow

30 Day Journal Challenge - Establish a Habit of Daily Journaling

Alex Shoolman

How To Pay Off A Mortgage Early

Hannah Hassler

The Entrepreneurs' Story Creation Guide

Sorin Amzu

50+ Actionable Tips To Make You More Productive

Sharlene Forbes

THE SUCCESS BRAIN COURSE

Bogdan Vaida

The Secrets of Time

Greg Vanderford

How to be Happy in the Modern World

Gilad James

Wicca Level 1: Witchcraft for Beginners

Bogdan Vaida

Test Your Personality Using The DISC Assessment Tool