Corrupt web page http://mojomojo.org/features
I'm not sure where to report this...
The features page of the website has been hacked. It contains some gibberish, and at least one link (Dr Susan Lim Singapore) that tries to download malware.
I'm not sure where to report this...
The features page of the website has been hacked. It contains some gibberish, and at least one link (Dr Susan Lim Singapore) that tries to download malware.
I would like to see a built-in spell checker. Either initiated by one of the "Save" buttons or dynamically as the page content is updated. Correction capabilities wouldn't be needed.
better documentation for rookies looking into learning mojomojo and catalyst together?
would make it easier for rookies to start working with mojomojo
MediaWiki has those. Probably easiest implemented via JavaScript. http://en.wikipedia.org/wiki/Comparison_of_programming_languages
Give MojoMojo a CPAN like distribution tarball like My-Class-2.0.tgz and MojoMojo would slurp that in (e.g. with Archive::Tar) to display a overview page from META.yml and links to the POD or source of each module file which is mentioned in MANIFEST. This would help projects to develop Perl Apps or prepare modules for CPAN. MojoMojo can already display POD and Perl source nicely!
Memcache Support, for db queries and possibly sessions.
Enable anonymous commenting on page. Authenticated/verified by CAPTCHA.
I noticed new user's page were created at the root of the hierarchy on mojomojo.org WIBNIF they were created below a users page. I'm a newbie here so this is probably already supported...
Even for a private Wiki one can get, say, users' list with a series of
`/.jsrpc/usersearch?q=' requests.
Calendar that any approved user could add events to.
When you are creating a hierarchy of pages, it would be quite useful to have a {subpages} option similar to {toc} that lists the subpages of the current page (perhaps in a ul, or other list form)
If you could do {subpages 1} you could create just the 'next level of detail' where {subpages 1-} or some such could generate a site map type thing that would stay up to date.
In wiki pages with dynamic content (e.g. http://wiki.dandascalescu.com/howtos/catalyst/introduction_to_catalyst.edit), it may become annoying for said content to keep refreshing as the user types. A toggle for live preview, on by default, would be nice. Ideal level of persistency would be per page because some pages are dynamic-content heavy and others are not. Per-user persistency (one user thinks the page is "heavy", ...more »
In wiki pages with dynamic content (e.g. http://wiki.dandascalescu.com/howtos/catalyst/introduction_to_catalyst.edit), it may become annoying for said content to keep refreshing as the user types.
A toggle for live preview, on by default, would be nice. Ideal level of persistency would be per page because some pages are dynamic-content heavy and others are not.
Per-user persistency (one user thinks the page is "heavy", another one not) would be overkill. Besides, the "heaviness" can be thought of as an attribute of the wiki, as a sentence saying "This is is a heavy page", which the other user deletes.
« less full details »
"WikiCreole is an attempt to develop a set of good practices and recommendations about markup languages for creators of wiki engines. It is also a set of basic markup rules commonly needed in such languages."
-- http://wiki.wikicreole.org/About
The WikiCreole 1.0 spec is stable: http://wikicreole.org/wiki/Home
Then, add MojoMojo to wikicreole.org /Engines and /Wikis.
Wouldn't it be great if people actually could install this software?
AJAX to do list, or some kind of task list than can occur multiple times per page
Keep attachments when they are deleted; just mark them as absent
Allow one to override the URL title with a title of their own.
Search and Replace Feature when Editing Pages.
You can already use the cascading permission system to allow stewardship of certain topics. It'd be nice to allow anyone to submit an edit, but to have the steward/admin review it before it becomes public and approve/deny it. This would allow a much more functional wiki and would support much higher quality wiki content. It would also make MojoMojo much more useful as an organizational document system, as different ...more »
You can already use the cascading permission system to allow stewardship of certain topics.
It'd be nice to allow anyone to submit an edit, but to have the steward/admin review it before it becomes public and approve/deny it.
This would allow a much more functional wiki and would support much higher quality wiki content.
It would also make MojoMojo much more useful as an organizational document system, as different groups / departments could manage their own information / keep control of it, but still allow information to be added with review)
« less full details »
LDAP authentication/roles for users would be quite useful, especially in environments where we already have a known set of users (e.g. internal to an organization).
Kill multiple slashes slashes that show up in URL's like /wiki///mama/mia
Social Web