How to edit a single page on a LifeItself website

[olayway]

Job story

As a new contributor to a Flowershow/PortalJS site (e.g. LifeItself.org), I want to edit an existing page on the website (whose contents are stored on GitHub), i.e. add/change some text, edit/add links to other pages, and/or add images to it so that the page is updated.

• What does this contributor know ...?
• Assume (but flag) you have edit access to the relevant repo/system (i.e. don't explain the process of getting the access in the tutorial)
• Any website that is markdown based with jam-stacky tendencies would be relevant here, not only Flowershow based one
• There is going to be a sandbox that readers can use when following the tutorial. A sandbox is a single instance of a simple Flowershow website with a few example pages. Assume this sandbox is already set up including automatic deployment.
• Will there be a live preview somewhere? No, not for now.
• ❗️ For now, add any terms/concepts explanations in e.g. Obsidian info callouts. They will form the basis of relevant sections in our Contributors Guide in the future.

Tasks

• [x] Create a sandbox Repo: https://github.com/datopian/flowershow-sandbox; Deployment: https://flowershow-sandbox.vercel.app/
• [x] Write a draft https://hackmd.io/qAJFi0O0Q9G4ZubeSCet9g?edit
• [ ] Write the content (no screenshots in this step yet)
• [ ] Try it out and adjust if necessary
• [ ] Improvements
  • [ ] Screenshots
  • [ ] Video (you have the script already with the tutorial)

[olayway]

@ZybN

I've created a very simple draft of the tutorial. The gist of it we already had in our mindmap, so I've added a screenshot of it instead of writing it over again. You can adjust the structure of the draft if you want (add, rename headings, etc.).

I've also created a sandbox app that people following the tutorial can use to test the flow before they attempt to make changes in the target website repo (see links in the issue description). You can also use it while writing the tutorial to go through all the steps we're trying to document and to make sure we don't miss anything.

For now please just write the raw content, no screenshots are needed. Once we have the copy, we'll maybe add just a few screenshots and record the video tutorial to show the rest (e.g. where you need to navigate to or click). That being said, you don't need to go into extreme details when writing the steps in the tutorial - these can be shown in the video.

[olayway]

@ZybN I've seen your draft. The steps are more or less correct but can you please write the whole tutorial draft? I mean, the tutorial shouldn't include just the 1, 2, 3... steps. It's a whole piece of writing, which could probably use some intro, some summary etc. That's why I prepared the skeleton in hackmd in the first place, which you were supposed to use - fill in with content (and ofc adjust if needed). Does that make sense?