reply to u/Efficient_Earth_8773 at https://www.reddit.com/r/Zettelkasten/comments/15fjb97/does_anyone_has_its_zettelkasten_in_google_docs/

Experimenting can be interesting. I've tried using spreadsheet software like Google Sheets or Excel which can be simple and useful methods that don't lose significant functionality. I did separate sheets for zettels, sources, and the index. Each zettel had it's own row with with a number, title, contents, and a link to a source as well as the index.

Google Docs might be reasonably doable, but the linking portion may be one of the more difficult affordances to accomplish easily or in a very user-centric fashion. It is doable though: https://support.google.com/docs/answer/45893?hl=en&co=GENIE.Platform%3DDesktop, and one might even mix Google Docs with Google Sheets? I could see Sheets being useful for creating an index and or sources while Docs could be used for individual notes as well. It's all about affordances and ease of use. Text is a major portion of having and maintaining a zettelkasten, so by this logic anything that will allow that could potentially be used as a zettelkasten. However, it helps to think about how one will use it in practice on a day-to-day basis. How hard will it be to create links? Search it? How hard will it be when you've got thousands of "slips"? How much time will these things take as it scales up in size?

A paper-based example: One of the reasons that many pen and paper users only write on one side of their index cards is that it saves the time of needing to take cards out and check if they do or don't have writing on the back or remembering where something is when it was written on the back of a card. It's a lot easier to tip through your collection if they're written only on the front. If you use an alternate application/software what will all these daily functions look like compounded over time? Does the software make things simpler and easier or will it make them be more difficult or take more time? And is that difficulty and time useful or not to your particular practice? Historian and author David McCullough prefers a manual typewriter over computers with keyboards specifically because it forces him to slow down and take his time. Another affordance to consider is how much or little work one may need to put into using it from a linking (or not) perspective. Using paper forces one to create a minimum of at least one link (made by the simple fact of filing it next to another) while other methods like Obsidian allow you to too easily take notes and place them into an infinitely growing pile of orphaned notes. Is it then more work to create discrete links later when you've lost the context and threads of potential arguments you might make? Will your specific method help you to regularly review through old notes? How hard will it be to mix things up for creativity's sake? How easy/difficult will it be to use your notes for writing/creating new material, if you intend to use it for that?

Think about how and why you'd want to use it and which affordances you really want/need. Then the only way to tell is to try it out for a bit and see how one likes/doesn't like a particular method and whether or not it helps to motivate you in your work. If you don't like the look of an application and it makes you not want to use it regularly, that obviously is a deal breaker. One might also think about how difficult/easy import/export might be if they intend to hop from one application to another. Finally, switching applications every few months can be self-defeating, so beware of this potential downfall as you make what will eventually need to be your ultimate choice. Beware of shiny object syndrome or software that ceases updating in just a few years without easy export.

https://www.inkandswitch.com/peritext/

js /** * This component is just a Box with border. * It serves as an example of how you can incorporate * components together. * * Component also has slots, methods and events. * * @component * @example <caption>Basic usage just with the default slot</caption> * <Box> * I am inside a slot * </Box> * * @example <caption>Using second component inside</caption> * <Box> * <ProgressBar :spent="spent" :remaining="50"></ProgressBar> * </Box> * * @example <caption>Example of passing an entire component in a preview</caption> * { * template: `<Box> * <ProgressBar :spent="spent" :remaining="50"></ProgressBar> * <ProgressBar :spent="50" :remaining="50" style="margin-top: 20px"></ProgressBar> * </Box>`, * data: function() { * return {spent: 223}; * } * } */ export default { name: "Box", props: { /** * This will be in the header */ title: { type: String, default: "My box" } }, methods: { /** * Also, you can describe methods for each component * the same as you would do this in regular @jsdoc * documented file * * @param {string} prop1 some example property * @param {string} prop2 other property */ exampleMethod(prop1, prop2) { // method body // The method could even throw an event /** * This event could be thrown by component in case * of some kind of unexpected behaviour. * * @category API * @event unexpectedEvent */ this.$emit('unexpecteEvent') } } }

Werberger, Raleigh. “Using Old Tech (Not Edtech) to Teach Thinking Skills.” Edutopia (blog), January 28, 2015. https://www.edutopia.org/blog/old-tech-teach-thinking-skills-raleigh-werberger.

link to: https://boffosocko.com/2022/11/05/55811174/ for related suggestion using index cards rather than Post-it Notes.

This process is also a good physical visualization of how Hypothes.is works.

Actually, versioning problems also affect major online tools.

Google Docs sometimes merges file versions which means their versioning is unreliable.

In other words, Google Docs can't be relied on for versioning.

Apparently sharing/comparing notes was reasonable advice in 1910 including the idea of in-class signals for splitting up note taking amongst multiple people.

Compare this to shared notes (Google Docs, Etherpad, etc.) in modern context with multiple people doing simultaneous notes.

https://youneedawiki.com/

Looks like a service that takes a Google Docs folder and turns it into a wiki. Clever!

Should be "operating".

Should be "enter a reasonable"

Should be "this"

Should be "Suppose you have many labels"

Where did this Grid come from?

Should be "assemblies".

Should be "macOS".

Deployment of Project Pages from /docs folder on main branch.

source at: https://github.com/graphite-docs/graphite

How scientists can respond to COVID-19. (n.d.). Google Docs. Retrieved April 24, 2020, from https://docs.google.com/document/d/1DYoQH2YmrhAXs_DYwYMWKNaIXTC21zkR31RoCVmXeC4/edit?usp=embed_facebook

https://www.graphitedocs.com/

Create a course or documentation for academic

This YouTube video is a quick overview of the SAMR model of instruction essential for universal design. "S" stands for substitution - New tech replaces old material but does not change text. "A" stands for augmentation - students work to complete a task such as on google docs. "M" stands for modification - tech is used to redesign part of task and transform learning. Ex. google docs comment feature provides instant feedback. "R" stands for redefinition - design and create new tasks. Ex. communicating across world through google docs, discussing it through google voice and recording it all as presentation. Rating 10/10

a questo link è illustrata la procedura per realizzare l'embedding di hypothes.is all'interno di un documento Read the Docs. Una comoda utilità per consentire la partecipazione online alla redazione di un documento, postando il commento direttamente nella parola o rigo di interesse del commentatore.

Note that this means that you'd have to duplicate rules/integrations since the highest level of control is a single Team. Would be useful (not sure if this has the capability though) to be able to have a higher level of control over a specific subset of teams?

This may be pedantic but I think this wording can be a bit confusing, since doesn't it only run the steps inside the always (i.e. the condition block)? Otherwise it would run steps defined outside of this block as well.

e.g.

post {
  always {
   // only steps here would run
  }

// but this is still the post section so if steps here
// were defined, it shouldn't run AFAIK
}

docs

len(s) is built-in function

Return the length (the number of items) of an object. The argument may be a sequence (such as a string, bytes, tuple, list, or range) or a collection (such as a dictionary, set, or frozen set).

Looks solid!

Better if multi-line

Better if multi-line

An asset for education. Using notebooks in the classroom.