AEM Site Tutorial Results In Blank Page

Send me an email - scottm@adobe.com. Lets setup a connect session - I just did this again yesterday and it worked.

Scott, I believe there some steps missing from the instructions when you first create the 'contentpage' component.  I would think there should be similar steps that you've highlighted when you create the 'homepage' component (rename homepage.jsp to content.html).

After you create the 'contentpage' component a 'contentpage.jsp' file is auto generated, then after adding the additional HTML files, my final file structure looks like this.  The screen in the article does not show the 'contentpage.jsp' in the directory structure.

What should I do at this point? Rename the contentpage.jsp to content.html? Copy the contents of 'contentpage.jsp' to 'content.html' I created?  Just delete it?  I'll keep experimenting with a various combinations, but no luck so far.

Thanks Scott, but I was getting the blank page after I did the 'Create a Root Page based on the Summit Toys Base Content Page template' step. After creating the Root Page and opening it for editing the render page was blank.  As suggested by someone in the post, I renamed the body.html to contentpage.html, created the Root page again and this time it rendered the page.

I hadn't even gotten to creating the Homepage component step yet.  I will start over from scratch again, because even after getting the page to render the 'Why is my Supertype messed up' header wasn't displaying nor was the CSS styling package applied either.

I am going through article again (we have tested many times).

You have to perform each step specified in the article. When you create a new page based on a super type - make sure you follow instructions -- such as:

Let me work with smacdonald2008​ to get this fixed.

~kautuk

This fixed it for me too.  I'm using the 6.3 QuickStart

Thanks kinmanc39931204. I faced the same problem. Renaming 'body.html' to 'contentpage.html', fixed the issue.

smacdonald2008​, is the tutorial step wrong? or did we miss something?

What was the error - may help ppl in the future?

Thanks for all of the help, a team member of mine discovered my error and has fixed it. The issue is closed, thank you for your responses.