On May 8, 2015, at 9:43 AM, Hitesh Sofat <sofathit...@gmail.com> wrote:
>> That might be possible with some URL rewriting but handling everything >> through Special: means mediawiki is not aware of that content (so it’s not >> searchable, editable, etc). Is it possible to close that gap as an >> extension (or set of extensions)? > > I have added the search feature please check. > > http://202.164.53.122/~hitesh/media/index.php/Special:Docbook_Search This looks fine, but I think you misunderstand. First, that’s not searching — that is a drop-down index/catalog/menu. Searching example might be to look for all of the different documents that reference a particular word or set of words like “colormap index”. The problem was that using the top-right main search box doesn’t work: http://202.164.53.122/~hitesh/media/index.php?search=rtexample&title=Special%3ASearch&go=Go A person visiting the site has a reasonable expectation that if we provide a search box, it will search our content including this documentation, no? We could rely on a generic Google site: search field, which will span the mediawiki content too, so searching in itself isn’t an insurmountable problem. Still, lets not get distracted! The underlying point was that mediawiki is not aware of the content. This affects a whole host of issues and searching is just one of them. I think a different approach is needed. It probably needs to either be a content extension like one of these: https://www.mediawiki.org/wiki/Category:File_system_content_extensions OR an import approach like one of these (examples for mediawiki and wordpress): http://wiki.blender.org/index.php/Meta:Tools/Wiki_conversions/DocBook_to_Wiki https://www.mediawiki.org/wiki/Extension:Html2Wiki https://wordpress.org/plugins/wp-all-import/ https://wordpress.org/plugins/import-html-pages/ OR a custom back-end thing that just happens to work with WP or MW. There are SO many possibilities, but I think the central problem is going to be editing. If you remember from my earlier e-mail, the priority is: 1) publishing our docbook docs online, 2) allowing those documents to be edited online or directly in the repo, and 3) having any committed edits automatically reflected/republished online. Anything else (like searching and navigation) is secondary and could be done after those are robust. Getting #1 is trivial. Even #3 is half-trivial. Figure out how to support editing, then you can build a publishing and republishing process around it accordingly. This will necessarily be direct editing of Docbook XML or editing of some other format (MANY possibilities) that will convert to/from Docbook XML (being limited to a subset of tags is okay!). Cheers! Sean ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ BRL-CAD Developer mailing list brlcad-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/brlcad-devel
