openownership / openownership.org-wagtail Goto Github PK

TBD

Backend

• Data (title and content?)

Frontend

• Styling

Designs

• Top level page within the Impact section
• SectionPage based on LandingPageType
• NOTE: Basically the same as Implement Section Page #22

• Backend

  • Make basic page and template
  • Add Streamfield for content
  • Allow layout choices in the cards
  • Hero #17

• Frontend

• Grid layout that fits the promotion needs of the cards in the streamfield blocks

• Content to use the card layouts #18

• TBD: Are there separate News Articles and Blog Posts? If so, do they differ in content and/or presentation? DECIDED: Separate sections. Assuming they look identical.
• Based on ArticlePage

Backend

• Basic pages and templates
  • Title
  • Publication date
  • Author
  • Publication type
  • Area of focus
  • Region specific (from the Countries/Regions used for map etc)
  • Sector
  • Content
• "Relevant articles and publications" See #58
• Breadcrumb navigation

Frontend

• Page layout
• Share component #33
• Relevant article and publications (cards from #18)

Backend

• Section title
• List sub pages (only next level)
• In pages like "Profile page", when visiting a page, it includes the name of the profile being visited #20
• Extra class/attribute if page is the current page
  Note: Items should be in the same order as they appear in the cards in the parent page/section

Frontend

• Style

Designs

• Top level page within the Implement section
• SectionPage based on LandingPageType
• NOTE: Basically the same as Implement Section Page #23

Backend

• Make basic page and template
• Add Streamfield for content
• Allow layout choices in the cards
• Hero #17

Frontend

• Grid layout that fits the promotion needs of the cards in the streamfield blocks
• Content to use the card layouts #18

On the Team Index Page (#15)

A Publication is a potentially multi-Page thing. Requirements:

• A title for the whole publication ("Beneficial ownership transparency of trusts")
• One or more pages, with a set order (these are linked to in a left-hand menu)
• Each page has a title ("Introduction", "Overview", etc)
• There is a cover image
• There could be a PDF to download
• There are "mandatory" sections on the front page: "Summary", "Learning outcomes", "Benefit & impact"
• They have the same meta data as other pages (Publication type, Area of focus, Region specific, Sector). Publication type can be one of "Case studies", "Briefings", "Consultations", "Guidance", "Reports".

I think it would make sense to have one Page type for the first page of the publication, with:

• title (The title of the report)
• page title (e.g. "Introduction")
• image
• PDF
• summary
• learning outcomes
• benefit & impact
• the meta data
• author(s)

Then it can have multiple child pages of a different Page type for subsequent pages that would only have:

• title (e.g. "Overview")
• body

The parent/child relationship will keep URLs for the pages nice like /implement/my-publication-title/overview/

• Backend

  • Make basic front page model and template
    • page title
    • image
    • pdf
    • summary
    • learning outcomes
    • benefit & impact
    • publication type
    • area of focus
    • region specific
    • sector
    • Next Page link
    • Add "Relevant articles and publications" See #58
  • Make basic child page model and template
    • They should be orderable (This can already be done in Wagtail admin)
    • Next Page link

• Frontend

  • Page layout
  • Left-hand nav #32
  • Share page #33
  • Style "Next page" link

One example design for a front page:

Backend

• Search functionality

Frontend

• Styling

TBD: how do we show the results?

• Single page with definition list that can be opened accordion style 🪗 🎶
• Under Implement section but I guess it's possible other versions could be used elsewhere?
• NOTE: Called "Category index" in Sketch

• Backend
  • Create Glossary items
  • Create Glossary page and template
  • Add body text block
  • Left-hand menu

Home page for the site

Page displaying all content tagged with {tag}

Backend

• Image
• Publication type
• Area of focus
• Region
• Sector
• Download

Frontend

• Styling
• Share #33

Designs

Backend

• Fill this data?

Frontend

• Styling

Designs

Backend

• Fill the data

Frontend

• Styling

Notes: Does this refresh the content on every interaction? Maybe for accessibility it should maybe have a "submit" button in the end of the filter and filter all at once?

Designs

• Some text followed by links to any Job description pages

Backend:

• Make page and template
• Title
• Intro
• Secondary navigation to all the jobs (similar to #32) except that this time it seems like the links are for the subpages of the careers page.

Frontend

• Page layout

• Colors
• Layouts
• Spacing
• Typography
• Logos
• Forms
• Pull quote
• Key notes (name TBD https://www.sketch.com/s/ddca6779-1055-4051-b7d6-ec699057b3e6/a/DP5gLzW)
• Highlighted bullet points (name TBD https://www.sketch.com/s/ddca6779-1055-4051-b7d6-ec699057b3e6/a/AxqkdDY)
• CTAs
• Tables

• A bit different to a blog/news Article (#24) (for one thing, the template displays a menu of sibling pages)
• There are two articles in the About section in the designs, presumably just demonstrating different possible content blocks.

• Backend
  • Make basic page and template
  • Add sibling page menu
  • Add content blocks
  • Add "Relevant articles and publications" See #58
  • Add "Examples of our work"

Two designs:

Backend

• Basic page (SearchView, Django view), URL, template
• Working form, send basic search results to template (no filtering) #40
• Add working filters #41
• Add sorting?
• Pagination #34

Frontend

• Page layout
• Show selected filters?
• Style sorting?

• Install wagtail-localise
• Add setting for list of languages (need to get list of languages supported)
• Ensure strings in models etc use gettext_lazy
• Ensure strings in templates use {% trans %}{% endtrans %}
• Add location switcher to templates/_partials/navigation.jinja

Backend

• Add snippet
  • Logo (check if can be optional)
  • External link
  • Blurb
  • Tag (Publication Type) (Doing them as snippets for now, with no publication type tag. PG)
  • Written by (check if this info is added manually)
  • Published in (check if this info is added manually)
• Add to the Theme listing page (taxonomy page)
• Add as a Stream Block that can be added to bottom of Section pages (see design for Insight)

Frontend

• Styling

Design

• Called "Themed Listing Page" in the spreadsheet.
• An example in the designs is "Insight - policy.jpg"
• Displays pages, of various kinds, within a section (Insight, Implementation, etc) that are in a particular Area of Focus, Sector etc.
• Originally listed as #26 but I'm baffled by these designs so we ended up with this twice.

• Backend

  • Area of focus tagging of pages
  • Sector tagging of pages
  • Management command to populate tags
  • Others? I'm not entirely sure how it's going to work...
  • View(s) that list tagged pages within a section
  • Add content fields to tags so stuff about the tag can be displayed

• Frontend

  • Page layout

Updated left-hand nav:

Earlier design:

• A Django View
• Using data from the tags (#9)
• List Pages tagged with that Country tag

Backend

• Make basic view (CountryView, Django view), URL, template
• Rich text blocks including "detail block" #39
• Send country data to template
  • Name
  • Static map image?
  • Last updated
  • Work by No longer happening
  • Consultants details
  • Commitment
  • Implementation
  • #61
• Send related pages to template See #58

Frontend

• Page layout
• Map (static image?)

Annotated image of where the data comes from

• The top-level section page under About
• Automatically lists the child pages beneath it

Backend

• Basic page and template
• Hero #17
• Send child pages to template

Frontend

• 3 col layout for the streamfield block
• Card layout #18

Most top-level section pages are like SectionPage, but this behaves more like SectionListingPage:

• Will be imported from data stored in Notion (see #7)
• Use Notion-sdk-py
• Store data about each country from Notion as fields on the tag
• Additional fields for anything on a Country Page (#8) that's not in source data

Frontend tasks and questions

• Investigate what map should be used here. Svg?
• Clarify what map/borders is OO comfortable with.
• Where does the data that populates the map comes from?
• What is inside the tooltips and on click where does it go to

• Index listing all the child pages below it

• Backend
  • Create basic page and template
  • Add list of Team Profile pages
  • Add left-hand menu
• Frontend
  • Style Team Profile cards

This is a child page of #29
Backend

• Back to careers menu
• Title
• Publication date
• Application deadline
• Intro
• Content
• Publication type
• Area of focus
• Location
• Sector

Frontend

• Page layout
• General rich text styles #30
• Share page #33

Designs

Like the one in rcew - to move all the stuff from the Settings menu into a single SiteSettings object with tabbed interface in admin.

• A map that (I assume) links to individual Country pages

Backend

• Make basic page and template
• Title
• Intro
• List countries
• Supply any further data needed for map? #35 and #36
• Data for accordion #37
• Search functionality #38

Frontend

• Page layout

• Backend
  • Email signup form
  • Bottom menu
• Frontend

• Top-level page within Insight
• SectionPage based on LandingPageType

Backend

• Make basic page and template
• Add Streamfield of content
• Hero #17

Frontend

• 3 col layout for the streamfield block
• Card layout #18
• Press link block #19

Backend

• Fill content

Note: can include anything (e.g. tables)

Frontend

• Styling

Designs: Component design and component in action

Backend

• Render pages

Frontend

• Base styling
• Add aria-current

Backend

• Title
• Intro (with rich text)

Pages where it can be added:

• All 1st level pages except (search and global register)

Designs for front-end

Languages currently used on the old site:

English
French
Spanish
Bahasa Indonesia
German
Russian
Armenian

• A single job posting
• I'm assuming the "Apply" button just links elsewhere...? (YES)

Backend:

• Make basic page and template
  • Breadcrumb/navigation
  • Title
  • Published date
  • Deadline
  • Publication type
  • Area of focus
  • Location (CharField, no link)
  • Sector
• "Apply" link/CTA
• Add "Relevant articles and publications" See #58

Frontend

• Page layout
• Share page #33
• Style "Apply" link page

• TBD - whether there are separate Blog posts and News articles. And if they're separate are there separate index pages. DECIDED: Separate sections and pages.
• NOTE: We're not making the list sortable, which was shown on initial designs.

Backend

• Basic pages listing articles/posts
  • Title
  • Intro
• Include two secondary navigations: One for all of the insights and another for the current streamfield content. Relates to #32

Frontend

• Page layout
• Include cards #18

Backend

• Basic page (HomePage Wagtail page, based off BasePage), URL, template
• Add Hero
• Add stream field content
  • Pick any page
  • Latest content in a section

Frontend

• Page layout
• Grid layout that fits the promotion needs of the cards in the streamfield blocks
• Content to use the card layouts #18

Backend

• Template
• Search input field to work

Frontend

• Style

• Generic content page
• Only shown as being used inside the About section, but wouldn't surprise me if it's used elsewhere (Terms? Privacy?)

Backend

• Generic Content page
  • Title
  • Body content
  • Block with other pages (confirm is manually picked). Confirm how choice of card layout happens (#18)
• Side menu as used in About version (#32)

Frontend

• Page layout
• Cards
• Body elements #30

Two designs:

Users need a way to switch between languages.

• Showing an individual person on the team and "relevant content"

Backend

• Page showing basic info
• Name
• Job Role
• Regional experience (from the list of Countries/Regions) (can be more than one)
• Specialist area (i.e. Area of Focus taxonomy)
• Location
• Contact
  • Email
  • Social media (Twitter, Github, LinkedIn)
• Intro/bio
• Block with body text
• Send "relevant articles and publications" to template (not sure what the connection is yet. authorship?)
• Secondary navigation (should include profile name in the current page) #32

Frontend

• Page layout
• Profile section
• Relevant articles and publications (card layout to be done in #18)

• Markdown into Pages
• PDFs, .docs, media, etc

• Backend
  • Logo
  • Top menu (top menu shows child pages in the mobile menu)
  • Language switcher #50
• Frontend

Backend

• Choose from existing content
• Choose between horizontal or vertical layouts
• Title
• Blurb
• Tags (optional)
• Author (optional)
• Date (optional)
• Image (optional)

Frontend
Designs: page 1 and page 2

• 2nd level page within a section (maybe only Insight and Implement?). e.g. "Policy" or "Banking Implementation"
• Lists all the content items (only publications? or other things too?) below it
• NOTE: I think we're leaving off the ability to sort the content items which is shown in the design

Backend

• Make basic page
• Title
• Intro (or is Intro part of the body?)
• Body
• Choose a tag (from which the content items are automatically pulled (use cards layouts #18))
• Secondary navigation. Relates to #32
• Pagination #34

Frontend

• Page layout

(Note updated left-hand nav in comment further down)

• Import into the tags in #9 using Notion-sdk-py
• Will need to run periodically to fetch fresh data