Tech Write Up Idea

[7991LXnSHO]

It would be awesome if jrichker's tech write ups were all in one easy to get to location. I have printed many and have them in a binder. I have found them more helpful than my Chiltons manual and even the kid tech appreciated it when I could not do the work.
How about a sticky list that links to them? There is another section on resources that would be a good place too. So moderators and guru j, what do you think? We could refer folks to look there first and get back with more info if they still need help.

 

[madspeed]

I like this idea @Noobz347. Should they be converted/posted as a resource?

 

[Grabbin' Asphalt]

Cha ching!! ...A personal binder would be golden too

 

[Noobz347]

I've spoken with @jrichker about this very thing. I think it's just a matter of he and I getting the time to build the resources.

 

[madspeed]

excellent

 

[HISSIN50]

A consideration for this great idea would be to have the links connected to the organic source, so that as he updates or revises a given tech note, the link takes one to that most recent version.

 

[84Ttop]

I'm excited for this idea as well!

 

[Noobz347]

A consideration for this great idea would be to have the links connected to the organic source, so that as he updates or revises a given tech note, the link takes one to that most recent version.

Yes... this is a HUGE feature of the resource although I'm not completely enamored with how the linear updates are handled.

The resource system wasn't really intended for what we'd like to use it for but it does function very well. There's been a couple of work arounds that have made it function much better for our purposes.

 

[jrichker]

The two problems arising out of a resource library are:
1.) The fact that many new users often don't have a clue as to what their real problem is or how to find the resource library if they do know. They may get disillusioned by just telling them "Go see the Resource Library document ".

Example:
http://www.stangnet.com/mustang-forums/threads/egr-code-33-easiest-fix.874130/#post-8787647

90lxwhite said: ↑
Seems the reg solenoid is ez. Oh n its never personal /jrichker, always a form letter.

My reply:

You're obliviously not rich, famous, or a beautiful lady in distress. So you don't qualify for a personally crafted exposition of how to fix your problem...

_____________________________________________________________

2.) The updating of resource library documents. Most my own Help & How to documents have the Revised date and revision description in them. This helps keep track of the changes, and is an aid to those who may have saved an older copy of the document. In order to make a Resource Library work well, a standard header format should be used to keep track of changes and date. Everyone needs to use the same header format in order to make a workable system.

 

[Noobz347]

The two problems arising out of a resource library are:
1.) The fact that many new users often don't have a clue as to what their real problem is or how to find the resource library if they do know. They may get disillusioned by just telling them "Go see the Resource Library document ".

Example:
http://www.stangnet.com/mustang-forums/threads/egr-code-33-easiest-fix.874130/#post-8787647

90lxwhite said: ↑
Seems the reg solenoid is ez. Oh n its never personal /jrichker, always a form letter.

My reply:

You're obliviously not rich, famous, or a beautiful lady in distress. So you don't qualify for a personally crafted exposition of how to fix your problem...

_____________________________________________________________

2.) The updating of resource library documents. Most my own Help & How to documents have the Revised date and revision description in them. This helps keep track of the changes, and is an aid to those who may have saved an older copy of the document. In order to make a Resource Library work well, a standard header format should be used to keep track of changes and date. Everyone needs to use the same header format in order to make a workable system.

You can post the resource links in t the threads that you visit just like you're doing already.

Updates keep track of themselves in the resource library. There's even version numbers that you can use if you choose. When the link is visited (regardless of how old the thread is), it doesn't show an archived version. It shows the most up to date version. What's more is that you can also have downloadable attachments if you choose as well.

 

[Gearbanger 101]

I started revamping the Technical Thread/How to index this pas fall to include more articles, update old ones and make the layout mor fluid, but life and obligation has slowed my progress some. I'll be back at her hard this spring....just in time for everyone to get their cars out of their winter mothballs.