openownership / openownership.beta Goto Github PK

Blog posts are particularly bad for this.

See: https://open-contracting.org as an example, and the pages it leads too. This is a need both to visually display where we work, but also structure the rest of the site such that we can link to country-specific information.

I think this would look a lot like the content that's currently in the boxes on the what-we-do page, so maybe we could merge it with that, given that we're adding some intro text to what-we-do in #6.

When I renamed news to latest I added a redirect for /news, however I didn't consider that google would have indexed paginated pages like /news/3.

We can add redirects through Netlify to cover this, so we should probably move /news to that system at the same time (currently it's a page in jekyll with a meta redirect header)

This is some feedback from our UX-review, it's less immediately actionable but is a commonly expressed need. Off the top of my head, I think it would be good to:

• Have one item for each resource with multiple language options, rather than separate items (in various orders) for translations
• Organise it into some sort of categories like 'basic info/policy positions/country specifics/tools'
• Have a general clean up - do we need our first mission statement there (for example)?

We'll start the first piece of work on the visualisation section of the site by creating content for the pages in markdown.

I think the best place for this to live is inside a new /_visualisation folder, with a visualisation.md to level page, but open to other suggestions

From @stevenday in reference to the scripts added in #33:

• scripts/update_framework.py
• scripts/framework_to_yaml.py

Assuming this is what we're working with for now, there's a few things I'd like to see:

On the setup

• Let's use python-dotenv, rather than a custom env.sh setup
• Can we get some documentation on how to run this in the README?
• We need a requirements.txt to pin the versions of these libraries and instructions to then run this from a virtualenv

On the code

• What happens if we rename a framework page/section? ideally I think we want to be able to redirect users to the new one, so we need a more persistent id, but that feels like a trickier task to ticket for later.
• Is the plan still to run this via a github action? Redirects notwithstanding, we'll need to remember to git rm everything before we run this and then git add afterwards, so that it picks up changes. (Presuming that's the way you're running it manually at the moment?)
• The code needs linting
• We should switch to f-strings where possible
• Other code improvements are noted in the review of #33.

This is part of the feedback from a UX review of the site and seems clear and actionable immediately, so I'm ticketing it here.

Keeping the site as it is, we could probably get away with using Algolia and it's Jekyll plugin to provide this initially for free.

• Transferring content from Google Docs → Markdown
• Embedding video into a section or body of a blog post
• Aligning images left or right with text flowing around them
• Required image sizes for each image field and how to quickly produce images for them