location of XHTML and CSS store files?

In terms of using all my Super Suite extensions to jazz up the PowerStore "entry" page:
(1) do defaults exist, and where?;
(2) if not, where should they go?

When I login to my installed PowerStore3, it sends me to <https://www.antimall.org/antiMall/PowerStore300/Admin/index.php> which, in turn, upon correctly logging in, sends me to <https://www.antimall.org/antiMall/PowerStore300/Admin/home.php>.

As admin, going to "home.php" is where I want to go.
For a user, I presume I tweak the "index.php" file to allow registration or entry if registered and correctly logging in?
I want my customer entry point at <https://www.antimall.org/index.php>
Would you suggest creating my registered entry page there and keeping my same admin location, or combining the two?
If I am using some "template" entry page, is this where you suggest putting it?
I'm a bit surprised that this part of the store software doesn't have defaults built in.
Are there any instructions for coordinating these "look-and-feel" files with the default PW3 files, i.e., ones that define the key files , their locations and functions?

Thanks,
chris

I'm not sure what you mean by defaults. Do you mean modifying the look and feel if there are any default templates to use? If that's what you mean, there isn't any additional templates provided to skin the store with currently.

The "entry" page is the index.php file. If you wanted the url for entry to be index.php, you could have an index.php page in the root of your server that will forward to the current location that the index.php is located (index.php) or you would have to reinstall all the PowerStore files in the root of your server. Basically all the files contained in the PowerStore300 directory would have to be copied to the root of your server and installed from there.

Jimmy:

First off, I apologize for not responding sooner. I have "instant notification" checked and never received ANY notification, let alone "instant". So, sorry about that, and thanks for responding.

Here is what I want to accomplish:
1) I have one dedicated ipAddress for my antiMall.org domain.
That is where I installed PowerStore3.
2) It has three domains that share its ipAddress which are the stores, each with their own databased products and store "look-and-feel".
3) All stores will use the same shopping cart, customer registration/authentication, payment authorization, and check-out.
4) So, the mall is "common" and the stores are distinct in how their web pages look. When you "walk" into a store, the CSS/XHTML will make it look different than the common mall and other two stores. What is available is only available in that store. You select an item or two, take your cart out into the mall again, and either check out or go into another store with that same cart. make sense?

So, I need to know how to install PowerStore and my Super Suite extensions, and where, such that I can share the common pieces and also make unique the store "ambiance" and availed products.

I despise stores that have everything in them competing for your eye; they're confusing and demeaning. Each store has a theme, like a restaurant would have.

Do I need to setup Powerstore3-accessible databases for each store and have what database is being looked at depending on which store is entered?

I could still use the same registration and shopping cart until that user logs out, right?

So, how do I distinguish a single store, and where?

Right now I log in as admin only.
It's setting up a test user that I need to let go into 2 stores, each with its own database (or section of a database) with one cart.

I need to know what pieces/modules are affected, where they reside, and what code to look for.

I see no code documentation, no module descriptions, no variable descriptions. Where is that basic code documentation kept or what would you suggest for mapping module data flow?

I need to map what may not be mapped. It's going to be very helpful to know system integration of modules, and what goes on inside the modules I am dealing with. At Intel, Mentor Graphivcs, and Network General, every module had a header that could be accessed. Maybe I can run a script to grab those headers so I can discover the info? Suggestions are very much appreciated.

Thanks Jimmy!

best wishes,
chris

The way that you have described you would like to set PowerStore up like sounds like it would be possible but it will be a custom endeavor. The store was not designed to work like this and we do not offer the fundamental documentation about how it all works that you are requesting. Getting this solution implemented would require you to customize how these things work together. I would suggest that you start on this project with a single store, then using the same db you can try to incorporate your other versions with their products.

Where is the documentation which describes what each module does, what each variable does, etc.?
This is basic software engineering to supply that information.
It is in IEEE, ISO, CMM, and all best practices documentation.
If I can see how the core modules interact then I can understand where I will have to focus for my method.

For a single store this should be available. Where is it?!
If I am being told that I have to draw my own data flow and walk through all of your code to find out the I/O and interactions, I will be very disappointed.
"Software" should all have internal documentation as well as a User's Guide (covering install, configuration, and interflow) and usually also a User's Manual (for descriptions of modules' variables, module interactions, and parameters/IO).
If it does not, then it shouldn't really be called software.

It's like calling something a car that has no steering wheel; without full documentation at the code level, it is not yet really a "product", as "how to use it" is as much a vital and integrated part of it as installation, invocation, input and output.

Adobe's doc is impeccable.

The doc that goes to a user should expand upon what's in the Functional and Design Specifications documents. Good software has trace/debug tools built-in that can be enabled/disabled for users.

Marketing should NEVER be in charge of writing documentation. Good doc is sent out to existing users to see if it helps, and they should be asked what is missing.

I wanted a working product, and it is NOT if doc on how to customize it has to be written by me.

Make sense?

I have bought PowerStore 2 and 3, subscriptions, and Super Suite and see no end in sight... and I am a senior software engineer (Intel, Tektronix, Mentor Graphics, etc.). As a SWQA person, I wouldn't have let this go out the door!

Of course, if I find that this is all available, in some hidden spot, or that I can be compensated for creating the missing doc then I will be more understanding.

This is a sound critique and is not meant to personally attack anyone. maybe the personnel are overtasked. It's all invisible to me. I would work with someone there to create the missing doc if approached. It would solve my problem and would be kind of fun, but I would need some starting point and a guiding hand. Interested?

best wishes,
Chris