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!
@Mukkamala-Akhil said in Please let us know whether NodeBB will be actively maintained as Enterprise Grade Community Software. ?:
@scottalanmiller said in Please let us know whether NodeBB will be actively maintained as Enterprise Grade Community Software. ?:
Not rude, just wondering why you were tagging me for input for plugin requests. I'm a pretty random person to have asked to respond about them.
Cos, You replied to my previous thread. So I thought you'll be throwing some light about NodeBB.
Sure, but your questions were about feature requests. Your original question was about when NodeBB would be enterprise maintained, and that was easy to answer... five years ago and continuously since then. It's absolutely enterprise ready now.
Your next set of questions weren't really questions, but just mentions of features specific for you that you'd like someone to develop. There wasn't really a question to answer there, it's just a note that you'd like to see those features. Not much that I, as a long time user, can say about those.
I can shed light on the usual paths... you can make a thread requesting them (one thread each or no one will notice), but unless they get loads of traction, there is no reason to assume that NodeBB will even consider that - that's not how the core system works. You can hope that others want them too and that someone third party makes a plugin for you to use, but if that is going to happen it is most likely to have already happened. You can offer a bounty on the plugins. Or you can hire either NodeBB themselves or a third party to make plugins. That's easy to do, but expensive.
Other than that, I'm just an end user like you, but not one that wants those features so am glad that NodeBB is not focusing on them.
The reason that no one responded to that particular post is because, if you read it, there isn't a question - nothing that would warrant a response. So I had read it, but it just seemed like you were mentioning a wish list. Which would make no sense for me to respond to since you weren't wishing it from me.
@PitaJ said in Scheduled Posts:
It may also be possible to set up a script running client-side that would submit a post at a certain time, though that would require you keep your tab open (but would probably be better than the CLI method).
Making a little app that does it externally would only be so hard, too.
@Enrique the main problem you seem to be having is that you are not aware that there is a frontend and a backend to NodeBB. You have to wire up the controls from the ACP and make a call to the backend (via websocket, for example), and then you can call server side libraries.
Thank you for your reply, and sorry for lack of information.
http://184.108.40.206:4567/nodebb/ → success to show nodebb.
http://220.127.116.11/nodebb/ → return 404 on parent site(my case is wordpress on nginx).
http://18.104.22.168:4567/ → return misconfigured csrf error on nodebb.
http://22.214.171.124:4567/nodebb → return /nodebbcategories not found on nodebb.
I reloaded nginx.
I setup and restart nodebb each time.
nginx -t → syntax and test is successful.
now I am trying below
I've been noticing some UI issues every time a user logs in or out.
Basically right after you log in, some of the styles do not get picked up (i.e. logo becomes larger, recent-topic cards stop displaying content). Refreshing the page fixes the issue but this is not ideal.
I solved my own problem... I setup a custom notification to fire on the action:post.save hook and I was using the same default standard format for the notifications nid value. Basically I was firing off a notification with the same nid as the notification that auto generates when you post a new topic.
Long story short: Make sure the nid is unique.
@julian said in What hook can I use to filter the topics that appear when accessing /groups/mygroupname ?:
Thank you for this info. My issue is now solved. I was able to perform my serverside filter logic and now everything is great.
FYI - I'm the same guy (username: jremi) that you helped related to the sharing sessions plugin. I was asking you about if using the cross storage solution would work for cross domain cookies.
Thanks again for your help. I really appreciate your assistance.