On Sun, May 3, 2009 at 6:56 AM, dlypka <[email protected]> wrote: > > I wish the wiki used the WYSIWYG HTML control for content entry a la > T3 instead of the text mode with python doc tags. > And then I think an XSL transform should be used to strip out the tags > to store a parallel copy of the content that is a pure text 'blob' > and then that text blob need to be run through some sort of full text > search preparation process which would identify keywords and insert > them into an index. > Each page would have one parallel text blob. The full text search > could search the blobs using the index, and return the corresponding > page links where matching text was found.
Thanks for your comments. At this point, I think there are 2 tracks to this discussion we could have: - immediate need: what do we need to do to wiki to further community manual creation (we have already decided docutils reStructuredText format, and sphinx document generation - so lets keep the discussion within these parameters for this part; - Long term: how do we make a "best in class" wiki appliance for web2py (which could include the above, but much more) > > > On May 3, 3:50 am, Joe Barnhart <[email protected]> wrote: > > Yarko -- > > > > I can't say about others, but for me the key missing features in the > > wiki are: > > > > * Wiki-style links and organization > > * Easy navigable URLs > > * More compact and usable layout > > > > All wikis I have used in the past use embedded WikiStyleTags to create > > links to other pages on the wiki, or even create stub pages > > automatically. Ours does not. It's linking is very cumbersome and > > more like a traditional web page. > > > > URLs in most wikis are related to the linked pages, so the page above > > might have a link ofhttp://www.ourwiki.com/wikistyletags. It makes > > the page easily reachable and much more accessible than an > > automatically generated crypto-garf name. > > > > The layout of the current wiki is very large and diffuse. It feature > > enormous titles, big fonts, and just does not use space efficiently. > > I know it's a style thing, but style is important too. This is less > > important than the wiki features already mentioned, but it ranks > > somewhere. > > > > I don't want anyone to feel like I'm telling them what to do. I am > > just a messenger, bearing the bad news that we still do not have > > significant community involvement in solving our documentation > > dilemma. While I am becoming more proficient at reading Python ;-), I > > believe we need more accessible documentation if we are ever to take > > on Django or PHP. > > > > On May 2, 2:44 pm, Yarko Tymciurak <[email protected]> wrote: > > > > > > > > > talk is cheap... > > > > > ...there is no shortage of opinions or advice on what "others should > do", or > > > (worse) what "others should stop doing" (as I read this all)...- Hide > quoted text - > > > > - Show quoted text - > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
