Yours are stirring up specialized and non-specialized terms apiece. So I attempt to clarify it in two different ways: From a unique, non-specialized level, and from a specialized perspective.
Unique, non-specialized clarification
The substance of your AEM venture, for the most part, contains pages. At the point when a client opens this page, he sees the substance of the page. A picture of the teddy bear, some illustrative content yet, in addition, the header and footer of your page. This is the place segments come in. Substance like the picture, the content, the header and footer are on the whole various parts on that page.
what is htl is like a question what is aem, and what about aem tutorial?
so htl is inbuild language like jsp.
Pages are made out of segments.
Specialized clarification
At the point when engineers attempt to execute pages and segments, they should make page layouts, page parts and segments.
Page layouts are fundamentally XML documents that characterize a couple of things about the page. For instance the title of the page (for example "Substance Page", "News Page", and so on.) that is appeared in the page creation exchange, a portrayal, permitted parent pages (formats), permitted kid pages (layouts) and ways in your substance where this page format can be utilized. Other than those things you can likewise characterize the essential structure of the page. Include a parsys, as of now add parts to this parsys so those segments are "hard wired" into each page you make.
Page segments are the "execution" of page formats. Here you can include the HTML for that page.
Segments are the structure squares of pages. A segment more often than not contains a JSP or HTML record that contains the HTML markup and perhaps some business rationale for that part.
Clearly, there are significantly more interesting points. Be that as it may, this should give you a fundamental diagram over the connection between those things.
Unique, non-specialized clarification
The substance of your AEM venture, for the most part, contains pages. At the point when a client opens this page, he sees the substance of the page. A picture of the teddy bear, some illustrative content yet, in addition, the header and footer of your page. This is the place segments come in. Substance like the picture, the content, the header and footer are on the whole various parts on that page.
what is htl is like a question what is aem, and what about aem tutorial?
so htl is inbuild language like jsp.
Pages are made out of segments.
Specialized clarification
At the point when engineers attempt to execute pages and segments, they should make page layouts, page parts and segments.
Page layouts are fundamentally XML documents that characterize a couple of things about the page. For instance the title of the page (for example "Substance Page", "News Page", and so on.) that is appeared in the page creation exchange, a portrayal, permitted parent pages (formats), permitted kid pages (layouts) and ways in your substance where this page format can be utilized. Other than those things you can likewise characterize the essential structure of the page. Include a parsys, as of now add parts to this parsys so those segments are "hard wired" into each page you make.
Page segments are the "execution" of page formats. Here you can include the HTML for that page.
Segments are the structure squares of pages. A segment more often than not contains a JSP or HTML record that contains the HTML markup and perhaps some business rationale for that part.
Clearly, there are significantly more interesting points. Be that as it may, this should give you a fundamental diagram over the connection between those things.
