Osin, If this were my project I would need to take account of the way the data is formatted in the spreadsheet, perhaps making an additional worksheet in excel that complies with one row per faq. Then export this as a CSV file, using JSON Mangler, in a utility wiki, to import and convert to tiddlers (In a plugin package) then transfer this plugin package to the new faq TW5. I would then build a view template for viewing both the previous shadow faq's and new ones I create going forward. If you want to modify an old FAQ you just edit the shadow to become a tiddler.
I would set a field such as object-type to faq in the faq tiddlers so I can always list them, I would try and retain dates from the original faq as it can help with data currency eg a really OLD faq may have aged. However you most likely need to reformat the dates found in the spreadsheet. If you are carful with you design you may even be able to retain the ability to export faq back to csv and import to the Spreadsheet. This would be a lot of effort and depends on how they are currently stored, however it may smooth the adoption of a new solution. I think tiddlywiki is ideal for this kind of business requirement. Especially with one editor and many readers. An over dependence on organically developed spreadsheets is common, they are fragile, and often become hard to maintain when the author leaves. Unless they have media images, audio and video you can store many thousands of faq's in one tiddlywiki. I would explain it as using a special smart document, that is published like a website and provides a managed user interface to the FAQ's for both readers and editors including search and categories etc... later it can be used to extract more knowledge from the FAQ's, provision answers for different users and much more. Do you have SharePoint available? regrads Tones On Tuesday, 10 November 2020 03:47:38 UTC+11, Osin wrote: > > I found this page <http://sukima.github.io/GitFixUm/> that is somewhat of > an FAQ that could become useful. > When you say "'question field' for the full question", are you referring > to the "add a new field" option at the bottom of every tiddler? I will dig > into this more. > > Re: IE, yeah, no one has much say, it's a very tight and regulated > workplace with old tools. I initially considered TWC because I could always > convert into TW5, but so far TW5 works. Drift doesn't, for example, which > is why I don't want to use plugins and stray away too much from vanilla TW5. > > On Monday, November 9, 2020 at 10:37:11 AM UTC-5 Mark S. wrote: > >> Side note. I believe MS will be retiring IE next year. Designing anything >> around it would be counter-productive. >> >> >> On Monday, November 9, 2020 at 7:29:01 AM UTC-8, Mark S. wrote: >>> >>> I would use the title for a short question, the text field for the full >>> answer, and a "question" field for the full question. A view template for >>> the item would allow the user to see as little or as much as they wanted of >>> the answer. Every tiddler would be tagged as "FAQ" and then tagged with >>> sub-topics. You create a tag tree and then use one of the TOC macros to >>> display the entire FAQ. >>> >>> That's a whirlwind answer. I'm sure someone will come up with an >>> all-singing, all-dancing FAQ. >>> >>> >>>> -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/f010442b-065d-4baf-af34-900c39c1dcb8o%40googlegroups.com.
