Hello jeretjordan and welcome to the Monastery.

I didn't mean to break any guidelines.

No worries - that's why we're linking you to the nodes that give tips on how to best ask questions. The better questions you ask, the faster and better we'll be able to help :-)

I was just looking for some general directions as I am just crawling through the dark with this right now.

"Code review" type questions are ok, I'd just suggest that you clearly label them as such. Otherwise, people will assume you just dumped a bunch of code on us, which is generally not considered polite, since it makes it look like you expect others to spend their free time going through a bunch of code that's not relevant to the problem.

If you have specific problems, then as the others have been saying, the best way to go about asking for help is to reduce the code down to just the bare minimum needed for others to reproduce the problem (including runnable code, short example input, expected output for that input, and actual output including any error messages). In this regard, Short, Self-Contained, Correct Example is a good read. Narrowing down the code to only that portion which shows the problem not only helps us in providing you faster and better help, it often will help you see the bug more clearly. Also, it's important to Use strict and warnings, since they will help avoid some obvious mistakes. Two more very good reads are the Basic debugging checklist to help you locate the issue, and How do I post a question effectively?