2f:T9dc,md`## BEFORE workshop on April 12: I’ve tried to meet with everyone in our mini-groups, but only David and Graham were able to attend together. We recorded this session and there was quite a lot of interesting discussion. Those of you who weren’t there, please **review [these recordings](https://brown.zoom.us/rec/share/bM5PwF1lEHCUwbPnFXtec0ghqGYIazsLW6sod2CaLXp8RGz-KVaw0XrPvLy4T-L0.wSu7S1OTn-d7NS8z)** – let me know if the link does not work for you – since there was quite a lot that will be of general interest, I believe. We are working to have our finished projects up and accessible by or before April 19! You should work with the person in your mini-group, and with myself, to make this happen. I will help with code and will very soon start to set up infrastructure for each of your websites. Your mini-group collaborator may also help you with code and is, as you know, already assigned also to write a brief appreciation of your work. The goal is: 1. A well-formatted, published notebook with: title, attribution, descriptive paragraph(s), what’s-at-stake paragraph(s), your colleague’s appreciation (attributed), and then everything else in the notebook including the working code. 2. A website that is driven by cells in this notebook. I will set up the simple infrastucture for this. (Except in the case of James, who is making his own webapp in a different framework – his Observable notebook will link to his webapp.) I will very soon have direct editing access to all your main project notebooks. We’ll be able to work steadily toward our goals and this will be the majority of our workshop work for this phase up the 19th. Remember that you should consider sharing your project notebook with the workshop member(s) in your mini-group in the same way that you have shared with me. Those you you who haven’t already done so **must** asap undertake the steps I set out in various emails to all of you: 1. Go to your main project notebook and make sure its latest version is ‘(Re)Publish’ed. 2. Click the ‘...’ menu for the notebook and scroll to the bottom. If ‘Go to Next’ is showing, then select it. (If it isn't showing this means that you are already using Observable's ‘Next’ user interface.) 3. Click the ‘...’ menu again and select ‘Share’. 4. Type ‘shadoof’ into the field for ‘User to share with ...’ and select my ID when it shows up. Make sure that I am given ‘Can edit’ access (default) and then click the ‘Confirm changes’ button. `30:T442,md`## FOR workshop on March 29: I checked in on the notebooks I am tracking for you over the weekend but did not see much that was new. At the last workshop I also asked that you all consider: making a list of \`‘tickets’\` for one or more \`‘issues’\` that you are having with the code for the project, indicating specific areas where you need help from me or from colleagues. So please: 1. Show (and ‘publish’) some progress on your projects before workshop later today. 1. Come to workshop with, at the end of your notebooks, a list of one or more \`issues\` on which you would like to work. Describe the issue as clearly as possible. The \`issue\` need not be a problem, it could be a specific request/desire for an enhancement on or a next-step for your project. 1. Be prepared to spend time in a break-out room with with another member of the workshop. For a goodly portion of this week’s workshop I will ask you to work on \`issues\` collaboratively in these breakout rooms, with me dropping in from time to time. You will then report back to the workshop as a whole. `31:T522,md`## TODO before meeting on March 1: 1. Make sure that you have made a notebook – the main notebook for your project – *in your personal account*. - The first cell of this notebook should contain your project’s (provisional) title *and* your name (on the second line of the Markdown seems best). - The second cell should be a draft (straighfforward, objective) description of the project (also in Markdown) – *as if it already existed*. - The third cell should be a brief draft paragraph on ‘what’s at stake’ for this project. - Anything else in subsequent cells is a bonus, especially, as I’ve been recommending: **pseudo code** and **storyboarding** (I’m including the notion that you might ‘storyboard’ in prose). - For my own, live, example of what I mean (from a more or less fully develop piece) read and explore [this copy of *shimmer*](/@shadoof/shimmer). 1. If you have not arranged an [Office Hours](http://goo.gl/1r99nM) or one-to-one meeting with me, do so now. 1. Review the notebook on [*Work, Suggestion, Merge &/ Apply*](https://observablehq.com/@dla/work-suggest-merge-apply). 1. Come prepared to actually do some work on your notebook in the first part of the meeting and then to present what you’ve got so far to the workshop in the latter part.`32:T961,md`## TODO During weeks 3 & 4, before meeting on Feb 22: 1. Ensure that you have copies of your own notebooks in your *personal* accounts.
*I’m pretty sure this is true for everyone except Megan and Brittany. Their first notebooks were created by myself within the dla team. I will work with Megan and Brittany separately to sort this out.* 1. Come up with a project idea for the semester, either the one that will develop into a final project, or one that you will bring to some kind of completion before or by **mid-semester – Mar 8**, then: - Either dedicate one of your existing personal notebooks to this project, or create a new notebook for it in your personal account. - Use \`md\` (Markdown) in one or two cells to describe your project:
What it will be. - In another cell, use \`md\`, but inside this one compose some lineated pseudo code within \`

\` tags to set out the processes and logics of any interactions with your project, even if this is only a step-by-step outline of what transpires for a reader over time. - In other cells, do things like: storyboarding; adding images and audio resources if you have them; beginning to actually code if you’re ready. - **Publish** the notebook, and let me know, by email, that you’ve done so. 1. Read, carefully, [this separate notebook on the *Work, Suggestion, Merge &/ Apply* circuit](https://observablehq.com/@dla/work-suggest-merge-apply) that we will all follow. - Practice by forking one of your colleague's notebooks. - Make some changes and Suggest them to your colleague’s ‘Parent’ notebook. 1. Read through the sample notebooks in the Weeks 3 & 4 collection, attempting to follow the code (but don’t worry if any of it is beyond you). 1. Dip into some or all of the following supplementary reading: - [Heldén & Jonson’s *Evolution*](http://www.textevolution.net/) (Online.) - [from: Nick Montfort’s *#!*](https://canvas.brown.edu/files/63551781/download?download_frd=1) (The link should take you to a pdf in the Canvas site and may ask you to login through Brown.) - Any published notebooks at [Daniel Howe’s Observable home page](https://observablehq.com/@dhowe), esp. anything \`RiTa\` related. 1. **Be ready** to present your work – this first project notebook – at the meeting on Feb 22.`33:Tbc5,md`## TODO During Week 2, before Feb 8: 1. Continue to experiment with with \`md\` (Markdown). Have a look at the \`md\` cells in any notebook.
Learn: Shift-Enter for when you've finished editing a cell, and Option-Delete for when you want to remove an empty cell from your notebook quickly. 2. Improve your *pseudo code*. Especially if you plan to use it for you project. Keep it readable and understandable as English but make it more like *actual* \`code\`. Example in the next item. 3. Forking, Suggesting, Merging:
*The following should still work in principle and is still a reasonable example of pseudo code but, having done some research on the way Observable 'teams' work, I've decided, basically, that you should keep your own working notebooks in your personal accounts. This will make forking and suggesting much more straightforward.*

if (you already have a 365-words notebook in your personal account AND
    I made a fork of that notebook and this fork is in your dla team collection), then {
    - navigate to the version in the dla team collection
    - make some changes to the dla team copy
    - click the notebook's "..." button
    - select Suggest
    - go to the parent copy of your notebook in your personal account
    - merge (i.e accept the suggestion)
}
else if (you only have a 365-words notebook that I made for you in your dla team collecton) {
    - go to this notebook
    - click the notebook's "..." button
    - select Fork      // NOTE you are now looking at the *forked* copy
    - click the notebook's "..." button
    - select Transfer and then highlight your personal account
    // the forked copy is now in your personal account
    - make some changes to the personal account copy
    - click the notebook's "..." button
    - select Suggest
    - go to the parent copy of your notebook in your dla team collection
    - merge (i.e accept the suggestion)
}

4. Better, get used to do doing this sort of thing with others in the workshop. Go to your one of your colleagues home pages (links below). Fork one of their notebooks into your personal account, then experiment with making changes and suggesting them to the colleague's 'parent' notebook. 5. Read through my [sifter notebook](https://observablehq.com/@dla/sifther). Make your own fork of this notebook. Keep it to yourself, that is: do *not* \`Share\` it for view and editing to the team. Play with your copy. Tinker with the code. Try changing words (anything inside double-quotes) or numerical values, like \`seconds\`. Don't worry about breaking things. You won’t do any harm. 6. Do some reading in amongst the material that is discoverable through the top-of-the-page \`Learn\` menu. 7. Think about the overall arc of the workshop: About preparing documentation for mid-semester. Read [this page in the Canvas site](https://canvas.brown.edu/courses/1083801/pages/project-proposals-and-documentation). Start thinking about what you’d like to do for a semester-final project. `34:T4a6,md`## TODO During workshop on Feb 1: 1. Experiment with md, markdown. Have a look at a number of cells in any notebook. (Learn: Shift-Enter for when you've finished editing a cell; and Option-Delete for when you want to remove an empty cell from your notebook quickly.) 2. *Pseudo code* An English language recipe describing exactly how you would like your 365 words to behave as and when certain events occur?
What do I mean by behave here? How does language behave? How should it? What “events”? What events usually occur when we are reading and why?
Are you content with the 365 words you have chosen? Do you want to take them further? Have you thought of other words which would be more amenable to “events" and “behavior”? With whichever are your preferred words, write a passage of pseudo code which unambiguously sets out how your words will behave when they are subject to one or more events. 3. Colloration. How did we get on with Commenting?
Ownership. Access permissions. Forking. Suggestions. 4. The Learn menu. 5. Overall arc of the workshop: Preparing for mid-semester. Documentation. Preparing for a semester-final project. `35:T4ec,md`## TODO during Week 1, ideally before Feb 1: 1. If you haven't already done so, use your Brown email address to create an account at https://Observablehq.com (If you already have an Observable account using a different email address, please make another account with your Brown address.) Use the Google option to authenticate your login identity with Observable. 2. I have invited those of you who were at the meeting to join the dla team. Please accept your invitations. If you weren't at the first meeting and want an invitation, let me know. 3. Publish the notebook that you made during the first meeting. If you weren't at the first meeting: make a notebook with at least two cells, one of which contains or displays your 365 words then publish the notebook. 4. I will find your notebooks. I will 'fork' these notebooks (make linked separate copies of the notebooks) and I will put the forked copies into the dla team. 5. For each of these forked notebooks, I will make a simple website that is driven by selected cells in the notebook. In the future, you will learn how to experiment with doing this kind of thing yourself. Or, if you can figure it out: Go for it! 6. Experiment with Commenting on one another’s notebook cells, within the dla team. `36:[] 2d:{"title":"aDLA","cells":[{"id":0,"value":"md`# aDLA`","pinned":false,"hidden":false,"mode":"ojs"},{"id":7,"value":"md`This is the landing page for the Advanced Digital Language Art workshop, Brown University, Literary Arts, Digital & Cross-Disciplinary, LITR 1010D, Spring 2021.\n\n• [Brittany Park](/@brittanypark99) • [David Onabanjo](/@writeallalong) • [Emma Capps](/@emmatcapps) • [Florence Wallis](/@florencewallis) • [Graham Bishop](/@grahammatology) • [James Huang](/@jh1) • [John Cayley](/@shadoof) • [Megan Slusarewicz](/@meganificent) • [Murphy Chang](/@murphy) • [SA Chavarría](/@sachavarria)\n\nHere you will find the current weekly assignments, projects, and plans.
**Scroll down for earlier todo lists.**`","pinned":false,"hidden":false,"mode":"ojs"},{"id":300,"value":"$2f","pinned":false,"hidden":false,"mode":"ojs"},{"id":287,"value":"md`---\n### *Past:* `","pinned":false,"hidden":false,"mode":"ojs"},{"id":297,"value":"$30","pinned":false,"hidden":false,"mode":"ojs"},{"id":260,"value":"md`## TODO before workshop on March 22:\n1. **Keep working to make progress on all your main project notebooks**:\n - I will check in on the notebooks throughout the week.\n1. We’ll be expecting presentation for critique/workshopping from: **Graham** and **James**, possibly something from **Brittany**. Everyone else should also be prepared to share whatever progress they are making on their projects.\n1. Optionally, set up a one-to-one meeting with me by sending me a couple of date+time’s that work for you and from which I will pick.\n1. Continue exploration of this collection, by Daniel Howe, covering his *RiTa* library and its affordances: https://observablehq.com/collection/@dhowe/rita\n - Reconsider finding something in this collection and the library that you might be able to use for your project.\n1. Optionally, have another look at the notebooks we recently discussed by penguin137: https://observablehq.com/@shadoof/word-operations and https://observablehq.com/@shadoof/cycle-poems`","pinned":false,"hidden":false,"mode":"ojs"},{"id":277,"value":"md`## TODO before workshop on March 8:\n1. **Show me some progression of work in your notebooks**:\n - I will check in on this tomorrow morning, Monday.
I have forked copies of each of your notebooks, tracking the one that you should be using to develop your chosen project. I'll compare my forked copy and whatever you’ve added in on Monday, as I say.\n - I’ve met individually with all of you except David, who is booked in for office hours tomorrow (great!), and James, who should *arrange a meeting with me asap* – looking forward to this!\n1. Do some exploration of this collection, by Daniel Howe, covering his *RiTa* library and its affordances: https://observablehq.com/collection/@dhowe/rita\n - Find something in this collection and the library that you might be able to use for your project.`","pinned":true,"hidden":false,"mode":"ojs"},{"id":253,"value":"md`## Warm-up Exercise (March 1):\n- Visit and read through my new notebook on [Getting Input](/@dla/getting-input).\n- Then do one of three things:\n - If you already have a notebook that uses inputs, get ready to show it to us and explain what you are doing and why.\n - Add code by cutting from my inputs notebook and pasting into one of your own. Then be sure to get it working. You only have to get the input working, you do not, yet, have to get it working with your own material, but if you can, all the better.\n - Take a fork of my inputs notebook into your personal account and play around with one or more of the input examples in order to make them into better/more amusing demos.\n`","pinned":false,"hidden":false,"mode":"ojs"},{"id":222,"value":"$31","pinned":false,"hidden":false,"mode":"ojs"},{"id":214,"value":"md`## Warm-up Exercise (Feb 22):\n- Fork – **into your personal accounts** – a copy of the notebook (you should find it yourselves) *A Paragraph that Evolves*.\n- Source a paragraph of your own, one that you would like to evolve.\n- In you fork, get your paragraph in to the cell that would allow this to happen.\n- See if you can add a cell with a variable that would allow you, more easily, to set the speed of ‘evolution’\n- Where should this variable be inserted: which cell? where?\n- Find the variable that sets the number of word changes that are made each tick of the ‘ticker.’\n- What is going on in this sketch !? Does it make sense?\n- How would you make this sketch ‘better’? How would you compose for it? What kind of paragraph or text would you give it?\n`","pinned":false,"hidden":false,"mode":"ojs"},{"id":156,"value":"$32","pinned":false,"hidden":false,"mode":"ojs"},{"id":129,"value":"md`## TODO During workshop on Feb 8:\n1. Introduce David ...\n2. Sort out collaborative ‘work flows.’ And introduce DCH’s \\`rs\\` tool, including how we got to it.\n3. Review questions and concerns from past work/assignments, pseudo code in particular. Read-throughs of *sifter*.\n4. Discuss project ideas, then ideas for how to prepare and make documentation. Reiteration of mid-semester and semester-final trajectory.
\n Presentations for critique. How critiques are run.\n5. Take time for some actual work on project ideas with pseudo code and psuedo code improvement: Javascript syntax.`","pinned":false,"hidden":false,"mode":"ojs"},{"id":77,"value":"$33","pinned":false,"hidden":false,"mode":"ojs"},{"id":93,"value":"$34","pinned":false,"hidden":false,"mode":"ojs"},{"id":89,"value":"$35","pinned":false,"hidden":false,"mode":"ojs"},{"id":66,"value":"md`## For the first meeting on January 25th, 3pm:\nIf at all possible and particularly if you are pretty sure that you will be taking or auditing this workshop:\n\n \\`Bring 365 words to the workshop.\\`\n\nYes, I am intentionally setting this assignment in these non-specific terms. Which words, their arrangement, their precise delivery media, your reasons for choosing them: it’s all entirely up to you. The only thing I would ask you to remember is that this is a Language Art workshop. These words should already have an aesthetic dimension and/or you should anticipate using them to make some art. And hey, it’s also a *Digital* Language Art workshop, so it will probably be a good idea to choose a delivery medium that will allow you to manipulate and reconfigure the words using digital editing tools. (But if you’d like to subvert this circumstance in some way, do be prepared to explain this ;)\n`","pinned":false,"hidden":false,"mode":"ojs"}],"files":"$W36","stdlib":"1","titling":"auto"}