Description
On ckan.org link text such as "Read more", "Read >", "View profile", "Visit site" is added at the end of the short teasers for blog posts/articles. Using links like "Read More", "Click Here", etc is considered a bad practice in general (WCAG 2.0 Success Criterion 2.4.4 Link Purpose (In Context) (Level A). And althought on ckan.org the scenario is not always connected with lack of context, these link texts are still unnecessary. It is not visually appealing, it adds clutter and disturbs readability. Not to mention that there's general inconsistency - on some pages we have them in blue, on some pages - in red, with/without ">".

Examples

Home page (Read more)

Features page (Read more >)

Showcase page (Visit site)

Solutions > CKAN for Government page (View profile)

Support > Commercial support (Details >)

Blog page (Read >)

Events page (Read >)

This is generally a better approach since the link actually gives context but since we aim at universal style and consistency, it should also be removed

Expected behaviour
When I see a text block/short teaser for blog post, I want to be able to open it by clicking anywhere on it - e.g. I want to be able to open it if I click on the title/avatar/image/icon) so that I don't need to click on "Read More", "Read >", etc.

Acceptance

• all "Read more", "Read >", "View profile", "Visit site" links from the website are removed and substituted with ability to open the blog/article by clicking on its title and avatar.
• clicking on the title or avatar of a text block/short teaser of a blog/article opens the link

Tasks

• Remove all "Read more", "Read >", "View profile", "Visit site" links from the website
• Make sure alternative ways to open the link are enabled e.g. make sure clicking on the title a/o avatar of a text block/short teaser of a blog/article opens it

Please remove data.norge.no from the FAQ (under "Who uses CKAN"), as it is not using CKAN.
https://ckan.org/faq/essential

https://twitter.com/livarb/status/1641381970952220672

Description

When attempting to log in at CKAN's main site (https://ckan.org > Log in), the server consistently returns a 502 Bad Gateway error.

Steps to Reproduce

1. Navigate to https://ckan.org/ and click on 'Log in'
2. Observe the 502 Bad Gateway error upon redirection to https://ckan.org/accounts/login

Description
We might want to consider having a call to action "Star us on Github" somewhere on the website. Not sure about the proper position. My suggestions would be:

1. We either change "View on Github" with "Star us on Github" or
2. We put it somewhere at the bottom e.g. next to the social media icons

Expected behaviour

On the page https://ckan.org/features/datastore the link to the Data explorer extension is wrong, missing part of the domain (ckan.org): http://docs./en/latest/maintaining/data-viewer.html#data-explorer

Describe the bug
On Community support page "Speak with us" snippet differs from the same snippet on Home page. How it differs: on Community support page "Speak with us" consists of email box (which we don't need) and a "Schedule a meeting" button.

Expected behaviour
All "Speak with us" snippets must be the same across all pages. The right one is the the one we have on Home page. Flow: When clicking on "Schedule a meeting", a contact form pops-up (no need of email box).

Description
This is a major, quite big fix but we should slowly start thinking about it. The events page needs a redesign. Currently it's no different than a regular blog post page - it's user-unfriendly, it looks poor and doesn't give a feeling of a platform.

What we imagine is something like:

• https://www.ataccama.com/digital-conference
• https://opensourcelive.withgoogle.com/events/security/watch?talk=opening

Expected behaviour
When visiting ckan.org/events page, I want to see a visually appealing event platform like this one: attaccama.com with the following structure:

• an attractive menu on left side bar that consists of:
  • live streams - where we have the last event video embedded with a short description alongside an option to go the previous ones using the arrows (see example: live streams)
  • events - where we have all events in a nicely formatted way with title, duration, thumbnails of the speakers, etc. (see example: events)
  • archive - all past events (see example: archive)
• ADDED Nov 2022:
  • calendar #25 (note that this has low priority because section Upcoming events solves the problem for now)
  • trending sessions/highlights - where we have 3-4 videos selected by site moderator as highlights (reference: https://business.adobe.com/summit/adobe-summit.html)
  • search bar
  • filtering of events by category/use case -(e.g. internal/external data catalog, gov/enterprise etc)
  • "join our next webinar" snippet (at the end) - where users can subscribe for email updates about future events - that should be the webinar form #89 (reference: https://www.ibm.com/events/think/)

When I click on a certain event e.g. ckan.org/events/ckan-monthly-live-october-4, I want to see a subpage with the following structure:

• embedded YouTube event video - video should be at the beginning like a hero image like on Google Open Source Live: https://opensourcelive.withgoogle.com/events/security/watch?talk=opening (see example: video)
• description below the video
• meeting agenda with timestamps and speaker thumbnails - like the one on Google Open Source Live: https://opensourcelive.withgoogle.com/events/cdapday (see example: agenda)
• ADDED Nov 2022:
  • filtering of events by category/use case -(e.g. internal/external data catalog, gov/enterprise etc)
  • "join our next webinar" snippet (at the end) - where users can subscribe for email updates about future events - that should be the webinar form #89 (reference: https://www.ibm.com/events/think/)

references

example: left side bar:

example: live streams

example: events

example: archive

example: video

example: agenda

Under the showcase section (https://ckan.org/showcase), there are some information currently misleading.

The australian government now uses a solution called Magda, which is open-source and developed for them. Therefore https://data.gov.au/ does not show a ckan instance.
The canadian goverment showcase should also point directly to https://search.open.canada.ca/en/od/, even when it does not seems like a classical ckan instance. The main site is probably not implemented in ckan and therefore irrelevant.
The U.S. catalog (https://catalog.data.gov/dataset/) seems also be down for some reason, but this should hopefully only be a temporary issue as the main site still links to the catalog.

The enterprise sites are mostly up and running, but the lego showcase, despite being really cool, does not bring any benefit when they only looked into.

So maybe the showcases should be updated and here are possible alternatives:

• https://healthdata.gov
• https://data.gov.uk
• https://data.nhm.ac.uk/ (Very cool data portal)
• https://data.govt.nz/
• https://catalogue.data.gov.bc.ca/
• http://www.geodata.gov.gr / https://data.hellenicdataservice.gr
• https://www.dati.gov.it (maybe)
• https://ridl.unhcr.org/

Description

There is an issue with the date management on the CKAN Blog where the "published on" date of blog posts is automatically updating to the current date whenever an article is edited. This behavior can lead to confusion, as seen in the case of an article about a UI designer: https://ckan.org/blog/call-to-ui-designers-front-end-developers-ckan. Originally published months ago, a recent edit (today) caused the publication date to display as today's date, potentially misleading readers into thinking the content is new...

Note: The issue is particularly problematic for posts that are time-sensitive or related to events and announcements. We need to have some clear distinction between 'created date', 'published date', and 'last edited date'.

Steps to Reproduce

1. Edit an existing blog post on the CKAN Blog that was published at an earlier date
2. Save the changes and view the post on the blog
3. Notice that the "published on" date reflects the edit date, not the original publication date

Expected Result

Editing a blog post should not change its original "published on" date. The date should remain as the initial publication date to avoid confusion and maintain the chronological integrity of the blog.

Actual Result

The "published on" date of a blog post changes to the current date whenever the post is edited, leading to potential misinformation regarding the timeliness of the content.

Describe the problem
Our contact form is notorious for collecting spam from bots. Most of the messages that come are spam.

Suggestion
Adding Google Recaptcha (wagtail-django-recaptcha package) or something to the contact form to reduce the number of fake form submissions.

Description
On the old website there was a page with CKAN instances (ckan.org/instances) which no longer exists. We want to revive it.

Expected behaviour
When visiting ckan.org website, one should be able to

1. see a list of all CKAN instances
2. add their instance to the list (after moderator approval)

Ideally this would be a subpage of the Showcase page - ckan.org/showcase/instances (although open to other suggestions).

Description

Our blog currently only supports centered images with large margins on both sides. This layout restriction leads to a less immersive visual experience. We want to enable full-width images in our blog posts (in addition to the current centered one). These images should stretch from edge to edge, without any padding, filling the entire width of the post container.

Details

Full-width style layout

• Description: Images span the full width of the blog post container (only images, not body text)
• Characteristics:
  • No padding around the main wrapper
  • Images extend edge-to-edge within the blog post container
  • Responsive design to ensure proper scaling across various devices

Consideration for Image height:

We need to determine an appropriate height limit for these full-width images to maintain aesthetic balance and ensure they don't dominate the screen space excessively. Potential options include setting a maximum height in pixels or a percentage of the viewport height.

Visual comparison

How it looks now

How we want the additional layout to look like

Description
Although users feel a deep-rooted connection between the blue underline and clickability, the blue underlined hyperlink is a relic from simpler days and looks outdated. The interruptive nature of the blue underline has been shown to impede readability. Not only does the underline disrupt the natural flow of the gaze over text (according to a Hamburg study), but it also cuts up the low-hanging letters and makes them harder to decipher. This negative impact on readability led Google to ditch the underlined link in 2014, citing a desire to "improve readability and create an overall cleaner look." Google’s decision certainly fits into the wider trend for interface minimalism and flat design, which sit uneasily with the blue underlined hyperlink.

According to web accessibility guidelines (WCAG 2.0), if links are not underlined, it is required that link text must be discernable from body text by at least a 3:1 contrast ratio.

Acceptance

• hyperlink text is red and with no underline
• all visited hyperlinks change their colour (as google search does - in their case from bright blue to purple-ish colour)
• all hyperlinks change their style on mouse-over, emphasizing that they are clickable

Tasks

• remove the underline from all hyperlinks
• change colour of all hyperlinks from blue to red #ED5248 (as the red in the logo)
• make all visited hyperlinks change colour to light red #EF6D6A
• make all hyperlinks change style on mouse-over:
  • 1st option: colour changes to dark red #B73C39
  • 2nd option: underline appear (like on ckan.org/features - see example below)

example

Description

When attempting to publish content on the CKAN.org Blog, a 502 Bad Gateway error occurs, preventing the publication of the content. This issue has been persistent for the last two weeks and appears to be content-specific, as tests with an empty page do not trigger the error. Specifically, I am unable to publish this article: https://ckan.org/admin/pages/367/edit

Note: This issue is critical as it entirely blocks the ability to publish new content on the CKAN Blog.

Steps to Reproduce

1. Navigate to CKAN Blog Admin Page https://ckan.org/admin/pages/7
2. Attempt to publish the blog post called "Product Market Fit for CKAN 2023": https://ckan.org/admin/pages/367/edit
3. Observe the 502 Bad Gateway error upon attempting publication
   Result: A 502 Bad Gateway error is presented upon attempting to publish content-filled blog posts, whereas empty posts get published without issue.

Environment

• Browser and Version: Chrome Version 118.0.5993.120 (Official Build) (64-bit)
• Operating System; Windows 11 Pro

Below is the link for your reference:
https://huntr.dev/bounties/73b09195-7c98-405f-a6d3-241439faf97b/

Description
We've launched a CKAN Monthly Newsletter and would like to invite people to stay connected by subscribing through an easy-to-use sign-up form on our website.

Expected behaviour
The newsletter form should be placed in prominent locations on the website, including the footer, blog page, on a dedicated subpage, e.g. ckan.org/newsletter and potentially as a pop-up. The form should consist of a minimal number of fields, such as a name and an email address. The form should be designed to be user-friendly and accessible, using clear and concise language, and ensuring that it can be used with keyboard-only navigation.

It's important to have a dedicated subpage, e.g. ckan.org/newsletter, where users can learn more about the newsletter and subscribe. Having such a subpage will help us share the newsletter on social media and invite them to subscribe. This subpage should include information about the frequency of the newsletter, the type of content it will contain, and the user's ability to opt-out at any time. Also link to Privacy Policy is a good practice but I am not sure of we have one...

Something to think about
For an additional level of security and to prevent spam sign-ups, we might want to consider using a double opt-in process to confirm a user's subscription. This would involve sending a confirmation email to the user, containing a link that they must click to confirm their subscription.

• Here's a prototype of the newsletter sign-up form: https://www.figma.com/proto/iDfXzrsgbDSuRxOLTc9CCa/CKAN-Monthly-Newsletter?node-id=4%3A23&scaling=min-zoom&page-id=0%3A1
• Text: Ready to stay ahead of the curve? Join our CKAN Monthly Newsletter and get the inside scoop! From new developments to upcoming events and everything in between, you'll find it all here!

Placement
Ideally, we'd have several sign-up forms (see image references below)

1. In the footer
2. At the beginning of the Blog page
3. As a pop-up
4. On a dedicated subpage ckan.org/newsletter

Acceptance

• "Sign up for our newsletter" form implemented on website
  • In the footer
  • At the beginning of the Blog page
  • As a pop-up
  • On a dedicated subpage ckan.org/newsletter
• Recaptcha or another anti-spam alternative is implemented
• Subscribers list is integrated with Mailchimp or another marketing tool

References

In the footer

Not sure - up to you. Probably right side is the only option.

How should it look like: It should be very simple, one line.

At the beginning of the Blog page

As a pop-up

On a dedicated subpage ckan.org/newsletter

See here: https://about.google/intl/ALL_us/email-newsletter-sign-up/

• Description
  We now have 5 types of subscription snippets:
• speak with us with a pop-up contact form (Home page) this one is ok
• speak with us with an email box, no pop-up contact form (Community) done: changed to a pop-up one
• subscribe to get new posts (Blog) done: removed
• join our next webinar (Home page) this one is okay
• schedule a chat (CKAN for Government) TODO: change to a pop-up one
• schedule a chat (CKAN for Enterprise) TODO: change to a pop-up one

Expected behaviour
We want to reduce the types of subscription snippets to these two:

• speak with us with a pop-up contact form
• join our next webinar

E.g. https://ckan.org/events/ckan-monthly-live-june-11 looks like a meeting that happens on "June 11". Can we remove the month name from the slugs for these posts?

Describe the bug
When I am trying to publish a new event through Left Menu Bar >> Events >> Add event post page (https://ckan.org/admin/events/eventpostpage), the event does get published but this is not reflected on the Events page.

• E.g. I've published a post re the first CKAN Monthly Live
  • it is there: https://ckan.org/events/ckan-monthly-live-1-june-meetup
  • but doesn't show up here: https://ckan.org/events

Steps to reproduce
Just try to add new event through https://ckan.org/admin/events/eventpostpage/ and see if it shows up here https://ckan.org/events

Expected behavior
I expect whatever I publish under "Events" to be reflected on the Events page.

Description
This is connected to issue #15 which was FIXED. For more context, please see issue #15. In brief, we reduced the steward forms to only one with a pop-up contact form (where users fill out details about their reasons of contact). The problem is we still receive some steward form subscriptions without any other information in our inboxes which doesn't make sense.

See images below

Expected behaviour
We want to receive only forms that come along with the submitted contact form:

Description of the problem
Hyperlink text act as if I've clicked on it when I have not clicked - some text is light red, and some is dark red on creating the page (no clicks). This is a new bug that came these days. See screenshots:

Description
All pages on the blog page are linked to page 1. When clicking on page 2 and the domain shows https://ckan.org/blog?page=2 or page 3 (https://ckan.org/blog?page=3), it directs you to page 1. Browsers the bug is found in: Chrome, Mozilla, Internet Explorer.

Expected behaviour
Pagination should work properly so that each page corresponds to the content.

Description
There is some problem with the way subscription forms work - I don't know at what point it became messy but it is messy.

1. We don't receive the contact entries in Wagtail. We receive them in our emails but they are not recorded in Wagtail. (tested right now - I got an email but nothing in Wagtail)

2. We receive the new webinar form for both people that contact us and people that subscribe to the webinar.

Expected behaviour

1. We want all forms (contact, webinar, newsletter) to be connected to Wagtail and integrated with MailChimp.

2. We want to receive the contact form when people that contact us and the webinar form for people that subscribe for the webinar.

Description
We have created a brand new company page on LinkedIn. We want the social media links on the footer of the website to be updated. The current link to LinkedIn redirects to CKAN Association LinkedIn Group - https://www.linkedin.com/groups/6795833. We want to add link to CKAN LinkedIn Company Page: https://www.linkedin.com/company/80804045.

I guess we can either have two LinkedIn icons - one pointing to group and another to company page or just one that leads to the company page.

Description

Experiencing a 502 Bad Gateway error when a. attempting to view a newly published article on CKAN's blog and b. when trying to create a new article. However, all other existing articles on the blog are accessible, suggesting that the issue might be localized to the publishing process or to new content specifically.

Steps to Reproduce

1. Navigate to the new article URL https://ckan.org/blog/call-to-ui-designers-front-end-developers-ckan
2. Observe a 502 Bad Gateway error
3. Try to create a new article through the CMS
4. Again, observe a 502 Bad Gateway error
5. Browse other existing articles on the CKAN blog
6. Note that these are accessible and render as expected

Description of the problem
Atm there's no integration between our webinar/contact forms and the email tools we use. Everything happens manually. We want to automate the process.

Expected behaviour
When someone submits a webinar/contact form, we want them to automatically be subscribed to the relative Mailchimp email list.

Suggestion for solution
Mailchimp Integration Feature: https://docs.coderedcorp.com/wagtail-crx/features/mailchimp.html

Description
We have tags for the blog posts but it is impossible to filter them by tag - tags are not clickable.

Expected behaviour
When clicking on a blog post tag, we want to be able to see all blog posts with this tag. Now this works only when you click on the author - it gives you all posts written by this author.

Please update my job title on the Community page to "Developer at Government of Canada"

I don't think anyone cares which department I'm working for, and that department changed a few years back anyway :-)

Description

The search functionality on the CKAN.org blog is not operating as expected. Queries are either returning no results or incomplete results, even though relevant articles are present on the blog.

Examples of the Issue:

Query: "POSE"

• Expected result: At least three articles related to the POSE project
• Actual result: No results are found
• Reference link: https://ckan.org/blog/search?query=POSE

Query: "digital"

• Expected result: An article "CKAN is now a Digital Public Good"
• Actual result: Only one result pertaining to the civic data lab, omitting other relevant articles
• Reference link: https://ckan.org/blog/search?query=digital

Query: "Digital Public Good"

• Expected: The article titled "CKAN is now a Digital Public Good"
• Actual result: Only one unrelated result about civic data lab
• Reference: https://ckan.org/blog/search?query=Digital+Public+Good

Screenshots

POSE

digital

DPG

Description
Blog page >> There is no information about the author of the blog posts.

Expected behaviour
When clicking on the name of the author under the article we want to have a short description about this person (like on the old ckan.org). It might be fetched from GitHub profiles for example. The description could be above/beneath the list of articles by this author - up to the designer.

I imagine something really simple e.g.:

1. name + role (like on Google Blog)
   

2. picture + name + role + short description
   

Describe the problem

1. email box (id = "blogform") generally adapts nicely to different viewports but doesn't adapt nicely to iPad viewport (1024x768) - email box is too close to the text
   

2. email box not justified with text (kind of tries to escape to the right) - Iphone (640x960)
   

3. social network icons too close to text (Iphone, 640x960)
   

Expected behaviour

1. email box to adapt nicely
   

2. aligned with text like this:
   
3. enough spacing between text and icon

Description
We want to have a calendar on Events page so that dates for events (CKAN Monthly Live, CKAN tech meetups, and hopefully more) can be listed publicly - with a little info about each event.

Expected behaviour
When landing on Events page one should be able to easily comprehend: types of events we're having, dates, event details.

Details
I imagine it something similar to the pictures below. A normal calendar widget with certain dates highlighted. When clicking on the highlihted date, the user sees more details about the event. The mechanism could be different, this is just one option.

For a beginning, an easier thing we could prob do is just to find a way list regular events on Events page

• CKAN Monthly Live - every third Wednesday of the month at 1 PM UTC (+meeting details)
• CKAN Tech meetings - every Tuesday and Thursday at 1 PM UTC (+meeting details)

Description
There's no special editable field for blog post author (in admin panel) which leads to: the moderator that publishes the article is marked as the author which might not be the case.

Expected behaviour
When posting a blog post, we want to have an editable field for author so that we can write the name of the real author.

This issue proposes some changes to the visual narrative and content of the homepage, as it is beneficial to CKAN's narrative to highlight that it was recently recognized as a Digital Public Good by the DPGA.

Update header

• Replace CKAN logo (with the DPG badge)
  Source file: https://drive.google.com/open?id=1MpqHW6IlvK6o_eQI_YXSrAHGWw-quPgA&usp=drive_fs

Expected result:

Update footer

• Add OKFN logo (source file: https://drive.google.com/open?id=1YTgml6HIgRh3vr-noy0CJO-hC8MeawBb&usp=drive_fs)
• Move and centralise the newsletter section at the bottom

Expected result:

Update contents

• Add DPG section
  Place it between "Powered by CKAN" and "Join our next webinar" sections with the following content:

Headline: CKAN is now a Digital Public Good
Text: CKAN has been added to the Digital Public Registry and is now officially recognised as a data management system helping tackle 9 of the 17 Sustainable Development Goals (SDGs) of the 2030 Agenda set by the United Nations (UN).
Image: https://drive.google.com/open?id=1Mqb0M7YfhsimDSnXEMiRVhDpuqx63xjv&usp=drive_fs
Button: Learn more
Button link: https://blog.okfn.org/2023/06/15/ckan-is-now-a-digital-public-good/

Expected result:

Here's how the entire homepage should look like after the changes:

Add a README file with:

• Description of the repository
• Instructions for a local development install
• License (AGPL)
• BONUS: Instructions on how to deploy changes

For instance, the date of the last post about the security patch releases appears wrong, as I reused an earlier draft:

https://ckan.org/blog/get-latest-patch-releases-your-ckan-site-october-2022

https://ckan.org/admin/pages/307/edit/

It appears the UI shows the creation date, not the publication one.

Description
We have only three options to align an image in text: full width, left-aligned, right-aligned:

If left-aligned, then no spacing between text and image

If right-aligned, then no spacing between text and image

If full width, image does not go full width (even if the image resolution allows it)

Expected behaviour
When aligning an image, I expect different align formats to work properly so that:

• full width format positions the image in full width
• when left/right-aligned, there's a proper spacing between text and image
  I also expect to be able to position the image right in the center.

Acceptance

• "align to center" function is enabled
• enough spacing between text and image is added
• full width alignment works properly

Tasks

• Add space around aligned images (between text and image)
• Add "align to center" function for image positioning
• Fix full width format

The idea for implementing Google Analytics was to add combine it with Google Ads seamlessly when promoting CKAN. This topic is closed for now and it's no reason to keep non-friendly to open-source big company product.

On the other hand we need web analytics. The topic is a bit tricky as not every system does the job right. I used PostHog (https://posthog.com/) for A/B tests on the web and was impressed by it:

• It's open-source and free to use (1,000,000 events in free version is probably 10 times more that we'd use)
• It offers solid set of tools
• It's comfortable to use both on dev and UI side

This change might likely prompt to further website changes to refine call to actions, messaging we have and to refine the informational purpose of the website through testing copy and changes.

Update website through experimentation is a healthy way to deliver more value to visitors by understanding them better.

Description
On ckan.org/showcase there is a quote that interrupts Government section and shouldn't be there.

Expected behaviour
The quote should be at the beginning, at the end or between Government and Enterprise sections.

The CKAN blog does not refer to an RSS/Atom feed, which seems reasonable given nothing in its source provides one.

Feeds help readers like me track new articles without needing to regularly visit many different sites. Given how good CKAN's support for syndication is, it would be great to see your blog provide this too.

The task is to add the code of an online chat so incoming users can ask questions and engage with us.

When you're ready to add the code, please ping me, I'll get a subscription and will provide the code.

I realise that this isn't the best place to report this problem, but as your "Contact Us" form is broken I can't contact you about it easily..

When I follow the "Contact Us" link at the bottom of https://ckan.org/ a form appears. I fill in this form, including telling you that I'm not a robot, then click the "Submit Query" button. I have seen a "Bad gateway" page earlier today and now I see the following error:

Forbidden (403)

CSRF verification failed. Request aborted.

More information is available with DEBUG=True.

Describe the bug
Hyperlinked text fails to resize to 16px on several resolutions (I'm guessing above max-width: 1024px, under 1024px is okay) and thus is not in sync with the rest of the text.

Tested on several resolutions, all above 1024px width look the same:

• Netbook (1280x800)
  

Expected behaviour
All text should be the same size regardless of the resolution:

Describe the problem
Atm if someone wants to subscribe to a webinar, the only thing they have to do is drop their email in the email box. The problem with this is that a. we're not collecting enough information (e.g. subscribed/unsubscribed for future events, interests, etc) and b. we're collecting a lot of spam.

Acceptance criteria

• the form is implemented on website
• user receives a thank you message on screen after submission
• the webinar submission is added to https://ckan.org/admin/contact/email
• the form is integrated with Mailchimp

Analysis

Suggestion

1. Add a new pop-up form, similar to the "schedule a call" one (see form suggestion below)
2. Add additional Recaptcha

Current flow:

insert email

once inserted - thank you message

How we want the pop-up form to look like:

marketing permission alternative of the checkboxes (in this case question should not be required)

Text:

1. Title: CKAN Monthly Live
2. Subtitle: I would like to be invited to the next CKAN Monthly Live meetup. Note: Any information you provide will only be used for inviting you to the CKAN meetups (and, if you opt-in, letting you know about CKAN news and updates). It will not be shared with any third parties.
3. Your Email* (required)
4. Your Name* (required)
5. Your Company/Organization* (required)
6. Are you interested in the technical or non-technical aspects of CKAN? (not required) | checkboxes: - technical/non-technical/both
7. Would you like to suggest a topic for one of our future meetups? (not required)
8. Would you like to present on CKAN Monthly Live? What topic would you like to talk about? (not required)
9. Any comments or something you'd like to share? (not required)
10. Marketing Permissions
    10.1 Would you like to automatically be invited to future meetups on CKAN Monthly Live? They happen every third Wednesday of the month at 1 pm UTC.* (required) | checkboxes: yes/no (or just a tick like the one in the contact form)
    10.2 Would you like to be informed about other CKAN news and updates?* (required) | checkboxes: yes/no (or just a tick like the one in the contact form)
11. SUBMIT
12. Thank you message after submission: Thank you for your interest in CKAN Monthly Live! You should receive an email with more information shortly.

Description
When publishing a tutorial/guideline/how-to article, we obviously want it to be user-friendly and properly formatted so that it is easy to use and read. We want to have a syntax highlighting feature.

Suggestion
Install a wagtail plugin like https://github.com/FlipperPA/wagtailcodeblock

Description
Corporate blogs are "de rigueur" in the social and content marketing worlds as vehicles to build authority, share insights, foster community and provide value. We’ve already got the basics down, but we can take it to the next level.

What's not working on our Blog page in my opinion

• Navigation
  • Problem: No clear navigation (for readers visiting our blog, clear navigation can keep them browsing the site instead of bouncing if they don’t see the information they need right away... currently, the structure of the blog page doesn't allow for quick navigation)
  • Solution: Implement categories (one easy way to add clarity would be e.g. adding “Categories” widget on the sidebar)
  • Solution 2: Insert a search bar (updated)
• Sharing
  • Problem: No sharing option (currently readers cannot share directly blog posts on social media)
  • Solution: Add "Share this" option (Tweet this, share via Facebook, LinkedIn)
• Readability
  • Problem: Some of the articles are too long and might be overwhelming
  • Solution: Use pull quotes (wherever possible of course) to break up long blog posts to make them more visually appealing
• General look (this is not quick fix but major one)
  • Problem: Design looks jejune, not juicy
  • Solution: Redesign so that it looks juicier (references: https://blog.google, https://www.thinkwithgoogle.com)

Tasks

• decide what's possible in terms of capacity - quick fixes mentioned above or major fixes (like general look)
• categories
  • create a list of categories we want on the blog (note they should be different than tags)
  • come up with a navigation solution - how are we going to implement the categories? is it gonna be just a side widget or bigger redesign?
• implement "share this" option
• come up with a design for pull quotes (mockup?)
• ...

Description

There is an issue with the formatting of headers (H1, H2, H3 etc) in Wagtail. There appears to be inconsistent and excessive spacing in two key areas:

1. Between Headers - the spacing between different headers (H1, H2, H3 etc) is larger than expected, disrupting the flow and readability of the content
2. Between Text and Headers - there is excessive space between the end of a text block and the subsequent header, leading to a disjointed visual presentation

Expected Behavior

The spacing between headers and between text and headers should be uniform and adhere to standard web content formatting practices. This ensures a cohesive, visually appealing layout that enhances readability.

How it looks like now

Sorry, I meant to raise an issue about that but forgot. I'd be nice to show past Teach Team members that have moved on to other projects. Right now these would be David Read (https://github.com/davidread) and Tyler Kennedy (https://github.com/tktech), we don't need to show any current affiliation.
In terms of design and presentation, you can do whatever works best with the current template/models.

Description
Readability of body text on ckan.org is poor - density of text is unbalanced and text is hard to read.

Expected behaviour
When visiting the website, I expect to be able to read the content in an easy manner. I expect the copy to have sufficient space between individual lines of text so that it's more scannable and readble.

Acceptance

• line height is increased
• text is justified

Tasks

• increase line height/line spacing - increase to 1.5 or if now 21px, increase to 23-25px
• change text alignment to justified

Adding F.A.Q. will help decision makers and non-tech professionals understand implications of CKAN to their situation and how it can cover their needs.

The current version of F.A.Q. is minimalistic and goes by answering low amount of basic questions. Then we'd need to categorize questions with tags and provide search functionality.

Preparation
We should decide on the implementation. The simplest solution will work fine but we should have a possibility then to expand to up to 200 questions.

My proposition is to have either:

1. A list of questions on https://ckan.org/faq page where each question is a link to a page with the answer. So each answer has own page.
2. Accordion list: each question is the line in the list, each answer rolls out when user clicks on the question.

Implementation

1. Create https://ckan.org/faq page.
2. Put it in the header menu between Events and Docs.
3. Add page to robots.txt (if it doesn't happen automatically).

Content
https://docs.google.com/document/d/1FrC8zVbsTK0QItNDoz8_O2Lbx2DDdnmNot4vVK25IcA/edit#heading=h.9epokvk2xipg