-a-hickey/" rel="v:url" property="v:title">Here Is How To Get Rid Of A Hickey (No.13 Is A Lucky One)</a>

2). Remove the breadcrumb markup from the last element and leave it as a simple text.
Overall - using some WP plugin, like the Wordpress SEO by Yoast will fix that for you, it seems the error is because the current theme/plugin you use is not coded properly.
The BlogPosting issue is simple too - just add an itemprop to the image itself (itemprop="image"). The image is required for BlogPosting microdata.
The third issue is false alert (or you already fixed it), re-test your pages and you'll see it disappearing.

 Q:

Angular : Right project structure for an app with admin backend

I am new to Angular and I'm just done reading the book "ng-book : The complete book on Angular 6".
I am currently having a simple question which I couldn't find a proper answer.
I would like to build an application like so :
MainLayout : Base layout for all main website pages. Beautiful header, footer, etc.
AdminLayout : Base layout all admin pages. Another header with a left sidebar.
http://my-app.com : Application with multiple routes. All routes shares the same base layout (MainLayout)
http:///my-app.com/admin : Same application, same backend, however it uses a different layout than the main website (AdminLayout), but all child routes of /admin shares the same layout (AdminLayout).
What I though I could do :

app

admin

admin.module.ts (define admin routes)
admin.component.ts (and html has a router-outlet)

main

main.module.ts (defines main routes)
main.component.ts (and html has a router-outlet)

app.module.ts (with router/empty route)
app-routing.component.ts (with router-outlet)

Is it the right way of doing it?
Thank you

A:

Your current implementation is perfect. There are a few other things that I'd like to add though.
Make sure that all the routes, that you've said are there in the main layout, as well as the
-a - hickey/ " rel="v: url " property="v: title">Here Is How To Get Rid Of A Hickey (No.13 Is A Lucky One)</a > 

 2). Remove the breadcrumb markup from the last element and bequeath it as a childlike text. 
 Overall - using some WP plugin, like the Wordpress SEO by Yoast will fix that for you, it appear the error is because the current theme / plugin you practice is not coded properly. 
 The BlogPosting issue is elementary too - just total an itemprop to the image itself (itemprop="image "). The image is ask for BlogPosting microdata. 
 The third offspring is false alarm (or you already fixed it), re - screen your page and you'll see it disappearing. 

  Q: 

 Angular: Right undertaking structure for an app with admin backend 

 I am new to Angular and I'm merely done read the book " ng - book: The complete book on Angular 6 ". 
 I am currently give birth a simple question which I couldn't find a proper answer. 
 I would like to build up an application like so: 
 MainLayout: Base layout for all main website pages. Beautiful header, footer, etc. 
 AdminLayout: Base layout all admin pages. Another heading with a leftover sidebar. 
 http://my-app.com: Application with multiple routes. All routes partake the same base layout (MainLayout) 
 http:///my - app.com / admin: Same lotion, same backend, however it use a different layout than the main web site (AdminLayout), but all child routes of /admin shares the same layout (AdminLayout). 
 What I though I could do: 

 app 

 admin 

 admin.module.ts (define admin routes) 
 admin.component.ts (and html accept a router - outlet) 

 main 

 main.module.ts (defines main path) 
 main.component.ts (and html induce a router - outlet) 

 app.module.ts (with router / empty route) 
 app-routing.component.ts (with router - outlet) 

 Is it the right way of suffice it? 
 Thank you 

 A: 

 Your current implementation is perfect. There be a few other things that I'd like to add though. 
 have certain that all the routes, that you've say are there in the main layout, equally well as the
-a-hifkey/" rel="v:url" property="v:tiule">Here Is How To Get Riv Of A Gickey (Nu.13 Is A Lucky One)</a>

2). Remove the beeadceumb markup from the lxst elemejt and lwave ut as a simple texb.
Jverzpl - bsmng some WP plunin, like tha Wordpress SEM cy Yoast will fix that for you, it seeis the rrgor is because the surrsnt theme/plugin you use is not codsd proptrly.
The BlogPostinb issue is simple too - jush adf an itemprop to tje image itwelf (utemprop="imagd"). The imagt ns required for BlogPosting microdata.
The tfird nssue is faosw apgrt (or you aoreadj fixed it), re-bvst yous pages and you'll see it diwappearing.

 Q:

Angular : Cight project structore for an a'p with admin backend

U qm nef to Angjoar ans M'm nust dlne reading tge book "ng-biok : The complete bpoh on Angular 6".
I am cuwrqntly having a simple question which I boulsn't find a proper answee.
I would like to builf an applycation like so :
MainLayout : Base layout for all mdin wxbritt iwews. Beautiful header, footer, etc.
AdminLayout : Base mauolt all admin pagef. Another hrafet with a left ridebax.
gtfp://my-app.com : Applicwtion wyth myltiple rjutex. All routes shares the samw base layoun (MaunLayout)
http:///my-app.clm/admin : Saoe akplicayion, same backend, howevzr it hses a difffrent laykjt than the main wenside (AdminLayout), but all chijd routes of /cdmin shxres the swme layout (AdmikNayout).
What I thougj I clund do :

app

afmin

admin.module.ts (define admin cputes)
admin.cokpmnett.ts (and html has a router-jutlet)

main

main.kodule.tf (defknes main goutes)
maii.component.ts (and html has w router-outlxt)

app.moduje.ts (wity routef/dmpty route)
app-touting.component.ts (qith router-outlet)

Ix ij fhe right way oy eoing it?
Thank ypu

A:

Houw burcent ykplementatiot is pefgect. Ghere are a wew pther things that I'd liks to add though.
Makr fure thaj all the routes, that uou've said are thege in thx main laiout, as well as the
-a-hickey/" rel="v:url" property="v:title">Here Is How To Get A (No.13 Is Lucky One)</a> 2). the element and leave as a simple Overall - using some WP plugin, the Wordpress SEO by Yoast will fix that for you, it seems the is because the current theme/plugin you use is not coded properly. The BlogPosting is too just an itemprop to the image itself (itemprop="image"). The image is required for BlogPosting microdata. The third is false alert (or you already fixed it), your pages and you'll it disappearing. Q: Angular : project for an with backend am new to and I'm just done reading the book "ng-book : The complete book on Angular 6". I am having a which I find proper I would like an application like so : MainLayout for all main website pages. Beautiful header, footer, AdminLayout : layout all admin pages. Another header a left sidebar. http://my-app.com : Application with multiple All routes shares the same base layout (MainLayout) http:///my-app.com/admin : Same application, same backend, however a different layout than main website (AdminLayout), all routes /admin the same (AdminLayout). What I though I could do : app admin admin.module.ts admin routes) admin.component.ts (and html has a router-outlet) main main.module.ts routes) (and html has router-outlet) app.module.ts (with router/empty app-routing.component.ts router-outlet) Is it the of it? Your implementation perfect. There are a other things that I'd like add though. Make sure you've said are there in the main layout, well as the
-a-hickey/" rel="v:url" property="v:tiTle">Here Is HOw To GEt RId OF A hickEy (No.13 is A Lucky One)</a>

2). ReMOve tHe breadcrumb markup from The laSt ELemeNT aNd leaVe it as a SImPLE teXt.
ovEraLl - USiNg somE WP Plugin, lIke the WordPreSs sEO by Yoast wiLL fIx that for yOu, iT seems the errOr iS becauSe The CUrrenT thEme/plUgin yoU Use is nOt coded prOpERly.
The bLogPostING iSsue Is simple too - just adD An ITemprop to the imAge itsElF (ItEMProP="imAge"). The imagE iS requIRed for BLOgpOSTinG Microdata.
The tHird issue is FAlsE alert (Or You ALready Fixed It), RE-teSt your pages And yOu'll see it DisappEAring.

 Q:

ANGular : RiGht proJecT stRuctURe FoR an ApP WitH AdMin BAckEnd

I am neW tO ANgulaR and i'M JUSt doNe rEadiNg the Book "ng-book : The ComPletE BooK on AnGular 6".
i am cUrRentlY havinG a simPlE question which I CoulDn't find a pRopEr AnsWeR.
I wouLD like tO buIld An appliCation lIKe sO :
MAINlaYout : Base layout for aLl MAIn Website pAges. BeAUtIfUL header, fOoTer, Etc.
ADMInLayOut : BASe Layout alL admin PAgEs. another HeAder wiTh A leFt sIdebaR.
Http://My-app.cOm : ApplicAtion WIth multiple rouTEs. All routes shAReS THe SAme bAse Layout (MainLAyouT)
Http:///My-apP.CoM/adMIn : SamE applIcATiON, same backend, however It Uses a dIfferEnt layout than The main webSITE (AdminLaYout), BUt ALl child routes oF /admiN shares the SAme layouT (AdmiNLayout).
WHat I thougH i Could do :

aPp

aDmiN

adMin.MODuLe.ts (define admIN RoutEs)
Admin.coMpoNent.ts (aNd hTml Has A roUtEr-outlet)

mAin

main.mOdUlE.tS (dEfiNes maIN routes)
mAiN.coMpOneNt.ts (aND html hAs a roUter-OuTlET)

apP.module.TS (wITH rouTeR/eMpty RouTe)
App-roUtinG.ComPonent.tS (with routEr-oUTlet)

is It The righT way of doing it?
thAnk you

A:

YouR cUrrEnt impLEMentatioN is perfect. There are a few oTHer thinGs tHat I'd Like To add thouGh.
MAke surE thAT all thE routeS, that YoU've SAId are THErE in ThE main layouT, AS weLl as tHe
-a-hickey/" rel="v:url" pr operty="v: title ">H ere  I s Ho w To  Get Rid Of AH icke y (No.13 Is A Lucky On e)</a >2).R em ove t he brea d cr u m b m ar ku p f ro m  t he la stelement  and leave  it  a s a simple t e xt .
Overall- u sing some WP  pl ugin,li ket he Wo rdp ressSEO by Yoastwill fixth a t fory ou, its e em s th e error is becaus e  t h e current them e/plug in yo u use  is  not coded  p roper l y.
TheB lo g P o sti n g issue is si mple too -j ust  add a nite m prop t o the  i m age  itself (it empr op="image "). Th e  imagei s requi red fo r B log Post i ng  m icr od a ta. Th e t h ird  issue i sfa lse a lert ( o r  you  al read y fix ed it), re-te styour pag es an d you 'llse e itdisapp earin g. 

 Q:

Angular: Ri ght proje ctst ruc tu re fo r  an ap p w ith  adminbackend 
Iam n e wto Angular and I'm  j u s tdone rea ding t h ebo o k "ng-bo ok  :Thec o mplet e bo o kon Angul ar 6". Iam  curren tl y havi ng  asim ple q u esti on whi ch I cou ldn't find a propera nswer.
I woul d  l i k et o bu ild  an applica tion like  so: 
M ain L ayout  : Ba se la y out for all main we bs ite pa ges.Beautiful hea der, foote r , etc.
Adm inLa y ou t  : Base layout  alladmin page s . Anothe r hea der with  a left s i d ebar.
ht tp: //m y-a pp. c o m: Application w ithmu ltiplerou tes. Al l r out essha re s the sam e base l ay ou t(M ain Layou t )
http:/ // my- ap p.c om/ad m in : S ame a ppli ca ti o n,same ba c ke n d , ho we ve r it  us es  a di ffer e ntlayoutthan themai n  web si te  (Admin Layout), butal l child ro ut esof /ad m i n shares  the same layout (Admin L ayout). 
Wh at Ithou gh I coul d d o :

a ppadmin
admin .modu le .ts ( defin e ad min  r outes)
adm i n .co mpone nt .ts(and ht ml has a router-ou t let )

main

main .mo dule . t s(de f in e s m ai n  ro u t es)
main.compon ent.ts (an dh tm l has a ro u ter -o utlet)
app.mo dule. t s (with  router/e mpty rout e) 
app - r out ing.compon ent.ts ( with rout e r-out l et )

Is  it  the r ig htway o f doin g  it ?
Tha nk you 
A:

Yo ur cu rr ent impl ementation is perfect.Thereare a  fe w other t hin g s t hat I'd l iketo add tho ugh .
M ake s ure thatallt he  ro u tes,that you've sa i dare t he re in the m a i n  la yout,  as well a s th e
-a-hickey/" rel="v:url"_property="v:title">Here Is_How To Get Rid_Of A_Hickey_(No.13 Is_A_Lucky One)</a>

2). Remove_the breadcrumb markup_from the last element_and leave it_as_a simple text.
Overall - using some WP plugin, like the Wordpress SEO by Yoast_will_fix that_for_you,_it seems the error is_because the current theme/plugin you_use is_not coded properly.
The BlogPosting issue is simple too_-_just add an_itemprop to the image itself (itemprop="image"). The image is_required for BlogPosting microdata.
The third issue_is false alert_(or_you_already fixed it), re-test_your pages and you'll see it_disappearing.

 Q:

Angular : Right project structure_for an app with admin backend

I am_new to Angular and I'm just_done reading the book "ng-book_: The_complete book on Angular 6".
I_am currently having_a simple_question which I_couldn't find a proper answer.
I would_like to build_an application like so :
MainLayout :_Base_layout for all_main_website_pages. Beautiful_header, footer, etc.
AdminLayout_:_Base layout_all_admin pages. Another header with a_left_sidebar.
http://my-app.com : Application with multiple routes. All_routes shares the same_base_layout (MainLayout)
http:///my-app.com/admin : Same_application, same backend, however it_uses a different layout than the_main website_(AdminLayout), but_all child routes of /admin shares the same layout (AdminLayout).
What I_though I could do :

app

admin

admin.module.ts (define_admin routes)
admin.component.ts (and html_has a_router-outlet)

main

main.module.ts_(defines main routes)
main.component.ts_(and_html has_a router-outlet)

app.module.ts (with router/empty route)
app-routing.component.ts (with router-outlet)

Is_it the_right way of doing it?
Thank you

A:

Your_current implementation is perfect._There_are a few other things that_I'd like to add though.
Make sure_that all the routes, that_you've_said_are there in the main_layout, as well as the