IssueBlogIt was an idea that came to me a while back. I needed a place where I could log issues that I’ve encountered with technology. Whether it is something I encountered professionally at work, or personally on a project, I wanted to be able to log all of the issues I came across and eventually provide and archive the solution I’ve uncovered.
By the time I finally got around to putting together this site, the idea grew slightly. As I wanted the site to behave like a product backlog (used in Scrum methodology), I realized this would be a great opportunity for me to allow the site to act more as a forum to any issues that any visitor might have (within reason of course). Although I would like the focus of the topics to be mainly around issues with technology, web development, application development, and design, I invite all to IssueBlog whatever is on their mind. I will ultimately filter the requests, but if it is deemed worthy, it will be made public for all to comment on and provide feedback and solutions.
How It Works
How it works is simple. Simply Submit an IssueBlog to get started. All you really need to get started is to provide your name, email, and overall summary of the issue. From there the request will go to firstname.lastname@example.org for review. Upon approval you’ll be notified that your request has been accepted and you’ll be sent a link to the latest posted IssueBlog you’ve submitted.
All IssueBlog topics will be tagged with at least one of two categories. When an IssueBlog is initially submitted, it will be tagged as Unresolved. Once the issue has been fully addressed it will be marked Resolved