Steve Davison
Email: <st WHATEVER eve DOT d DOT dav TRULY is NOT on AT intel DOTT DOT com COM>
We have implemented a wiki system for our entire group that is designed to be a single point of access for all documentation needs.
Subpages
/DeleteMe : What happens when you delete (or create) a page that you are subscribed to. Also, if the source and definition of a move/rename are both subscribed, do you get two notifications?
/EffectiveWikiModel : Discusses the mindset and processes that will result in the most effective wiki site.
/WYSIWYG page: Keep my markup separate from The Slayer of Well Formatted Markup until I'm convinced...
Links of Interest
Test site for latest MoinMoin alpha version (currently 1.6.0)
To Do
- Documentation/help on configuring interwiki list is rather inadequate
Fix incorrect reference to FarmConfig in HelpOnConfiguration (should be WikiConfig)
Move RecentChanges bug to FeatureRequests, and write shorter request
Document how RecentChanges currently works.
Make HelpOnSearching more helpful concerning regular expressions
Learn about DocBook
Study MoinDev
- Case Sensitivity: pros and cons
- Investigate changed headings model and how to do titles
- Feature request: More smileys, including fixme and/or todo.
- Consistent link syntax...
- Including: too many ways to do the same thing (confusing)
ThemeGuidelines merge/extract?
Don't use HelpOn* for stuff we don't distribute. But feel free to integrate this page into MoinDev/ThemeDevelopment and maybe extract the only historically interesting parts to a subpage there. -- ThomasWaldmann 2007-08-11 04:15:35
Bugs/Feature Requests Filed
Bugs/Requests to be Filed
Weird underline bug: this Underline: should end. FIXED!
- Better statistics
- User list per day
- Page view and edit per user
- Subtract out edits from view stats
- Collapse proximal edits / views to reduce noise
- Most-viewed pages
- least recently viewed pages
Hi Steve; I use Piwic for my statiscs need, bye -- MarcelHäfner 2009-12-23 07:27:58
- Advanced search options
Provide a page that adds these criteria/options (in separate controls for ease of use)
- Edited by user
- viewed by user
- Last edited by
- created by ...
- Date last edited
- Date last viewed
- optional system/help pages
- number of views
- number of edits
- statistics by "recently", or date range
- Ranking (percentile) of edits
- Ranking (percentile) of views
- Page quality, completeness, or user ranking (see maintenance tools, below)
- Limit many (or all) of the other criteria to within certain date ranges
- Search comments in markup? macro names? acl? other markup-type stuff?
- search in edit comments?
- search invisible text or not
- search text from previous revisions (with optional date range)
- search in deleted pages
- search in deleted text (I know that text was somewhere, once... where did it go?)
search edits, not pages
- by content but exclude title matches (exists)
- One word "near" another
- subscribed by
- Owned by
- Others?
- Search result sort (and group) options
- by "relevance" formula. (Huge range of algorithms)
- by date (created, last viewed, last edited)
- by creator
- by page quality/completeness/user ranking
- by title then content matches
- by content matches only
- show exact name match first
Many or all of the above can be implied by the search criteria
- More intuitive search/page lookup
Exact page name matches treated more like Wikipedia. MoinMoin already takes you directly to a page if it is the only match, no matter how many search matches there are. This saves you from having to go to FindPage and using the "Go To Page" option. But wikipedia will also take you to a page if you type in the exact page name in the search box, and gives you the option to see all the search results.
- Alternative to above... Always list exacte page/subpage matches at the top of the search results. This could belong under the Sort options just as easily.
- For title searches, add a link to the bottom of the matches that will perform a content search using the same criteria. Not always useful, but I think more often than not.
- Features to support wiki content quality / freshness
Every page has user-feedback options, allowing tags to be added and subscriber notices to be sent without having to go into the editor.
- Rating (0-5, was helpful, was not helpful)
- Contains errors (with editbox to explain)
- Is incomplete (with editbox)
- Is out of date (with editbox)
General comments (like PageComment macro)
Some support for embedded tags such as ToDo or FixMe. May not be needed, could be convention only
- Recognize that certain pages receive review after each edit.
A selection of "canned" admin reports (or can be defined & saved from Advance Search (above) such as:
- Pages that need attention, sorted by most viewed
- Pages not edited in forever
- Pages marked high-quality and not edited in WAY forever
- Pages marked to be reviewed by a certain date, when that date arrives
- Mark a certain user as owner of pages by regex, or single pages by tag/metadata
- Pages marked for review, by owner.
- Changes not reviewed yet. All changes could be marked for review until you check them off.
- Blame
- Who made changes on this line or in this selected range of text? If the range has a history of multiple edits, have the ability to go back farther in the history.
- Possibly also show deleted text if the place it was deleted from is part of the line/paragraph/selection.
- Make it interactive, so that when you click blame it scans the history and updates a blame cache. Then the page is rendered to look exactly as normal, only contains javascript that brings up blame info. when you click or double-click on a location. No need to show full blame info. for every line (like traditional blame programs) when you're only interested in a small area.
- Icon for URL (globe) displayed in wrong place if link split across lines (in MS i.e. 6, at least)
- Better diff:
- Show more context
- Don't attempt to show character-by-character diffs in differing blocks unless they meet some criteria for being an almost match. it's darned annoying.
- Highlight differences in the rendered page.
Have a Next Diff and Prev Diff button to go through the change history. Group edits together by adjacent changes from the same user that are within a certain time range (6 hr, 12 hr, 24hr ??)
- Algorithm could recognize moves
- Renaming pages should move subscriptions
Renaming a page should definitely move all subpages with it. Links within the renamed branch should be fine without editing, as long as they are relative link (hopefully GUI editor does not mess with those any more)
- Default to followed links to non-existent pages do not look like links to existing pages. VERY ANNOYING. At least document where in the CSS to change that.
Ability to change parser mid-stream without enclosing in {{{ / }}}
- Multiple #acl zones per page, or at least an "#acl-else" part
- Hotkeys
- Edit Screen: Save, Preview, spell-check, Diff
- View Screen: Edit, History(info) page
- Ability to link to attachments on other pages (without resorting to http: link)
- Ability to provide alternate text for every type of link
- Complete control of whether attachment references are shown inline or as links. This may all be possible now, but how to do so is rather inconsistent/confusing.
- Allow "subscribe to trivial changes" to be specified/overridden on a page-by-page basis.
Handy Tools & Links
version
Disappearing stuff
are lot comments! (/* here */ are /* a */ lot /* of */ comments)
Can we....
/* make a
block of
text... */
go away??
(nope. if not closed on the same line, the inline comment can never be closed. Remainder of page disappears. Looks like it applies the opening/closing tags blindly, because the action links at the bottom disappear as well.
Messages
An example of the current Frame parser you can found at http://www.iam-wiki.org -- ReimarBauer 2007-01-23 08:33:44