Actually...Adobe has been less than helpful in many ways. I'm still trying to get the example index.html file that is based on the Adobe example page of a workspace. I have had zero luck getting this an now it makes me feel like all they are presenting is a mock-up of a workspace page.

This is what I'm trying to get from them and no responses other than how to program for AEM. I know how to do this...I just need the file that produces this...

Thank for your help!

Hi Jared,

Unfortunately IE dosen't seem to work very well with AEM.  I'm not sure why as for many entities, its their sole desktop browser.    I work with one such entity so yes its painful.  I had asked if there was a reason why this was the case and got dead air.  At any rate  Its nearly a must to have Chrome and Firefox (I use chrome when working on AEM)

Great info and would be nice if they updated the instructions for this!

I figured out my problem with Package Manager.  When I would create a package nothing happened.  I was using IE.  I simply went over to Firefox and everything worked properly.  This article explains what to do:  How to Work With Packages .  If it's not working for you, try another browser.  When you add the filter, add /apps/ws.

Updating this thread with some things that I've learned on my journey.  I learned today that the whole business about using Maven to package and deploy as described in Adobe Experience Manager Help | Introduction to Customizing AEM form workspace  isn't really necessary if all you're doing is some minor CSS changes or swapping out images.  You can just follow the "generic" instructions and then make your changes in CRXDE (using WebDAV to upload any additional files like images).  After that you can package your changes using Package Manager (or so they say.  That isn't working for me at the moment, but that's another matter.  If I figure it out I'll post it here.)

Here's another nugget.  To get WebDAV to work, don't believe what it says here:

WebDAV Access

In actual fact, you need to add /lc to the end of your path or you will be unable to connect.  in my case the path for WebDAV is http://localhost:8080/lc.

Excellent community response!

kdenso01, you have been enormously helpful.  I will now punish your helpfulness by abusing it with more questions. 

Okay, with your help, I have successfully completed the "generic" steps.  I can even add some CSS customizations in my handy newStyle.css and they work.  Awesome.  Now what though?  I'd like to save up my precious customizations and deploy them to another environment.  I presume that has something to do with the package manager.  I package up my newly created apps/ws somehow and deploy it elsewhere, right?  If so, please point me to the instructions for doing so.

If that's not how it's done, then I'm guessing the answer has something to do with the subject of this article:

Adobe Experience Manager Help | Introduction to Customizing AEM form workspace

After referencing the "generic" article, this "introduction" article goes on to describe the "ship" package and so on.  Huh?  I don't see how the instructions in the "generic" page connect to this.  The "ship" package contains all the CSS and other bits used in the workspace application.  So why did I do that other stuff to create the application under apps/ws?  It seems like there's some missing instructions that connect the steps listed in the "generic" article with the instructions in the "introduction" article.

Thank you so much for posting this workaround.  I'm having trouble with the following step:

If you create the apps/ws folder as nt folder, you can't copy that file over.  So When I redid this I made the folder a sling folder which mimics the /libs/ws folder.

How do I make it a sling folder?  I assume that I need to change the jcr:primaryType property, but I don't see how to do that.  Thanks.

We will log a bug on this doc based on your comments.

Ok I sort of answered my own question.

Adobe Experience Manager Help | Generic steps for AEM Forms workspace customization

Here's what I had to do differently:

I noticed in the error page it kept wanting the index file.

In  Step 10, you're asked to point to an index file.

<meta http-equiv="refresh" content="0;URL='/lc/apps/ws/index.html'" />

But it never asks you to actually copy the index file from libs/ws and you're never asked to create one.     If you create the apps/ws folder as nt folder, you can't copy that file over.  So When I redid this I made the folder a sling folder which mimics the /libs/ws folder.

As an extra precaution I logged out then restarted JBoss.

Once I did that, I was able to  get to the page. 

The steps should be straight forward but I just feel like they miss some nuanced steps to make it work as expected.  In all, 10 tries to get this to work.