What makes a wiki suck?
-
Actually, I think you're right - I'll reword it as "The contents of a line cannot affect the output of any preceding line"
So how do you close a block?
-
Say $$$ indicates a div (it won't - but whatever)
$$$ A line $$$Becomes
<div> A line </div>The first one opens a block, the third line closes. So the first line effects how the third is output. Hope this makes sense, it's been a long day.
-
Bah, my gradients are teh suck.
-
The first one opens a block, the third line closes. So the first line effects how the third is output.
Right; but the third line affects a line other than itself. (Depending on how you look at it, either the first, or the line after the third line.) EDIT: oh wait, you changed it to any PRECEDING line, so maybe you have an "out". Maybe.
I'm sure it makes sense in your head, but I'm not sure the words you're typing correctly communicate the thoughts you have.
And none of this has anything to do with creating a really killer wiki.
-
I'm sure it makes sense in your head, but I'm not sure the words you're typing correctly communicate the thoughts you have.
It makes sense, but not in the way you're thinking. In other words, he means that a line is interpreted the same way, no matter what's on the line before or after it. As opposed to putting some dashes surrounded by newlines vs right below a line of text here on Discourse.
-
It makes sense, but not in the way you're thinking. In other words, he means that a line is interpreted the same way, no matter what's on the line before or after it. As opposed to putting some dashes surrounded by newlines vs right below a line of text here on Discourse.
I think it's a bad idea, at least for a wiki where anyone is exchanging code. Having a convenient way to mark a multi-line block of code as such is ever so useful.
-
The email not working would be a problem. If it had worked, you could update the user's email address in the database and he could have it mail a new password.
-
Ok, a couple of people have mentioned this, but I think a large part of what makes a wiki suck or not is the community. Rather than thinking about making the layoout good or not, think about what you can do to
encouragefacilitate good neighbourship among the users. The key flaw in wikis in this regard might be talk pages. Talk pages are always threaded discussions with headings and subheadings and usernames next to posts, but you have to put that stuff in manually, and if you do it wrong, or forget to sign your post, people get pissy.So, my thoughts:
- Look at current wiki talk pages
- Write something that produces similar output, but automates the boring bits
- Probably have the most recently active sections at the top, though
- Adding avatars/usercards could go a long way to making a place feel more vibrant
- If you want to allow social media comments, don't integrate them into the community sections, rather leave them as a ‘peanut gallery’ at the bottom of the page, like most wikis that have them already do corrrectly
-
We've given him like 10 ideas for a good Wiki product, and instead he's jerking-off creating Yet Another Shitty Markup Language. It's a lost cause.
-
The key flaw in wikis in this regard might be talk pages. Talk pages are always threaded discussions with headings and subheadings and usernames next to posts, but you have to put that stuff in manually, and if you do it wrong, or forget to sign your post, people get pissy.
Are you thinking what I am thinking? DiscoWiki?
It is everything else, it may as well be a wiki also!
-
instead he's jerking-off creating Yet Another Shitty Markup Language.
Is it time for the obligatory XKCD?
Yes.
-
creating Yet Another Shitty Markup Language
Yeah, but I suppose he needs to have something fun in the project to keep him interested.
Anyway, thinking about the templating suggestions that were mentioned, remember instant update?
(Executive summary: when you click ‘edit’, every html element that has an
idattribute becomes wysiwyg-editable)http://what.thedailywtf.com/t/instant-update-open-source-cms/4692/
Add some of the stuff mentioned in the current thread, and I bet you could get a pretty slick wiki out of it.
It is everything else, it may as well be a wiki also!
Domain Specific Discourse.
-
Yeah, but I suppose he needs to have something fun in the project to keep him interested.
If I live for a million years, I will never understand how people find something that's not only tedious, but has been done a billion times before, "fun".
-
something that's not only tedious, but has been done a billion times before
That is the definition of fun, as far as I can tell.
-
That is the definition of fun, as far as I can tell.
See: Everything that people do for recreation...
-
-
Losing?
Days since last @ben_lubar post with
outDwarf Fortress reference: 0
Filed under: I have an idea for another bot for @accalia...
Edit reason: Poster apparently does not understand English or negation.
-
Filed under: I have an idea for another bot for @accalia...
It should have a real time,
accurateprecise to the nanosecond.
-
It should have a real time, accurate to the nanosecond.
So...a @riking-@accalia collaboration?
-
Days since last @ben_lubar post without Dwarf Fortress reference: 0
Technically, this is true because of this post:
http://what.thedailywtf.com/t/gnu-coreutils-sort-u/8684/6?u=ben_lubar
-
Losing?
✓ Tedious
✓ Been done a billion times before
Back on topic: theoretically, a new markup language could be good branding for a wiki, if it were distinctive enough. Like if you're editing a wiki page, and have to use some newfangled syntax for every little thing, that could help to remind you that you're on a @null_loop™ wiki. Obviously this is a double-edged sword, though.
-
Technically, this is true because of this post:
Not sure if trolling or whooshing....
-
Filed under: I have an idea for another bot for @accalia...
Pull requests accepted. :-P
-
-
Not sure if capable of understanding that @Polygeekery posted "0 days since @ben_lubar's last post with no reference to Dwarf Fortress"
-
Pull requests accepted.
What makes a wiki suck: people start feeling like they ‘own’ certain pages.
What makes a wiki suck: when people have no attachment at all to pages they created or edited.
-
Not sure if capable of understanding that @Polygeekery posted "0 days since @ben_lubar's last post with no reference to Dwarf Fortress"
You're a robot, aren't you? ;)
the definition of fun
@ben_lubar said:Losing?
Relevant bit:
As there is no way to win the game, every fortress, no matter how successful usually gets destroyed somehow and to encourage experimenting further through this, prompted the unofficial community phrase: "Losing is Fun!"
-
-
Actually the DF tileset repository is perhaps a good example of what might be needed in terms of templating and collection views. At http://dwarffortresswiki.org/index.php?title=Tileset_repository&oldid=199177 the page was still in the egocentric layout that would have seemed natural to people adding their own tilesets ad-hoc to the repo. It was frustrating to use if you wanted to find something in a particular size, which I figured was the most common use case for people coming to the wiki to find tilesets, so I reordered everything, tediously.
What's interesting is that there already was a mediawiki template for tilesets, that each tileset on that page was an instance of. Except that the way the page had been laid out before, each tileset had its title as a section header above the template, which I thoughtlessly discarded when I edited, as someone else pointed out in the talk: http://dwarffortresswiki.org/index.php/Talk:Tileset_repository#Headers_and_anchors
Anyway, the main thing is that there should have been no need to lay that page out any particular way: since each tileset was already a template instance, the whole page could have been a collection view that would have allowed filtering and ordering any way the user wanted.
-
Except that you posted
@Polygeekery said:Days since last @ben_lubar post without Dwarf Fortress reference: 0
which contains the word "without" instead of the word "with", which negates the meaning of your statement.
-
...I am not bringing my A-game tonight...
-
So wait, was that a DF reference or not?
-
So wait, was that a DF reference or not?
I think it was, but I am also not entirely sure that I did not just fail a Turing Test.
-
Yet Another Shitty Markup Language. It's a lost cause.
Seriously though, I'd be pretty surprised if it was as bad as Markdown...
-
What if the spec is just "markdown but with dollar signs"?
-
What if the spec is just "markdown but with dollar signs"?
They have options for that.
-
Any news?
-
Look at what Sharepoint does, and basically replicate it
Last time I looked at sharepoint wiki, it only worked in IE and was a horrible shit. Is Microsoft paying you for shils?
-
When was the "last time"? 1998?
I just don't live in a timepod.
-
I want to build my own markdown based wiki (maybe scratching a mongodb itch... maybe). One that doesn't suck and that people want to use.
Markdown
Doesn't suckYou can only choose one.
-
When was the "last time"? 1998?
I just don't live in a timepod.
Isn't there a single Microsoft product you don't like?
-
Yes. Or maybe no. Your double-negative is confusing me.
-
This post is deleted!
-
Of course there are. For starters, they're not his holy grail of software engineering, known to common folk as Mac Classic.
-
Microsoft Bob.
-
Clippy
Dwarf Fortress - Wikipedia
