Bludit v3.21.1 is here

[Edi]

Bludit v3.21.1 is here and can be downloaded from

https://www.bludit.com

[bayerberg]

damn... can't keep up with updates anymore as soon as I install one the next one pops up!

btw. was working on a Claude plugin and now I'm not sure it's needed.

[kbeezie]

btw. was working on a Claude plugin and now I'm not sure it's needed.

Such as using Claude to help build the plugin, or something else?

If you meant using it to help find the undocumented quirks in help building a plugin I actually built a larger one with Deepseek v4 Pro, then created some flash optimized reference plus "theme architect" and "plugin architect" that I can load beforehand to help fill in the gaps that are not currently documented, so that it's working with the actual source behavior and not what a web search shows.

The v4 Flash optimized one (ie: stripped of the reasoning nuances and just pure syntax and flow) seems to work rather well with Qwen 2.5 Coder as well as the old blend of DeepSeek-R1-Distill-Qwen-7B if you're the type that runs a locally running Model on your 8GB vRam for free (they work pretty well on my old Nvidia 2060 Super 8GB).

Note sure if you can do the same with Claude, but this is what I did with Deepseek v4 Pro in telling to create me a reference I can reuse in future chats , and repeated with Flash Optimized (so can do the same in v4 Flash), as well as one for Theme Architect and Plugin Architect (has all the details on what's needed to correctly configure either with any known bugs currently in 3.21.1 [there's a couple])

Code: Select all

**“Create a reusable, source‑verified Bludit Pro Developer Reference based on everything you’ve analyzed in this chat.
Include:
– Verified plugin API (all hooks, methods, parameters, return values)
– Verified theme API
– Actual internal behavior vs documented behavior
– Known quirks and edge cases
– Correct patterns for plugin development
– Correct patterns for theme development
– Notes on routing, rendering, and load order
– Any pitfalls or undocumented behaviors
– A checklist for building new plugins
– A checklist for building new themes

Format it as a clean, structured technical document I can reuse in future chats.”**

Example of the Architect Prompt

Code: Select all

**Create a compact, Flash‑optimized “Bludit Pro Plugin Architecture Reference” based on everything you’ve learned in this chat.

Requirements:**
– Must be source‑verified, not documentation‑based
– Must include:
• Plugin lifecycle (constructor → init → prepare → hooks → save)
• Required files and folder structure
• All plugin properties (dbFields, db, formButtons, customHooks, etc.)
• All plugin methods with correct signatures and behaviors
• Hook system: how hooks are registered, invoked, and ordered
• Routing overrides using beforeAll + Reflection
• How to read/write settings safely
• How to detect other plugins
• Workspace usage
• Asset inclusion (includeCSS, includeJS)
• Metadata handling
• Known quirks and pitfalls (source‑verified)
– Must include a Plugin Development Checklist  
– Must be formatted as a single Markdown document  
– Must avoid long reasoning chains; keep it flat, explicit, and lookup‑friendly
– Output should be optimized for use with DeepSeek Flash

Goal: Produce a reusable, accurate reference I can feed into Flash for future plugin development.

I can share the already built 3.21.1 references if you want, not sure how it'll translate over into Claude.

[bayerberg]

wow

I wanted to do a article writer plugin. Claude has a php thing ready to use and it's relatively easy to hook it up to such plugin.

[kbeezie]

wow

I wanted to do a article writer plugin. Claude has a php thing ready to use and it's relatively easy to hook it up to such plugin.

Ahh I see. I prefer to keep that kind of process in the chat client so I can tweak as needed with my own insights or corrections and can summarize the process to go back thru and check on other stuff. (Since I would want to proofread everything before publishing anyways).

Interesting idea though. Might be better to use the DeepSeek API for that, would run you less than 15 cents per million tokens for v4 flash , and 40 cents for v4 pro (until 5/30 then it's 1.74, which you'd only need for heavy reasoning anyways). And it's even cheaper if you hit it with the same repeated input for new content generated since cache hits would be less than 1 cent per million tokens.