Title: Expose NSFW/18+ Flag as a CSS Class or BBCode for Styling and Visibility   Description:  

What functionality is missing? What is unsatisfying with the current situation?

Currently, there is a checkbox under Article Preferences to mark an article as containing NSFW and/or 18+ content. This checkbox works well to control access, as it triggers the appropriate warning page for users who are either not logged in or have not opted into viewing 18+ content.     However, this flag does not currently expose any CSS class or BBCode that authors can use to visually mark, style, or hide/show elements based on the NSFW setting. Unlike tags—which automatically add identifiable classes that can be targeted in CSS—this checkbox functions entirely in the background, without any direct, visible indicator to readers or builders once the article is viewed.   To maintain consistency across the UI, and to support clearer content signaling, it would be helpful if the NSFW/18+ flag also added a class or BBCode marker that could be targeted via custom CSS or conditional BBCode logic.  

How does this feature request address the current situation?

By exposing the NSFW/18+ flag as a targetable class or BBCode condition, this request would allow worldbuilders to:  

Add visual indicators (e.g., an icon, banner, or label) to clearly mark NSFW content inside the article itself.

Apply custom styling or warnings for readers who are already cleared to see the article.

Hide/show specific content blocks based on whether the article is flagged, without needing redundant tags or manual settings.

Align the NSFW checkbox behavior with existing systems (like tags or categories), making the builder experience more predictable.

Right now, the only way to manually style or label NSFW content is through additional tags, which introduces duplicate effort and a higher chance for inconsistency or user error. This feature would reduce the need for workaround solutions.  

What are other uses for this feature request?

Streamline worldbuilding workflows for authors who manage content for different age groups or content safety tiers.

Help co-authors and editors more easily identify sensitive material while working collaboratively.

Enable template-level customization for NSFW content without hardcoding a tag into every article.

Offer more transparency to readers, especially in long-form content where the nature of NSFW material might not be immediately obvious.

---