konstantinkudelko / church-website Goto Github PK

We need to change the format of the article URL from magazine/4 to magazine/article-slug.
Docs are here

Нам нужно апдейтнуть Nextjs до последней версии. Здесь можно посмотреть, как это нужно сделать.

Need to bootstrap project with: preact, next.js, effector, reakit, reshadow, ?routing

How we can use mdx for the articles?
What we have to do to replace all of this logic?

Next.js and the client code already has it functionality - we need a webhook to articles creation and editing for updates static generated pages.

UPD: frontend already includes all necessary code for dynamic prerender, all we need is a webhook

Задача сделать прототип страницы статей. Можно оформить в виде карточек, как это отрисовано в Фигме.

Нижние теги можно опустить, а цвета для обложек положить в метаданные каждой статьи (файл .mdx).

We need a page thats render article by a link.

Layout example: https://whatabout.com.ua/ya-zhenschina-manifest

Right now we have content jumping if the page is loading initially. We have to fix it by adding inline styles to the image.
As well we have to align image height on the articles list screen. We have to fix this bug.

We need to replace wysiwyg in strapi for preparing content structure at the server (currently server responding unparsed markdown).

Client expecting content with a structure like:

[
  {
    "type": "title1",
    "body": "Abc"
  },
  {
    "type": "note",
    "body": "Abc"
  },
  {
    "type": "paragraph",
    "body": "Abc"
  },
  {
    "type": "title2",
    "body": "Abc"
  },
  {
    "type": "paragraph",
    "body": "Abc"
  },
  {
    "type": "title2",
    "body": "Abc"
  },
  {
    "type": "paragraph",
    "body": [
      {
        "type": "strong",
        "body": "Abc"
      },
      {
        "type": "text",
        "body": "Abc"
      }
    ]
  }
]

For content:

# Abc

> Abc

Abc

## Abc

Abc

## Abc

**Abc** abc

https://strapi.io/blog/how-to-change-the-wysiwyg-in-strapi

User should be able share article to VK & Facebook:
https://habr.com/ru/post/250021/

Wait until here we will not see a clear migration guide from the strapi team.

@artalar

We have translations at the platform, for example:
https://github.com/ke-community/platform/tree/master/client/src/features/Articles/translations

Can we remove this? I don't think that we will need a translation for this platform.

In README.md FE guys should be able check current available API based on strapi

Also, we need to populate db right data when strapi starts

Actually you can remove this block:

For now remove footer completely