Thread

Before we begin building the rest of our templates, what we’ll want to do is take a deep breath and think about our Bug Tracker’s structure. 

In my experience there are two ways to approach this:

1. Plan out the navigation, then build your structure according to that or,
2. Build the structure, then figure out how to create navigation that makes sense.

A Bug Tracker is a fairly specific application that has straightforward needs.  As we’re using a simple template, with only a left menu, we can already see that navigation needs be simple and easy to use. 

This particular article is going to hint at some of the upcoming features of the Bug Tracker, since we’re going to add some links right now.

Onwards!

Hi Lisa, thanks for keeping this going.
Do you have a working version demo, just with what you’ve got so far and the nav.
The nav would be the perfect chance to fancy up the design for anyone following along to do a little D & D (Design and Development - acronym for the day) 😉

I have a working demo - on localhost. It’s not available for public consumption.  In reality, we’re not even at the point where it would do much, anyway. I’m working through the tutorial as we build it. =)

I would recommend “fancying up” for after the tutorial, in case someone does have a problem - troubleshooting from the known code will be much easier and faster to keep the tutorial following on track. =)

OK thanks for the recommendation of waiting on the design bits then.
I thought you might be all for it, but makes better sense to wait, and to troubleshoot any problems code problems, errors, bugs… Debugging the bug tracker, it should practically debug itself, lol.
Thanks again Lisa.

Well also remember some of those direct links won’t remain direct links, and may effect your design decisions after they’re changed.  You can fiddle if you want, it’s just a recommendation. =)

Hi Lisa! Great demonstration of EE at work.

Just as I’m needing to learn how to do this, there’s a tutorial available. Keep up the good work!