Check out this new
NetSuite Implementation that I just completed. This ones seems simple, but actually end up being pretty complex. It uses a right hand column across 95% of the pages, I did it using tag substitution. Then the headers rotate based on the page, iframed contact forms and custom NetSuite Item template. Wow, the NetSuite Implementation gets better and better. Getcha sum with
Save Phace.
I finally made it to 100% of space used in my gmail. I guess too many PSDs being sent back and forth. I just thought they would keep giving me more space. Guess that was a rumor, because after I made it over 2731 MB they wouldn't let me send email anymore. Booohhh!
---------------------------------------------------------

NetSuite 11 has some really cool features for accounting, shipping, web store and ect, but what I like the most is the fact that they added (an option to have) a DIV tag wrapper around the main table of the code. This opens up the door to using a lot more xHTML and CSS with NetSuite 11.
For example, this
Oil Analysis Software store is using a border around the entire template. But because NetSuite using SOOOOO many HTML tables in the code it was impossible to create this effect. Now that DIV #outerwrapper was a great enhancement.
Now if they can just clean their code a little more, the
NetSuite Search Engine Optimization wouldn't be so difficult. If your listening, here are some suggestions.
- Remove that big block JavaScript (errortextheading) message at the top of all the source code.
- Put ALL JavaScript in external files
- Remove the nested table, at least some of they. Code is nasty
- Remove the empty divs, like #div_label and #div_title. They are barely used
- Remove the additional URL variables that are always attached to unique visits. That ;jsessionid= is really not good for SEO. Plus ugly and long, See how long these variables are below. I even shortened it cuz didnt fit in my blog.
jsessionid=ac112b1d1f436068e93c0099409fa8f280173540df13.e3iKaNePch4Re3mPaNiMbh8Sc41ynk
Thats right, I'm very sensitive about how the code looks :-) ... I understand why the tables are there... to keep the layouts from breaking. But a little more flexibility to clean up the SOURCE CODE would be very helpful.