Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate content from portaljs.org/guide to this site #7

Closed
11 of 12 tasks
Tracked by #12
rufuspollock opened this issue Dec 14, 2023 · 6 comments
Closed
11 of 12 tasks
Tracked by #12

Migrate content from portaljs.org/guide to this site #7

rufuspollock opened this issue Dec 14, 2023 · 6 comments
Assignees

Comments

@rufuspollock
Copy link
Member

rufuspollock commented Dec 14, 2023

Which itself was migrated from markdownbased site - see datopian/datahub#994

Content to migrate is therefore likely covered in this PR datopian/datahub#996 i.e. guide page plus some howtos.

Acceptance

Finally

  • Remove from portaljs.org (and add redirect?) ❌2023-12-21 WONTFIX. I think we should delete only once Makeitmarkdown is complete, as backup in case anything goes wrong or we need to reference something. Added this to inbox of outstanding tasks to revisit later

Tasks

  • Make list of things to migrate See tasks below
  • Migrate content (Done this via Obsidian)
    • guide index page See flowershow
    • guide index page images (Is there a way to do this that doesn't involve manually downloading each image from GitHub and importing into Obsidian?)
    • tutorial pages See tutorial 1 and tutorial 2. Tutorials 3 and 4 have not yet been written
    • tutorial pages images
    • howtos See links to 6 howtos at the bottom of the index page
@rufuspollock rufuspollock changed the title Migrate content from portaljs.org/guide Migrate content from portaljs.org/guide to this site Dec 19, 2023
rufuspollock added a commit that referenced this issue Dec 19, 2023
@elisapaka
Copy link
Collaborator

@rufuspollock I've transferred over the content of the guide from portaljs to makeitmarkdown/flowershow. Please review and let me know if anything needs changing. Some notes:

  • There is currently no 'home' or 'next' button on the howto/tutorial pages, but I thought we should think about how we want to structure the site first to avoid unnecessary work.
  • In the 'content' folder in makeitmarkdown, I've replaced the 'blog' folder with a 'tutorials' folder.
  • I have not transferred over all the images on the tutorial pages into the new assets folder. They are currently showing on flowershow but linking to the portaljs repo. I didn't know of a way to transfer the contents of the assets folder automatically from one repo to another in a way that they show up in the Obsidian files, and it would be a lot of work to do it manually for each image. Since we might re-do the tutorials and thus not keep these images, I'll hold off from doing this until we've confirmed what we're keeping.

@elisapaka
Copy link
Collaborator

elisapaka commented Dec 21, 2023

FIXED. PortalJS content mingrated to Make It Markdown on flowershow app.

@rufuspollock Closing this issue as migration is complete. NB images still link to the portaljs repo, so I don't want to delete anything on there just yet. I haven't migrated the images to the makeitmarkdown repo (except for the ones on the index page) because I imagine I'll redo the screenshots as we'll be using a slightly different method for the tutorials (and migrating them manually would be a lot of unnecessary work). But until I've finalised what I need I don't want to delete anything on portaljs, so I've marked the last acceptance item as WONTFIX. UPDATE 23-12-29: Added this to inbox of outstanding tasks to revisit later

@rufuspollock
Copy link
Member Author

@elisapaka remember when updating here i'd recommend updating the tasks with the resulting outputs as per https://lifeitself.org/tao/issues#completing-tasks (i.e. where you migrated stuff to) - we do this especially here because acceptance is high level.

Note also the acceptance updates are pretty general and don't tell me much. Better to have something like:

  • Migrate content from portaljs ✅2023-12-20 DONE: see next two items.
    • Identify content ✅2023-12-23 see the detailed list of items below in tasks section
    • Add the content ✅2023-12-23 migrated guide front page to front page LINK and each of the 2 complete tutorials to XXX and YYYY (link). Also migrated all 6 howtos - see links below [OR: see the detailed list of items below and update tasks below]

Instead of what we have:

  • Migrate content from portaljs ✅2023-12-20 DONE: see on makeitmarkdown, and on flowershow
    • Identify content
    • Add the content

@elisapaka
Copy link
Collaborator

elisapaka commented Dec 29, 2023

@rufuspollock Great, thank you for the feedback! I've edited the updates as per your suggestion.

@rufuspollock
Copy link
Member Author

Great. Last comment: we can easily forget the stuff about removing from portaljs and doing redirect so I would capture that somewhere like a new issue or an inbox for end of this phase of work and mention that in your issue completing comment.

@elisapaka
Copy link
Collaborator

@rufuspollock Perfect, I've added it here: #20

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants