Building a heirarchy of reference code

[Former Member]

Some of my friends keep asking me to share code.  I thought what better than SCN.  But how to do it.  One possibility that strikes me is a group of "Documents" joined by links in a "BLOG".  But I'm too new to know that this will be a good idea.  I've got to make my code generic and well documented.  So, I don't have everything on hand.  It would be generated over time. Will the BLOG stay modifiable for years?

Please tell me what you think the best answer is?

Neal Wilhite

[former_member182521 · Accepted solution]

To startup with blog

http://scn.sap.com/community/about/blog/2013/06/13/build-a-better-blog-step-1-tell-the-story-you-wan...

[JasonLax]

Hi Neal,

Blog posts are where you express your point of view or share your thoughts on something. They are timely and aren't meant to be continuously updated.  In your case, you'd publish a blog to let the community about your documents while providing an overview on why you created them and how they can be used (background info, etc.).

A master document would be more suitable to list the links to the other documents. It can be updated continuously and even shows the date it was lasted edited in the masthead.

Jason