This would be a cool feature for all “generator”-like use cases, and many others.
Maybe it is an additional Button feature, where you can select the “data source”.
Or it could be Column feature, that you can activate in the “format column” menu. When it is activated, a small “copy to clipboard” icon appears next to the data-cell value.
+1 vote for this. A copy to clipboard option would be extremely useful, particularly because the number of packs are still very limited.
For example, I have a doc that generates the text for an email. Because I don’t use gMail, I need to copy the text from Coda and paste in my email client. Having a button that would copy to clipboard would make this a much simpler (instead of click in cell, then click and drag to select, then Cmd+C to copy) and more elegant process.
For me, cells are a great way to start I have not thought about sections as a whole, but can’t find a use case right now
My main use case are generators, where different values / results are combined with a formular / a button. The outcome (a link, a number, a text) needs to be used somewhere outside Coda. I can calculate it in a cell, and then want to copy the result to the new location. A second use case is a Brand Book / Design Guide. E.g. brand color codes can be ‘picked’ into clipboard with one click. Cell-level would do that again.
Regarding developing your own text layout, for me it was just a lot of trial and error. The best I can suggest is just to look at lots of other people’s docs. Even those that don’t seem related to what you want to do, will have interesting solutions. It’s through doing this that I discovered the FormulaMap function for example. I was looking at someone’s solution for something else, but once I came across that function, it really expanded what I could do with Coda. Similarly for the RunActions function, that’s fantastic as well for being able to carry out multiple steps with one button click.
It’s one of the great things about Coda and its community, the way everyone shares their docs and knowledge.
+1 for both options, although I guess the former would be easier
My use case is an internal purchase request doc I’m building for my lab. The students will fill a kind of request form with the necessary details (item, vendor, quantity, etc) and then, when I want to create a purchase order, I will copy and paste the required details to the university’s purchasing system.
This is going to be harder than I expected, especially since actions are computed asynchronously and the copy command should be executed synchronously.