CraftLegensy

TheSeekeerWorld · 28 Maja 2015

Witam, chciałbym abyście ocenili moją stronę napisaną na bootstrap. Jest ona w fazie beta więc większość nie będzie działać:

Ogólny wizerunek strony:

Panel Administratora :

Możliwość dodania postów z panelu admina:

Pięć najnowszych postów dodanych przez panel wyświetlane na stronie głównej:

Wyświetlanie postów w nowej stronie:

Planowane:

-dodanie możliwości edycji postów z panelu admina;

(jest to możliwe poprzez bazę mysql)

-dodanie możliwości komentowania poradnika

-dodanie możliwości głosowania na najlepszy poradnik

W odległym czasie:

Panel Logowania dla użytkowników strony

Panel zarządzania swoim profilem

Możliwość dodawania poradników na osobnej podstronie z możliwością ich edycji przez autora oraz administratora

Jeśli macie jakieś propozycje co dodać jeszcze proszę pisać w komentarzach

Pozdrawiam WojtaS.

Jeśli chcesz zobaczyć stronę wejdź na ten adres http://www.craftlegensy.pl

Pamiętaj strona jest w fazie beta i większość przekierowań nie działa !

TheSeekeerWorld · 2 Czerwca 2015

@ref

cody3223 · 2 Czerwca 2015

No to lecim

Brak <!DOCTYPE html>
Na kiego wuja dodajesz tab do każdej linijki, nawet po meta?
Brak kompresji CSS/JS
A teraz grubo, bo używasz <font color="#A0A0A0">
Brak friendly-links czy jakoś tak
Brak alt="" w <img>
<center> ....
I grzech główny czyli nagle na koniec kodu się ucina, i nie ma zamknięcia połowy elementów, razem z html, body
Validator

Line 1, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
<html lang="pl">
✉
The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.

Error Line 3, Column 16: there is no attribute "CHARSET"
	<meta charset="UTF-8">
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Error Line 3, Column 23: required attribute "CONTENT" not specified
	<meta charset="UTF-8">
✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Error Line 14, Column 59: required attribute "TYPE" not specified
												<script src="http://code.jquery.com/jquery.js"></script>
✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Error Line 15, Column 95: required attribute "TYPE" not specified
…"https://maxcdn.bootstrapcdn.com/bootstrap/3.2.0/js/bootstrap.min.js"></script>
✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Error Line 17, Column 48: required attribute "TYPE" not specified
														<script src="css/js/bootstrap.js"></script>
✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Error Line 18, Column 52: required attribute "TYPE" not specified
														<script src="css/js/bootstrap.min.js"></script>
✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Error Line 19, Column 42: required attribute "TYPE" not specified
														<script src="css/js/npm.js"></script>
✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Error Line 40, Column 14: there is no attribute "CLASS"
		<nav class="navbar navbar-default main-menu">
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Error Line 40, Column 47: element "NAV" undefined
		<nav class="navbar navbar-default main-menu">
✉
You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
Error Line 43, Column 72: there is no attribute "DATA-TOGGLE"
…"navbar-toggle collapsed" data-toggle="collapse" data-target="#bs-example-navb…
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Error Line 43, Column 95: there is no attribute "DATA-TARGET"
… collapsed" data-toggle="collapse" data-target="#bs-example-navbar-collapse-1">
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Error Line 62, Column 27: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
						<li class="logo-img"><a href="#"><img src="images/logo.png"></a></li>
✉
The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

Error Line 62, Column 66: required attribute "ALT" not specified
						<li class="logo-img"><a href="#"><img src="images/logo.png"></a></li>
✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Error Line 64, Column 10: end tag for "UL" which is not finished
					</ul>
✉
Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

Error Line 77, Column 21: there is no attribute "DATA-TARGET"
				<li data-target="#carousel-example-generic" data-slide-to="0" class="active…
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Error Line 77, Column 63: there is no attribute "DATA-SLIDE-TO"
… data-target="#carousel-example-generic" data-slide-to="0" class="active"></li>
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Error Line 92, Column 83: there is no attribute "DATA-SLIDE"
…ass="left carousel-control" href="#carousel-example-generic" data-slide="prev">
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Error Line 99, Column 47: required attribute "TYPE" not specified
<script src="http://code.jquery.com/jquery.js"></script>
✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Error Line 100, Column 85: required attribute "TYPE" not specified
…tp://netdna.bootstrapcdn.com/bootstrap/3.0.0-rc1/js/bootstrap.min.js"></script>
✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Warning Line 104, Column 6: NET-enabling start-tag requires SHORTTAG YES
	<br />																					
✉
For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

Error Line 113, Column 52: start tag for "LI" omitted, but its declaration does not permit this
…v class="panel-heading borders-bottom"><h5><font color="aa6708">Tworzenie stop…
✉
Warning Line 124, Column 130: cannot generate system identifier for general entity "width"
…ook.com%2Fserwerroyalcraft%3Fref%3Dhl&width=800&height=558&colorscheme=light&s…
✉
An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (. The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

Entity references start with an ampersand (&) and end with a semicolon (. If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.

If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

Error Line 124, Column 130: general entity "width" not defined and no default entity
…ook.com%2Fserwerroyalcraft%3Fref%3Dhl&width=800&height=558&colorscheme=light&s…
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Error Line 124, Column 135: reference to entity "width" for which no system identifier could be generated
…om%2Fserwerroyalcraft%3Fref%3Dhl&width=800&height=558&colorscheme=light&show_f…
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Info Line 124, Column 129: entity was defined here
…book.com%2Fserwerroyalcraft%3Fref%3Dhl&width=800&height=558&colorscheme=light&…
Warning Line 124, Column 140: cannot generate system identifier for general entity "height"
…serwerroyalcraft%3Fref%3Dhl&width=800&height=558&colorscheme=light&show_faces=…
✉
An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (. The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

Entity references start with an ampersand (&) and end with a semicolon (. If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.

If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

Error Line 124, Column 140: general entity "height" not defined and no default entity
…serwerroyalcraft%3Fref%3Dhl&width=800&height=558&colorscheme=light&show_faces=…
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Error Line 124, Column 146: reference to entity "height" for which no system identifier could be generated
…royalcraft%3Fref%3Dhl&width=800&height=558&colorscheme=light&show_faces=true&h…
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Info Line 124, Column 139: entity was defined here
…Fserwerroyalcraft%3Fref%3Dhl&width=800&height=558&colorscheme=light&show_faces…
Warning Line 124, Column 151: cannot generate system identifier for general entity "colorscheme"
…craft%3Fref%3Dhl&width=800&height=558&colorscheme=light&show_faces=true&header…
✉
An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (. The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

Entity references start with an ampersand (&) and end with a semicolon (. If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.

If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

Error Line 124, Column 151: general entity "colorscheme" not defined and no default entity
…craft%3Fref%3Dhl&width=800&height=558&colorscheme=light&show_faces=true&header…
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Error Line 124, Column 162: reference to entity "colorscheme" for which no system identifier could be generated
…%3Dhl&width=800&height=558&colorscheme=light&show_faces=true&header=false&stre…
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Info Line 124, Column 150: entity was defined here
…lcraft%3Fref%3Dhl&width=800&height=558&colorscheme=light&show_faces=true&heade…
Warning Line 124, Column 169: cannot generate system identifier for general entity "show_faces"
…idth=800&height=558&colorscheme=light&show_faces=true&header=false&stream=true…
✉
An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (. The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

Entity references start with an ampersand (&) and end with a semicolon (. If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.

If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

Error Line 124, Column 169: general entity "show_faces" not defined and no default entity
…idth=800&height=558&colorscheme=light&show_faces=true&header=false&stream=true…
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Error Line 124, Column 179: reference to entity "show_faces" for which no system identifier could be generated
…eight=558&colorscheme=light&show_faces=true&header=false&stream=true&show_bord…
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Info Line 124, Column 168: entity was defined here
…width=800&height=558&colorscheme=light&show_faces=true&header=false&stream=tru…
Warning Line 124, Column 185: cannot generate system identifier for general entity "header"
…558&colorscheme=light&show_faces=true&header=false&stream=true&show_border=fal…
✉
An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (. The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

Entity references start with an ampersand (&) and end with a semicolon (. If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.

If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

Error Line 124, Column 185: general entity "header" not defined and no default entity
…558&colorscheme=light&show_faces=true&header=false&stream=true&show_border=fal…
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Error Line 124, Column 191: reference to entity "header" for which no system identifier could be generated
…&colorscheme=light&show_faces=true&header=false&stream=true&show_border=false" 
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Info Line 124, Column 184: entity was defined here
…=558&colorscheme=light&show_faces=true&header=false&stream=true&show_border=fa…
Warning Line 124, Column 198: cannot generate system identifier for general entity "stream"
…&colorscheme=light&show_faces=true&header=false&stream=true&show_border=false" 
✉
An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (. The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

Entity references start with an ampersand (&) and end with a semicolon (. If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.

If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

Error Line 124, Column 198: general entity "stream" not defined and no default entity
…&colorscheme=light&show_faces=true&header=false&stream=true&show_border=false" 
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Error Line 124, Column 204: reference to entity "stream" for which no system identifier could be generated
…&colorscheme=light&show_faces=true&header=false&stream=true&show_border=false" 
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Info Line 124, Column 197: entity was defined here
…&colorscheme=light&show_faces=true&header=false&stream=true&show_border=false" 
Warning Line 124, Column 210: cannot generate system identifier for general entity "show_border"
…&colorscheme=light&show_faces=true&header=false&stream=true&show_border=false" 
✉
An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (. The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

Entity references start with an ampersand (&) and end with a semicolon (. If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.

If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

Error Line 124, Column 210: general entity "show_border" not defined and no default entity
…&colorscheme=light&show_faces=true&header=false&stream=true&show_border=false" 
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Error Line 124, Column 221: reference to entity "show_border" for which no system identifier could be generated
…&colorscheme=light&show_faces=true&header=false&stream=true&show_border=false" 
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Info Line 124, Column 209: entity was defined here
…&colorscheme=light&show_faces=true&header=false&stream=true&show_border=false" 
Error Line 127, Column 26: there is no attribute "ALLOWTRANSPARENCY"
							allowTransparency="true">
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Warning Line 133, Column 7: NET-enabling start-tag requires SHORTTAG YES
		<br />
✉
For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

Error Line 142, Column 35: required attribute "ALT" not specified
				<img src="images/projekt1.jpg">
✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Error Line 145, Column 35: required attribute "ALT" not specified
				<img src="images/projekt1.jpg">
✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Error Line 148, Column 35: required attribute "ALT" not specified
				<img src="images/projekt1.jpg">
✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Warning Line 151, Column 7: NET-enabling start-tag requires SHORTTAG YES
		<br />
✉
For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

Warning Line 158, Column 34: NET-enabling start-tag requires SHORTTAG YES
						<center><p>Kontakt:</p><br />
✉
For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

Warning Line 159, Column 39: NET-enabling start-tag requires SHORTTAG YES
						<p>[email protected]</p><br />
✉
For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

Warning Line 160, Column 47: NET-enabling start-tag requires SHORTTAG YES
						<p>[email protected]</p><br /></center>
✉
For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

Warning Line 163, Column 46: NET-enabling start-tag requires SHORTTAG YES
						<center><p>Copyright © OneInAll</p><br />
✉
For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

Error Line 164, Column 33: required attribute "ALT" not specified
						<img src="images/logo.png"></center>
✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Warning Line 167, Column 41: NET-enabling start-tag requires SHORTTAG YES
						<center><p>Odwiedz nas na:</p><br />
✉
For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

Error Line 168, Column 38: required attribute "ALT" not specified
							<img src="images/facebook.png"><img src="images/youtube.png">
✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Error Line 168, Column 68: required attribute "ALT" not specified
							<img src="images/facebook.png"><img src="images/youtube.png">
✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Error Line 170, Column 2: end tag for "CENTER" omitted, but its declaration does not permit this
	
✉
You forgot to close a tag, or
you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.
The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

Info Line 167, Column 7: start tag was here
						<center><p>Odwiedz nas na:</p><br />
Error Line 170, Column 2: end tag for "DIV" omitted, but its declaration does not permit this
	
✉
You forgot to close a tag, or
you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.
The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

Info Line 166, Column 6: start tag was here
					<div class="col-sm-4">
Error Line 170, Column 2: end tag for "DIV" omitted, but its declaration does not permit this
	
✉
You forgot to close a tag, or
you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.
The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

Info Line 156, Column 5: start tag was here
				<div class="panel-body">
Error Line 170, Column 2: end tag for "DIV" omitted, but its declaration does not permit this
	
✉
You forgot to close a tag, or
you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.
The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

Info Line 155, Column 4: start tag was here
			<div class="panel">
Error Line 170, Column 2: end tag for "DIV" omitted, but its declaration does not permit this
	
✉
You forgot to close a tag, or
you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.
The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

Info Line 154, Column 3: start tag was here
		<div class="col-sm-13">
Error Line 170, Column 2: end tag for "DIV" omitted, but its declaration does not permit this
	
✉
You forgot to close a tag, or
you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.
The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

Info Line 153, Column 2: start tag was here
	<div class="row">
Error Line 170, Column 2: end tag for "DIV" omitted, but its declaration does not permit this
	
✉
You forgot to close a tag, or
you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.
The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

Info Line 32, Column 2: start tag was here
	<div class="container borders-all borders-bottom cont-color">

Kawamintai · 2 Czerwca 2015

No to lecim

Brak <!DOCTYPE html>
Na kiego wuja dodajesz tab do każdej linijki, nawet po meta?
Brak kompresji CSS/JS
A teraz grubo, bo używasz <font color="#A0A0A0">
Brak friendly-links czy jakoś tak
Brak alt="" w <img>
<center> ....
I grzech główny czyli nagle na koniec kodu się ucina, i nie ma zamknięcia połowy elementów, razem z html, body
Validator

Line 1, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
<html lang="pl">
✉
The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.

Error Line 3, Column 16: there is no attribute "CHARSET"
	<meta charset="UTF-8">
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Error Line 3, Column 23: required attribute "CONTENT" not specified
	<meta charset="UTF-8">
✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Error Line 14, Column 59: required attribute "TYPE" not specified
												<script src="http://code.jquery.com/jquery.js"></script>
✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Error Line 15, Column 95: required attribute "TYPE" not specified
…"https://maxcdn.bootstrapcdn.com/bootstrap/3.2.0/js/bootstrap.min.js"></script>
✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Error Line 17, Column 48: required attribute "TYPE" not specified
														<script src="css/js/bootstrap.js"></script>
✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Error Line 18, Column 52: required attribute "TYPE" not specified
														<script src="css/js/bootstrap.min.js"></script>
✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Error Line 19, Column 42: required attribute "TYPE" not specified
														<script src="css/js/npm.js"></script>
✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Error Line 40, Column 14: there is no attribute "CLASS"
		<nav class="navbar navbar-default main-menu">
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Error Line 40, Column 47: element "NAV" undefined
		<nav class="navbar navbar-default main-menu">
✉
You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
Error Line 43, Column 72: there is no attribute "DATA-TOGGLE"
…"navbar-toggle collapsed" data-toggle="collapse" data-target="#bs-example-navb…
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Error Line 43, Column 95: there is no attribute "DATA-TARGET"
… collapsed" data-toggle="collapse" data-target="#bs-example-navbar-collapse-1">
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Error Line 62, Column 27: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
						<li class="logo-img"><a href="#"><img src="images/logo.png"></a></li>
✉
The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

Error Line 62, Column 66: required attribute "ALT" not specified
						<li class="logo-img"><a href="#"><img src="images/logo.png"></a></li>
✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Error Line 64, Column 10: end tag for "UL" which is not finished
					</ul>
✉
Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

Error Line 77, Column 21: there is no attribute "DATA-TARGET"
				<li data-target="#carousel-example-generic" data-slide-to="0" class="active…
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Error Line 77, Column 63: there is no attribute "DATA-SLIDE-TO"
… data-target="#carousel-example-generic" data-slide-to="0" class="active"></li>
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Error Line 92, Column 83: there is no attribute "DATA-SLIDE"
…ass="left carousel-control" href="#carousel-example-generic" data-slide="prev">
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Error Line 99, Column 47: required attribute "TYPE" not specified
<script src="http://code.jquery.com/jquery.js"></script>
✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Error Line 100, Column 85: required attribute "TYPE" not specified
…tp://netdna.bootstrapcdn.com/bootstrap/3.0.0-rc1/js/bootstrap.min.js"></script>
✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Warning Line 104, Column 6: NET-enabling start-tag requires SHORTTAG YES
	<br />																					
✉
For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

Error Line 113, Column 52: start tag for "LI" omitted, but its declaration does not permit this
…v class="panel-heading borders-bottom"><h5><font color="aa6708">Tworzenie stop…
✉
Warning Line 124, Column 130: cannot generate system identifier for general entity "width"
…ook.com%2Fserwerroyalcraft%3Fref%3Dhl&width=800&height=558&colorscheme=light&s…
✉
An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (. The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

Entity references start with an ampersand (&) and end with a semicolon (. If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.

If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

Error Line 124, Column 130: general entity "width" not defined and no default entity
…ook.com%2Fserwerroyalcraft%3Fref%3Dhl&width=800&height=558&colorscheme=light&s…
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Error Line 124, Column 135: reference to entity "width" for which no system identifier could be generated
…om%2Fserwerroyalcraft%3Fref%3Dhl&width=800&height=558&colorscheme=light&show_f…
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Info Line 124, Column 129: entity was defined here
…book.com%2Fserwerroyalcraft%3Fref%3Dhl&width=800&height=558&colorscheme=light&…
Warning Line 124, Column 140: cannot generate system identifier for general entity "height"
…serwerroyalcraft%3Fref%3Dhl&width=800&height=558&colorscheme=light&show_faces=…
✉
An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (. The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

Entity references start with an ampersand (&) and end with a semicolon (. If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.

If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

Error Line 124, Column 140: general entity "height" not defined and no default entity
…serwerroyalcraft%3Fref%3Dhl&width=800&height=558&colorscheme=light&show_faces=…
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Error Line 124, Column 146: reference to entity "height" for which no system identifier could be generated
…royalcraft%3Fref%3Dhl&width=800&height=558&colorscheme=light&show_faces=true&h…
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Info Line 124, Column 139: entity was defined here
…Fserwerroyalcraft%3Fref%3Dhl&width=800&height=558&colorscheme=light&show_faces…
Warning Line 124, Column 151: cannot generate system identifier for general entity "colorscheme"
…craft%3Fref%3Dhl&width=800&height=558&colorscheme=light&show_faces=true&header…
✉
An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (. The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

Entity references start with an ampersand (&) and end with a semicolon (. If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.

If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

Error Line 124, Column 151: general entity "colorscheme" not defined and no default entity
…craft%3Fref%3Dhl&width=800&height=558&colorscheme=light&show_faces=true&header…
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Error Line 124, Column 162: reference to entity "colorscheme" for which no system identifier could be generated
…%3Dhl&width=800&height=558&colorscheme=light&show_faces=true&header=false&stre…
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Info Line 124, Column 150: entity was defined here
…lcraft%3Fref%3Dhl&width=800&height=558&colorscheme=light&show_faces=true&heade…
Warning Line 124, Column 169: cannot generate system identifier for general entity "show_faces"
…idth=800&height=558&colorscheme=light&show_faces=true&header=false&stream=true…
✉
An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (. The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

Entity references start with an ampersand (&) and end with a semicolon (. If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.

If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

Error Line 124, Column 169: general entity "show_faces" not defined and no default entity
…idth=800&height=558&colorscheme=light&show_faces=true&header=false&stream=true…
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Error Line 124, Column 179: reference to entity "show_faces" for which no system identifier could be generated
…eight=558&colorscheme=light&show_faces=true&header=false&stream=true&show_bord…
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Info Line 124, Column 168: entity was defined here
…width=800&height=558&colorscheme=light&show_faces=true&header=false&stream=tru…
Warning Line 124, Column 185: cannot generate system identifier for general entity "header"
…558&colorscheme=light&show_faces=true&header=false&stream=true&show_border=fal…
✉
An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (. The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

Entity references start with an ampersand (&) and end with a semicolon (. If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.

If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

Error Line 124, Column 185: general entity "header" not defined and no default entity
…558&colorscheme=light&show_faces=true&header=false&stream=true&show_border=fal…
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Error Line 124, Column 191: reference to entity "header" for which no system identifier could be generated
…&colorscheme=light&show_faces=true&header=false&stream=true&show_border=false" 
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Info Line 124, Column 184: entity was defined here
…=558&colorscheme=light&show_faces=true&header=false&stream=true&show_border=fa…
Warning Line 124, Column 198: cannot generate system identifier for general entity "stream"
…&colorscheme=light&show_faces=true&header=false&stream=true&show_border=false" 
✉
An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (. The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

Entity references start with an ampersand (&) and end with a semicolon (. If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.

If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

Error Line 124, Column 198: general entity "stream" not defined and no default entity
…&colorscheme=light&show_faces=true&header=false&stream=true&show_border=false" 
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Error Line 124, Column 204: reference to entity "stream" for which no system identifier could be generated
…&colorscheme=light&show_faces=true&header=false&stream=true&show_border=false" 
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Info Line 124, Column 197: entity was defined here
…&colorscheme=light&show_faces=true&header=false&stream=true&show_border=false" 
Warning Line 124, Column 210: cannot generate system identifier for general entity "show_border"
…&colorscheme=light&show_faces=true&header=false&stream=true&show_border=false" 
✉
An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (. The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

Entity references start with an ampersand (&) and end with a semicolon (. If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.

If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

Error Line 124, Column 210: general entity "show_border" not defined and no default entity
…&colorscheme=light&show_faces=true&header=false&stream=true&show_border=false" 
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Error Line 124, Column 221: reference to entity "show_border" for which no system identifier could be generated
…&colorscheme=light&show_faces=true&header=false&stream=true&show_border=false" 
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Info Line 124, Column 209: entity was defined here
…&colorscheme=light&show_faces=true&header=false&stream=true&show_border=false" 
Error Line 127, Column 26: there is no attribute "ALLOWTRANSPARENCY"
							allowTransparency="true">
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Warning Line 133, Column 7: NET-enabling start-tag requires SHORTTAG YES
		<br />
✉
For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

Error Line 142, Column 35: required attribute "ALT" not specified
				<img src="images/projekt1.jpg">
✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Error Line 145, Column 35: required attribute "ALT" not specified
				<img src="images/projekt1.jpg">
✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Error Line 148, Column 35: required attribute "ALT" not specified
				<img src="images/projekt1.jpg">
✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Warning Line 151, Column 7: NET-enabling start-tag requires SHORTTAG YES
		<br />
✉
For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

Warning Line 158, Column 34: NET-enabling start-tag requires SHORTTAG YES
						<center><p>Kontakt:</p><br />
✉
For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

Warning Line 159, Column 39: NET-enabling start-tag requires SHORTTAG YES
						<p>[email protected]</p><br />
✉
For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

Warning Line 160, Column 47: NET-enabling start-tag requires SHORTTAG YES
						<p>[email protected]</p><br /></center>
✉
For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

Warning Line 163, Column 46: NET-enabling start-tag requires SHORTTAG YES
						<center><p>Copyright © OneInAll</p><br />
✉
For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

Error Line 164, Column 33: required attribute "ALT" not specified
						<img src="images/logo.png"></center>
✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Warning Line 167, Column 41: NET-enabling start-tag requires SHORTTAG YES
						<center><p>Odwiedz nas na:</p><br />
✉
For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

Error Line 168, Column 38: required attribute "ALT" not specified
							<img src="images/facebook.png"><img src="images/youtube.png">
✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Error Line 168, Column 68: required attribute "ALT" not specified
							<img src="images/facebook.png"><img src="images/youtube.png">
✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Error Line 170, Column 2: end tag for "CENTER" omitted, but its declaration does not permit this
	
✉
You forgot to close a tag, or
you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.
The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

Info Line 167, Column 7: start tag was here
						<center><p>Odwiedz nas na:</p><br />
Error Line 170, Column 2: end tag for "DIV" omitted, but its declaration does not permit this
	
✉
You forgot to close a tag, or
you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.
The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

Info Line 166, Column 6: start tag was here
					<div class="col-sm-4">
Error Line 170, Column 2: end tag for "DIV" omitted, but its declaration does not permit this
	
✉
You forgot to close a tag, or
you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.
The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

Info Line 156, Column 5: start tag was here
				<div class="panel-body">
Error Line 170, Column 2: end tag for "DIV" omitted, but its declaration does not permit this
	
✉
You forgot to close a tag, or
you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.
The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

Info Line 155, Column 4: start tag was here
			<div class="panel">
Error Line 170, Column 2: end tag for "DIV" omitted, but its declaration does not permit this
	
✉
You forgot to close a tag, or
you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.
The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

Info Line 154, Column 3: start tag was here
		<div class="col-sm-13">
Error Line 170, Column 2: end tag for "DIV" omitted, but its declaration does not permit this
	
✉
You forgot to close a tag, or
you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.
The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

Info Line 153, Column 2: start tag was here
	<div class="row">
Error Line 170, Column 2: end tag for "DIV" omitted, but its declaration does not permit this
	
✉
You forgot to close a tag, or
you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.
The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

Info Line 32, Column 2: start tag was here
	<div class="container borders-all borders-bottom cont-color">

Niby tak, ale strona ogólnie brzydka nie jest.

TheSeekeerWorld · 3 Czerwca 2015

Brzydka może nie jest ale cody3223 ma racje masę błędów które trzeba poprawić . Dzieki za opinie i zaraz zabieram się za poprawę błędów

NeqGPlay · 3 Czerwca 2015

-Bootstrap napisz cos podobnego w czystym html5 i css3

-Brak html5 lub css3

-Tak, twoj poradnik sie komus przyda po ki c**j robic kontener i uzywac diva? skoro mozna zrobic id lub klase w znaczniku <footer> (dobra wyjdzie na to samo lecz html5 to html5)

-Ja bym uzyl jebanego <aside> na ten sidebar

-Wszystko sie zlewa, nagle wyleciales z projektami nikogo to nie bedzie obchodzic gdyz jest to "blog" projekty mozna zrobic w osobnej karcie.

-Stopka z kibla wyjeta

-Kolory :/

-"Widzę, że zainteresował Cię mój artykuł! Jeśli doceniasz moją pracę, podziel się nim ze znajomymi !" gdzie sa social linki?

-Dlaczego w artykulach jest "text-align: center;" ? lepiej dac "text-align: left;"

-To co pierwszy post wymienil

+Ladny efekt nawigacji

PRACUJ!

//EDIT

-Dlaczego tytul artykulu nie zawiera linku?

cody3223 · 3 Czerwca 2015

-Bootstrap napisz cos podobnego w czystym html5 i css3

-Brak html5 lub css3

-Tak, twoj poradnik sie komus przyda po ki c**j robic kontener i uzywac diva? skoro mozna zrobic id lub klase w znaczniku <footer> (dobra wyjdzie na to samo lecz html5 to html5)

-Ja bym uzyl jebanego <aside> na ten sidebar

-Wszystko sie zlewa, nagle wyleciales z projektami nikogo to nie bedzie obchodzic gdyz jest to "blog" projekty mozna zrobic w osobnej karcie.

-Stopka z kibla wyjeta

-Kolory :/

-"Widzę, że zainteresował Cię mój artykuł! Jeśli doceniasz moją pracę, podziel się nim ze znajomymi !" gdzie sa social linki?

-Dlaczego w artykulach jest "text-align: center;" ? lepiej dac "text-align: left;"

-To co pierwszy post wymienil

+Ladny efekt nawigacji

PRACUJ!

//EDIT

-Dlaczego tytul artykulu nie zawiera linku?

1. Co złego w używaniu Bootstrap?

3. footer jest opcjonalne, nie wymagane przez HTML5, oraz to nie jest poradnik tylko projekt

5. Co proszę? Kogo obchodzi ten projekt? No może autor wstawił go tu aby ktoś go ocenił....

NeqGPlay · 3 Czerwca 2015

1. Co złego w używaniu Bootstrap?

3. footer jest opcjonalne, nie wymagane przez HTML5, oraz to nie jest poradnik tylko projekt

5. Co proszę? Kogo obchodzi ten projekt? No może autor wstawił go tu aby ktoś go ocenił....

Mnie to obchodzi jak mam cos ocenic to chce aby to dzialalo.

Wszystko jest zle w uzywaniu bootstrapa to jak bys mial ferrari i jezdzil 20km/h (CSS3==Ferrari).

Alt tez jest opcjonalny? skoro strona nie zalicza sie nawet do standardu 2015 roku to ja nie chce wiedziec co jeszcze tutaj zobacze.

Zadna z Twoich wypowiedzi nie ma sensu gdyz nie wypowiedziałeś sie wystarczajaca lub/oraz zbyt malo powiedziales.

TheSeekeerWorld · 3 Czerwca 2015

@NeqGPlay Dlaczego nie bootstrap ? Został on chyba stworzony po to aby z niego korzystano a nie po to żeby po prostu był ?

NeqGPlay · 3 Czerwca 2015

@NeqGPlay Dlaczego nie bootstrap ? Został on chyba stworzony po to aby z niego korzystano a nie po to żeby po prostu był ?

Dlatego ze nie nauczysz sie css3 uzywajac tego syfu, zero wiedzy o paginacji a co dopiero o pozycjonowaniu elementow na stronie.

Burned123 · 4 Czerwca 2015

Dlatego ze nie nauczysz sie css3 uzywajac tego syfu, zero wiedzy o paginacji a co dopiero o pozycjonowaniu elementow na stronie.

Widzę, że masz jednak zerowe pojęcia nt. używania frameworków.

Samym bootstrapem nie napiszemy strony, jest jedynie drobną pomocą z której korzysta dosłownie każdy, od całkowicie zielonego po profesjonalistę.

NeqGPlay · 4 Czerwca 2015

Widzę, że masz jednak zerowe pojęcia nt. używania frameworków.

Samym bootstrapem nie napiszemy strony, jest jedynie drobną pomocą z której korzysta dosłownie każdy, od całkowicie zielonego po profesjonalistę.

Gdzie napisalem ze samym bootstrapem napiszemy strone?(wtf to nawet sie nie klei kupy, bootstrap to zwykle klasy)

Tak, bootstrap jest drobna pomoca. Gotowe klasy ktore wpisuje sie w divach duzo kogos naucza.

Krotka pilka, uzywajac jakiegokolwiek frameworka nie nauczysz sie html oraz css koniec.

"Profesjonalisci" rzadko uzywaja bootstrapa bo znaja JS+JQ(oraz duzo innych bibliotek mozna by pisac i pisac), HTML5,CSS3, PS i to sprawia ze zajmuja sie front-endem.

W kazdej odpowiedzi kierowalem sie do stwierdzenia "nauka html5 oraz css3". Nie samym bootstrapem czlowiek zyje.

Moim zdaniem lepiej znac html oraz css niz jakiegos frameworka. Btw jezeli szukasz pracy w front-endzie to nikt Cie nie zatrudni przy znajomosci wylacznie bootstrapa.

//EDIT

Lepiej by zrobil stawiajac to na WP i robiac wlasnego template.

TheSeekeerWorld · 4 Czerwca 2015

Hej, ja ogólnie strony robię jedynie dla tzw. "przyjemności" , nie chcę ani na nich zarabiać ani nic . A tu kolejny projekt z oparciem o bootstrap lecz z dodatkim dużej ilości elementów wykonanych przeze mnie w css. http://www.craftlegensy.pl/demo

Burned123 · 4 Czerwca 2015

Proszę, zapisz tło i umieść na swój serwer ew. skompresuj bo myślałem, że ustawiłeś tło tylko do połowy

Stopka zdecydowanie za duża i jakoś byle jak się komponuje do tego wszystkiego. Niektóre litery w foncie tez dziwnie wyglądaja.

TheSeekeerWorld · 5 Czerwca 2015

@ref

TheSeekeerWorld · 6 Czerwca 2015

@ref

Burned123 · 7 Czerwca 2015

Tak sobie wszedłem na Twoje portfolio chcąc zobaczyć więcej projektów i w oczy rzuciło mi sie to, że tekst "o mnie" oraz w wolnym obszarze pod nim jest identyczny jak u mnie (nawet grafika ta sama). Header również bardzo podobny no i wisienką na torcie jest kod strony. W head jedynie pole z CSS lekko zmieniłeś ale reszta jest tak sama no i oczywiście początek po body, który jest taki sam jak u mnie, reszta to marna kopia kodu. Lepiej pracuj nie tylko nad pisaniem stron ale również nad własną kreatywnością bo z tym co masz daleko nie zajdziesz.

Pozdrawiam.

TheSeekeerWorld · 7 Czerwca 2015

@Burned123 masz w 100 % rację chciałem spróbować zrobić pierwszy raz w życiu taką stronkę i text oraz dużo elementów css zaczerpnąłem od ciebie

**carbonx** · 18 Stycznia 2018

Archiwum.

Powód: Strona jest nieaktywna.

Jeżeli zdecydujesz się na powrót do projektu, użyj opcji raportu aby poinformować o potrzebie przywrócenia tematu.

Zaloguj się

👋 Witaj na MPCForum!

CraftLegensy

Rekomendowane odpowiedzi

Zarchiwizowany