Q3 Improvements to website about website HOT 3 CLOSED

I am happy with the progress we have made on this initiative. @maanasb01 is fully ramped up on the website code now. I'm closing this initiative. We'll create a new consolidated initiative for other improvements.

from website.

This is a rough outline of all tasks I could think of, organized by complexity. I'll scope them into Features and list on the issue.

Easy

• a sitemap and index page
• Review and update README
• Add documentation in wiki to show how someone can add a new blog post. Best practices and caveat.
• Standardize how to use images in a blog post. We have sometimes used images from the /images directory and sometimes from the /static directory. Find out the best pratices recommended by gatsby, change current usage to the recommended way, document them and enforce them for future.
  • If you go to the /blog page, you will see that the page loads with the image and then resizes, causing a jitter in the UI. This should be fixed when you fix this.
• dynamic sections on the homepage
  • recent blogs
  • recent updates
• on the product page, embed dynamic sections which shows all the blog posts and updates of that product

Medium

• Like the blog posts, updates also need to have a project field. It should be possible to query updates based on a project. Make filters on the /updates page.
• add follow/subscribe widget, which users mailchimp to facilitate user subscription to a particular product
• add rss feed
• a breadcrumb UI at a suitable place
• audit performance and responsiveness on mobile. Make UI tweaks to improve the
• Define entities and use their relationships to drive content in pages
  • members
  • projects
  • tags
  • blog posts
  • Define dynamic Links between them

Complex

• Upgrade Gatsby to latest
• Create a GUI for the team to add and edit content

from website.

Hello, Can you assign this issue to me please, I would like to work on it.

from website.