The case for asciidoc from the asciidoctor folks, quoted liberally from AsciiDoc vs Markdown for purposes of discussion and analysis (i.e. Fair Use):
"The defacto lightweight markup language is Markdown. (At least, that’s what you call it at first). The
main advantage of Markdown lies in its primitive syntax: its manual and cheatsheet are one and the
same. But this advantage is also its greatest weakness.
As soon as authors need something slightly more complex than basic prose (e.g., tables, cross
references, footnotes, embedded YouTube videos, etc.), they find themselves resorting to embedded
HTML or seeking out more feature-rich implementations. Markdown has become a maze of different
implementations, termed “flavors”, which make a universal definition evasive.
The IETF has declared “there is no such thing as "invalid" Markdown.” See This Is Markdown!
Or: Markup and Its Discontents.
Here’s how the story inevitably goes. You start out with Markdown. Then it’s Markdown + X. Then
Markdown + X + Y. And down the rabbit hole you go. What’s worse, X and Y often require you to
sprinkle in HTML, unnecessarily coupling content with presentation and wrecking portability. Your
instinct to choose Markdown is good. There are just better options.
AsciiDoc presents a more sound alternative. The AsciiDoc syntax is more concise than (or at least as
concise as) Markdown. At the same time, AsciiDoc offers power and flexibility without requiring the
use of HTML or “flavors” for essential syntax such as tables, description lists, admonitions (tips, notes,
warnings, etc.) and table of contents.
It’s important to understand that AsciiDoc was initially designed as a plain-text alternative to the
DocBook XML schema. AsciiDoc isn’t stuck in a game of whack-a-mole trying to satisfy publishing
needs like Markdown. Rather, the AsciiDoc syntax was explicitly designed with the needs of publishing
in mind, both print and web. If the need arises, you can make full use of the huge choice of tools
available for a DocBook workflow using Asciidoctor’s DocBook converter. That’s why mapping to an
enterprise documentation format like DocBook remains a key use case for AsciiDoc.
And yet, AsciiDoc is simple enough to stand in as a better flavor of Markdown. But what truly makes
AsciiDoc the right investment is that its syntax was designed to be extended as a core feature. This
extensibility not only means that AsciiDoc has a lot more to offer, with room to grow, it also fulfills the
objective of ensuring your content is maximally reusable."
Alright. Okay. I know what I said before. But there is one other thing. Drum roll, please....
The visitor and use graph on the Admin landing page is useful to me. Some nice presets that cover most everything I'd be interested in. But I do find myself oft times pining for an hourly X-Axis spanning more days, e.g. 72 hour axis scaled in one hour increments.
Damn. This is a slimline the cruft and tech debt announcement and I've now added two feature requests. Mea culpa!
Thanks and keep up the great work!
@crazycells said in Forum Stats CSS Issue:
@Tpk you have very cool stats right here:
would you mind sharing the codes for this appearance ?
@Tpk it would be great if you can share the codes. This looks very cool!
Hooray for forward-thinking
Initially, we kicked around the idea of supporting multiple categories per topic (so, more like a "tagging" approach, as opposed to categories).
In the end, we felt that having a "middle-ground" between statically defined categories and user-defined tags was not a proper compromise (since it ended up not being greater than the sum of its parts), so we stuck with static categories.
A tagging plugin can be built, of course........
Need a custom theme or plugin for NodeBB - Google Search
I just posted that question on SO to flamebait Jeff Atwood Just kidding
Yes we figured it out, as per the link above, we are showing up on the discussions tab on Google now Not sure if discourse has yet...
I don't think so..
Hey @RefinedSoftware, @caske33,
There's an ongoing issue right now with plugins not being "ajaxified" in the admin panel. "Ajaxifying" is our pet name for our shorthand method that loads pages in NodeBB (since it is a one-page application, it doesn't truly do a page reload when you click links).
Give it a try, if you'd like:
Open up your console (hit F12), and navigate to the console tab, if it is not open already
Type in ajaxify.go('users/online') ;
Also, it looks like I found a bug with the Skype Emoji -- darnit.
Hi @sbdubz, our indiegogo campaign was over in August. We do have some unit tests but they do not cover the whole codebase yet. With that said NodeBB is already pretty stable and we usually get onto bugs that crop up within the same day.
I think you are referring to vars like
If that's the case you are right those can and probably should move into the functions where they are used.
Heroku allows developers to run small instances for free (even their redis add-on is free), but if your site becomes popular, you will have to pay.
We have a guide to setting up NodeBB on Heroku in our wiki.
I was working on my NodeBB server last night and noticed how actually annoying it is to set up, so not anyone can simply set it up...
So I started to ponder if I can make the process faster and easier for everyone to use and I came up with the following idea which I was able to get working on a NodeBB install integrated right into NodeBB which basically took all the methods and checked.
So What i did was the actual following:
Updated App.JS to support require.Resolve() method to check for all needed files
Made a basic requirements reader that was able to read the NodeBB package info
*Made it so it test each module to see if it existed on every start up, checked for updates and updated if needed or downloaded them and installed them if needed
Doing this took out about 15 to 20 mins of work for a none NodeJS user so all someone know would have to do is basically run
Without needing all the other things such as
Or anything of the sorts, i am working on also making it get it's other needed resources like redis and a few others
Will Post source to my github when I get home from work
I'll post some stuff here regarding my migration from SMF 2.x forum to NodeBB. I've had a forum for ~4 years and it's about time I revamped it. I'm a huge node.js and redis fan, so having a forum written in php is blasphemous.
thanks for all the effort you've put into this!:)