About Us

History

Hi, my name is Sandi Laufenberg. I am the lead developer at LadySword Productions, which is based in the Madison, Wisconsin, area. I started LadySword Productions in 1998. In 2004, LadySword became part of The Winner's Way, Inc. Then, in 2014, we became a division of YHWH Is Our Rock, Inc.

Bragging is not really my forte', nor my hobby---but this would be the time to do it, I guess... So let me say that formerly, as a freelancer, I had produced hundreds of artistic AND awesome webpages, rendered hundreds of graphics, and created many databases. However - things just got better and better for LadySword. You see, over the years we have grown in our connections and associations. This network of professionals make up "our team". And now -- though I myself can't do everything -- OUR TEAM CAN.

More info and my resume links can be found here.


Dedicated to Excellent Service


LadySword Productions has an excellent team of associate programmers. Their combined talents CAN DO ALMOST EVERYTHING. No lie. 

Our network is made up of a number of excellent IT professionals.  Whether you need a brand new website -- a new or improved database -- or -- a programming fix, you have come to the RIGHT place!

With LadySword Productions, you will get fantastic results -- that is my personal promise to you.



Future Goals

  • We are looking to constantly improve upon our services and our systems.
  • Working to expand and improve the resources we offer to the public through our website. 
  • Plans for the future: 
    • More free articles and information.
    • Increasing the availability of economical business solutions without sacrificing quality.
    • In general - helping the Internet to become a better resource for all.

So.... if you don't see what you need on our site -- please don't hesitate to ask... or make a suggestion.  We'd love to hear from you.

With our network of professionals --- the sky is the limit !!


- Sandi Laufenberg

 

 

Article ID 14

 

About Us

About Us

{ some content }

 

 

Article ID 131

8 Tips to Good Wizard Design

Use a wizard when you have a situation where the user wants to achieve a single goal which consists of multiple dependable sub-tasks.
Example:


Enlarge Image

The wizard used to get an insurance quote at homesite.com uses a highlighted tab in the menu to communicate the purpose of the wizard, uses a good default pattern for selecting options, has a clear communication of the wizard length as well as how far the user has gone, uses large navigation buttons, has all its content above the fold, and provides a nice alternative to the wizard by letting the user talk to a real-life person for assistance.
 


Usage:

  • Use when the user needs to perform a task or a goal that dictates more than one step. An example is adding an image to a website which can include uploading the image and cropping the image; the image cannot be cropped before it is uploaded to a server.
  • Use when the user needs to perform a complex task consisting of several dependable sub-tasks.
  • Use when the user needs to input complex data into a system that is easier for the user to comprehend parting the process into multiple steps.
  • Use when the user needs guidance: the user wants to achieve an overall goal, but may not be familiar in the steps needed to reach the goal.
  • Use when the steps needed to reach a final goal may vary due to decisions made in previous stages.
  • Use when the user lacks necessary domain knowledge.
  • Use when the user must complete steps in a specific sequence.


Other Tips to Good Wizard Design:

1. Keep the purpose clear: explain
2. Use plain language
3. Summarize choices
4. Good defaults
5. Minimum of training
6. Keep the amount of screens low
7. Be careful not to make each step too long
8. Allow alternatives to using the wizard

Read More >> Click Here to jump to the whole article. Thanks to UI Patterns for their article, "Wizards".

 

Get a FREE consultation.

 

 

Article ID 91

Check Out the Portfolio


Strict Standards: Non-static method PhocaGalleryLibrary::getLibrary() should not be called statically in /home/f35d185/public_html/main2/modules/mod_phocagallery_image/mod_phocagallery_image.php on line 35

Strict Standards: Non-static method PhocaGalleryLibrary::getInstance() should not be called statically in /home/f35d185/public_html/main2/administrator/components/com_phocagallery/libraries/phocagallery/library/library.php on line 44

Strict Standards: Non-static method PhocaGalleryPath::getPath() should not be called statically in /home/f35d185/public_html/main2/modules/mod_phocagallery_image/mod_phocagallery_image.php on line 36

Strict Standards: Non-static method PhocaGalleryPath::getInstance() should not be called statically in /home/f35d185/public_html/main2/administrator/components/com_phocagallery/libraries/phocagallery/path/path.php on line 50

Strict Standards: Non-static method PhocaGalleryRenderFront::renderAllCSS() should not be called statically in /home/f35d185/public_html/main2/modules/mod_phocagallery_image/mod_phocagallery_image.php on line 43

Strict Standards: Non-static method PhocaGalleryFile::getCSSPath() should not be called statically in /home/f35d185/public_html/main2/administrator/components/com_phocagallery/libraries/phocagallery/render/renderfront.php on line 731

Strict Standards: Non-static method PhocaGalleryPath::getPath() should not be called statically in /home/f35d185/public_html/main2/administrator/components/com_phocagallery/libraries/phocagallery/file/file.php on line 154

Strict Standards: Non-static method PhocaGalleryPath::getInstance() should not be called statically in /home/f35d185/public_html/main2/administrator/components/com_phocagallery/libraries/phocagallery/path/path.php on line 50

Strict Standards: Non-static method PhocaGalleryFile::getCSSPath() should not be called statically in /home/f35d185/public_html/main2/administrator/components/com_phocagallery/libraries/phocagallery/render/renderfront.php on line 731

Strict Standards: Non-static method PhocaGalleryPath::getPath() should not be called statically in /home/f35d185/public_html/main2/administrator/components/com_phocagallery/libraries/phocagallery/file/file.php on line 154

Strict Standards: Non-static method PhocaGalleryPath::getInstance() should not be called statically in /home/f35d185/public_html/main2/administrator/components/com_phocagallery/libraries/phocagallery/path/path.php on line 50

Strict Standards: Non-static method PhocaGalleryFile::getCSSPath() should not be called statically in /home/f35d185/public_html/main2/administrator/components/com_phocagallery/libraries/phocagallery/render/renderfront.php on line 731

Strict Standards: Non-static method PhocaGalleryPath::getPath() should not be called statically in /home/f35d185/public_html/main2/administrator/components/com_phocagallery/libraries/phocagallery/file/file.php on line 154

Strict Standards: Non-static method PhocaGalleryPath::getInstance() should not be called statically in /home/f35d185/public_html/main2/administrator/components/com_phocagallery/libraries/phocagallery/path/path.php on line 50

Strict Standards: Non-static method PhocaGalleryAccess::getUserRight() should not be called statically in /home/f35d185/public_html/main2/modules/mod_phocagallery_image/mod_phocagallery_image.php on line 635

Strict Standards: Non-static method PhocaGalleryOrdering::getOrderingString() should not be called statically in /home/f35d185/public_html/main2/modules/mod_phocagallery_image/mod_phocagallery_image.php on line 663
facebook