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!
If it were a bot, I could assign it a token from the ACP. I am creating a third party application that interfaces with NodeBB. It needs to be able to inherently create new user accounts, and then also login as them (which is where logging in via a token would come into play). I suppose it would be possible to create an account via a socket connection directly, but I imagine I could have uses to some of the write API methods anyways.
Is it possible to programmatically create user tokens for the Write API? If that's the case, I could use a socket to create the account, and then generate a JWT token specifically for that user rather than hacking something into the application itself. That would leave the only hurdle being logging in, but at that point I could just store encrypted login credentials in a config file, and login to the API using https://github.com/NicolasSiver/nodebb-plugin-ns-login
I'd like to export a list of the users and their emails from a specific group. Is there a way to do this? And if not, is there a way to export all users, but add more fields to the list besides username and email address?
Hi @mikewa, we don't have a plugin that allows NodeBB to act as the OAuth2 provider, but I'm interested in creating one if you're interested.
Reach out to us at email@example.com and I'll be happy to discuss further
We did have one in the past, although it is likely not working anymore.
In communities where we participated heavily, but didn't run the community ourselves, we used to build tooling that would go post by post and pull out some of this data and record date-time and poster of different posts and threads to track how people would post over time.
Sorry for necromancy but I have exactly the same problem as @shri to change sidebar bootstrap properties...
With the latest nodebb version, do I need to do the same hack modifying directly the widget.js code ?