How we built the new OpenSpending.org with PortalJS (dev oriented)

[rufuspollock]

Dev oriented overview/tutorial of how we build new OpenSpending.org with PortalJS - follow up and complement to #882

Acceptance

Status: :heavy_check_mark: DONE. See https://www.datopian.com/blog/the-open-spending-revamp-behind-the-scenes and https://portaljs.org/blog/the-open-spending-revamp-behind-the-scenes

• [x] Mention background blog post - ie https://www.datopian.com/blog/the-open-spending-revamp
• [x] Link to github repo
• [x] Explain key items e.g.
  • [x] Where we stored data
  • [x] It's format
  • [x] How we pulled that into the frontend
  • [x] Repeat: where you can find the code, get help etc
• [x] Some nice screenshots including of code

Tasks

• [x] Bullet point outline
• [x] Tidy
• [x] Post 2023-10-16 :heavy_check_mark: FIXED. See https://www.datopian.com/blog/the-open-spending-revamp-behind-the-scenes and https://portaljs.org/blog/the-open-spending-revamp-behind-the-scenes.
• [ ] Promote

[demenech]

First version created: https://hackmd.io/I-p14Le8T5-p3w7rR-YfoQ?both

Waiting for @popovayoana 's input

[demenech]

First version created: https://hackmd.io/I-p14Le8T5-p3w7rR-YfoQ?both

Waiting for @popovayoana 's input

Yoana provided some feedback in an internal document. We'll post this to the Datopian blog and to the PortalJS blog tomorrow.

[popovayoana]

@demenech @rufuspollock left comments in this file https://docs.google.com/document/d/1qQ7sc163A9UOPGnDJaI5Z2_kuVtl_kE-gXSwaWbjBwQ/edit?usp=sharing but sharing them here as well for visibility and thoughts exchange ; )

situation is: we want this article to be posted on 2 blogs (Datopian and PortalJS). We have two options:

1. repurpose content = ideally, we don't want to copy-paste the content (not good for SEO). it's better if we tailor the content slightly to suit the audience of PortalJS e.g. focus more on the technical aspects, diving deeper into how PortalJS contributes to the OS project etc. (I've provided a general outline of how we can tweak it in the file above). however, if we don't want/don't have the capacity to do that, we can simply:

2. cross-post we can cross-post by copy-pasting the content but in that case, we should think about the SEO impact (search engines generally prioritize original content as you know, so duplicate content could result in a lower ranking for both sites. to mitigate this, we should: 2.1 use canonical tags to indicate the original source 2.2 add note at the beginning or end stating: "This post was originally published on [XXX Blog]. 2.3 do phased rollout: we can publish first on the Datopian blog (if we want this to be considered the "original source"), wait several days to allow search engines to register the content, and then publish on portalJS Blog 2.4 use different meta descriptions and titles to distinguish it from the original

[rufuspollock]

@popovayoana do the simplest thing possible which is simple xpost imo.

[demenech]

Both articles were posted. See See https://www.datopian.com/blog/the-open-spending-revamp-behind-the-scenes and https://portaljs.org/blog/the-open-spending-revamp-behind-the-scenes. @popovayoana do you have a plan to promote it?

[popovayoana]

@demenech yes, will share on social media

[rufuspollock]

FIXED 🎉

[rufuspollock]

@demenech can you update acceptance with links 😄