BladeXBladeX

BladeX — fast, stable, efficient. A long-term partner for enterprise digital transformation.

  • Open-source QQ group · 1078507904
  • Member QQ group · 748802498
  • Email · bladejava@qq.com

Catalog

  • Products
  • Plugins
  • Pricing
  • License

Products

  • BladeX Enterprise
  • BladeX IoT Platform
  • BladeX AI Platform
  • BladeX Visual Platform

Open Source

  • SpringBlade · Gitee
  • SpringBlade · GitHub
  • BladeTool · GitHub
  • Saber · Gitee

Partners

  • DreamLu
  • Avue.js
  • Gitee
  • BladeX · SNS
BladeX

Copyrights © 2026 Shanghai Bladex Technology Co., Ltd. All Rights Reserved.

苏公网安备 32041102000998号沪ICP备2023009528号-1

BladeXBladeX
  • Home
  • Products
  • Plugins
  • Pricing
  • License
  • Community
  • Contact
  • Core ProductsMore
    • BladeX Microservices Platformsaber3.bladex.cn
    • BladeX AI Platformaigc.bladex.cn
    • BladeX IoT Platformlinks.bladex.cn
    • BladeX Data Visualization Platformdata.bladex.cn
    Ecosystem PluginsMore
    • BladeX Workflow Platformdemo3.nutflow.vip
    • BladeX SCADA Platformscada.bladex.cn
    • BladeX Visualization Digital Twindata.bladex.cn/digitwin
    Live previews · open in new tabbladex.cn
Grain overlay
COMMUNITY

Master the art of asking — faster replies follow.

BladeX technical Q&A runs exclusively through sns.bladex.cn. Structured questions earn higher-quality answers, and archived threads feed AI training data so the assistant can co-triage future questions and keep response times sharp.

Open communitySee posting guidelines
OFFICE HOURS
09:0017:00
Weekday support windowWeekends & national holidays: off

Outside office hours, please still post on the community (sns.bladex.cn) — we process the backlog during the next support window.

THE CHANNEL

BladeX community forum

sns.bladex.cn

Technical Q&A runs exclusively on the community forum. Register, post in the relevant section, and link back to your thread — other channels (WeChat groups, DMs, email, tickets) aren't guaranteed to respond for technical questions.

Open community
TRIAGE FLOW

Five steps from problem to reply

The five steps below are the recommended triage flow. Following them gets your question answered faster and helps future developers hitting the same problem.

  1. 01

    Hit a problem or bug.

  2. 02

    Business-logic issue? Drop a breakpoint and try to isolate it locally first.

  3. 03

    System / framework issue? Search Baidu, Google and the community for existing answers.

  4. 04

    Still stuck? Post a detailed question on the community at sns.bladex.cn, following the posting guidelines below.

  5. 05

    Once posted, the team replies during office hours — please be patient and avoid reposting or DMing.

RULES OF ENGAGEMENT

Keep support bandwidth fair

A handful of simple agreements so every person who needs help gets seen.

  1. 01

    One official channel

    We answer only on the community forum (sns.bladex.cn). Other channels aren't guaranteed.

  2. 02

    Search before you post

    Try Baidu / Google / the community for basic questions first. Save support bandwidth for the hard problems.

  3. 03

    Office hours window

    Office hours are Mon–Fri 09:00–17:00. Weekends and holidays: off.

  4. 04

    Post in a structured way

    Follow the posting guidelines below — it cuts the back-and-forth cost.

POSTING GUIDELINES

Get sharper answers sooner

Vague questions raise answer cost and delay replies. Include all five of the following when you post:

  1. 01

    Reproduction steps

    Which page / endpoint you started from, what you clicked, what inputs you passed.

  2. 02

    Full error detail

    Complete stack, error.message, HTTP status code, relevant log snippets.

  3. 03

    Relevant code & logic

    Paste the key snippet or link a repo; describe the surrounding business logic.

  4. 04

    Software versions

    BladeX / JDK / Node.js / frontend framework versions.

  5. 05

    Operating system

    OS version of the runtime (Windows / macOS / Linux distro and version).