# \[csln\] ideas for development workflow, etc

**URL:** <https://discourse.citationstyles.org/t/csln-ideas-for-development-workflow-etc/1851>\
**Category:** CSL Development\
**Created:** [June 30, 2024, 1:30pm UTC](https://discourse.citationstyles.org/t/csln-ideas-for-development-workflow-etc/1851 "2024-06-30T13:30:56Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bruce\_D\_Arcus1](https://avatars.discourse-cdn.com/v4/letter/b/4bbf92/32.png) [@Bruce\_D\_Arcus1](https://discourse.citationstyles.org/u/Bruce_D_Arcus1)\
**Post date:** [June 30, 2024, 1:30pm UTC](https://discourse.citationstyles.org/t/csln-ideas-for-development-workflow-etc/1851/1 "2024-06-30T13:30:56Z")

</div>

I’ve not had much time, nor apparent outside interest, in working more on my [next-gen CSL experiment](https://github.com/bdarcus/csln), but I have gotten pretty far in figuring out possible answers to the [questions we failed to resolve in 2022](https://discourse.citationstyles.org/t/upcoming-csl-meetup-context/1767).

[Here’s a post](https://github.com/bdarcus/csln/discussions/152) that lays out a key part of that: both a technical approach, but also how that might enable a workflow for managing change.

Aside: some of the ideas I’ve been playing with, including these, are inspired by what I’ve seen digging into biblatex.

Finally: it’s now been close to two years since we had that meeting, with zero movement, or resolution to any of those questions. But we still get feature requests for CSL, without any idea of if or how we implement them. I remain concerned about this, and see no way forward with status quo.