I agree with Paul, it makes perfect sense to see JSPWiki as a lightweight/free alternative to something like Confluence.
Very similar to how Bugzilla is usually the *starter* bug management tool before investing in something like JIRA Get it showing on here! https://www.google.co.uk/search?q=free+confluence+alternative&gws_rd=cr&ei=Z080WPPmFciCgAbBr4XgDQ On 22 November 2016 at 13:53, Paul Uszak <paul.us...@gmail.com> wrote: > You're kidding, right? > > I've asked this previously but for the newest members, I'll ask again. > What is JSPWiki for? I know that this appears to be banging a drum, but it > is unrealistic to expect large scale uptake of JSPWiki if you can’t decide > what or who it’s for. Picking out and replicating minor features of > successful products seems to be without direction and ultimately > fruitless. Could we be honest with ourselves here? Why are we looking at > features from solutions used by the US Navy, Boeing and Orange? Is it to > compete with them, or to continue a hobby? > > There is a huuuge market opportunity for a simple very low bandwidth wiki > /website solution (I see the two as synonymous). The market space is > virtually uncontested in this area. There are numerous strengths that > JSPWiki has that could be leveraged to dominate in this role. Market > segmentation is key here. Try to provide a solution to a very specific > problem, and do it well. There are thousands of nerds (I use the term > playfully) who'd like a turnkey solution to hosting their own website from > that old box under the table. They struggle with low bandwidth. There are > organisations across the whole of the developing world wanting their own > websites with minimal bandwidth requirements to pass over the mobile > network. There is now probably more mobile (low bandwidth) coverage in > Africa than hard wired. Pick a market segment and make it your own. > That's the route to success. “Whatever you are, be a good one” > > On the specifics of Metalsmith and as a user of JSPWiki, I vote no. Why > rip out the heart of what already kinda works, to replace it with a static > meta data driven tool? Don’t forget that static web sites are just a fad > like the old thick /thin client-server debate. It’ll pass so just stick > with what you know. The technology is not the issue here. That’s just > simple code. The vision is the issue. > JSPWiki doesn’t have to copy. JSPWiki could lead. > > On 21 November 2016 at 19:43, Dave Koelmeyer < > dave.koelme...@davekoelmeyer.co.nz> wrote: > > > Nuxeo is a major open source enterprise documentation management system > > product. Their developer team recently migrated all documentation from > > Confluence to a static site generator. While not related directly to > > JSPWiki, the reasons why they switched are interesting, and it's not > > every day one hears about a switch from the Microsoft Office of wikis: > > > > https://www.nuxeo.com/blog/from-confluence-to-metalsmith- > > a-migration-story-of-nuxeo-docs/ > > > > This could provide some insight into potential features for JSPWiki down > > the line. > > > > Cheers, > > Dave > > > > -- > > Dave Koelmeyer > > http://blog.davekoelmeyer.co.nz > > GPG Key ID: 0x238BFF87 > > > > > -- Col
