The perfect choice of one-stop service for diversification of architecture.
So I am thinking of a possible answer to my own question:Build my own journal note entry app linked to a wiki.Zim Wiki uses a file based system for wiki. Maybe I could write app to export/sync entries in its files. Or WikkaWikki uses a MySQL (which is probably what I would use for journal entries anyway) so perhaps use same DB for Wiki and journal, with Journal app "doing right thing" to enter/sync Entries in wiki.Does this seem like a good approach?Or maybe I can customize a wiki with existing plugins - "All" I really need is good journaling / date feature, time tracking, checklist, and tags. Perhaps there already are plugins for this?Please comment if you have feedback on this idea.
1. Circular tag wiki excerpts
Tag excerpts should at least try and give a concise definition as to the subject, and provided any usage guidance if necessary.Therefore, you need to make sure to address a set of key points:In general, excerpts should provide at least some guidance, even if it may appear to be ridiculously basic. Therefore, interpretation of the rejection reason is critical:That's like saying, [abs]: For questions about [abs] filaments. That should probably be rejected. This is better: [abs]: For questions about [abs] filaments - filaments that are used with blah blah printers, and are not toxic for use.Or even better: [abs]: For questions about [abs] filaments - filaments that are used with blah blah printers, and are not toxic for use. Not to be confused with [pla] filaments. Do not use this tag if your question does not concern this filament specifically. Obviously, I have no idea if abs is even a thing. Anyways, I hope this helps :)
2. Why is this answer a community wiki?
Apparently the answer under scrutiny was made CW because it drew on an answer from another Stack site, and the answerer wanted to share it without being associated with it for good or for ill.But community wiki is not a tool for reputation denial (or for dodging the repercussions of questionable-quality answers) and practically speaking I see no difference between quoting a different Stack and quoting a blog or a book. We would never expect someone to eschew rep for quoting a blog or a book. The answerer went to the trouble of tracking down the information and sharing it; why should not rep gains should reflect that?The moderation team is under no obligation to revert the CW in this case, nor are they obligated to leave it be, but I would lean toward reverting it myself, for reasons which follow.We've talked about posting answers from other sites, and it's pretty clear this is not cheese.Community wiki used to be massively overused. Changes to the editing system rendered its original purpose largely moot, and there's now a lot of confusion about CW's role in the Stack mechanics. These days there are three basic reasons to use CW:I do not see this particular answer needing CW to make it "easier to edit and maintain by a wider group of users," so I do not see any reason for it to be a community wiki. Community wiki is a tool with a specific set of uses, and CW rollbacks are left to mod discretion. One of the responsibilities of our moderators is to help the community use the right tools for the job at hand.As for the answer itself--it's not very good by lit.se standards, because it was written for a different site with different priorities. And the question itself is under a tag whose implementation is still being debated, so quality there is... in flux, I suppose we could say. We need to bring in our own expertise and tailor the answer to meet the expectations of our own Stack.
3. Need to Change Edit Approval Limits for Tag Wiki Editors
I just upped it from 3 to 5. Hopefully this alleviates the issue a bit. If we still notice a pattern of users being blocked we can look at adjusting further
4. Difference between Wiki Library and Document Library
Yes there is difference, Below might be helpful to understand.Document library can contains documents, it can be any document like office documetnts doc,xls,ppt, js, css, jpg, png etc...any file extension you can think of. Main purpose of document library is to store documents. wiki library is a kind of document library which contains wiki pages, Wiki pages are html pages with rich text editing capabilities so that users can create pages using Rich Text Editor without knowing html in detail. So when wiki library template is selected it comes with some default columns created based on content type, this columns are useful to create wiki page. Making changes and edits in a wiki page is incredibly easy. Just click on the edit button (at the top of the page) and immediately the page appears as an editor's version of the page. You can then make edits straight away and simply hit save. The page will instantly be up and running with your changes in place.