design-sparx / blook-frontend Goto Github PK

Describe the bug
The landing page is blank. On the console this error is showing - Uncaught TypeError: Cannot read properties of null (reading 'current') from article-card.tsx:74

To Reproduce
Steps to reproduce the behavior:

1. Go to 'https://blook-blogger.netlify.app/'
2. Open inspect element
3. Navigate to the console tab
4. See error

Expected behavior
I expect to see the landing page loaded with all components, not a white blank screen.

Screenshots

Desktop (please complete the following information):

• OS: Windows
• Browser: Chrome
• Version: Version 116.0.5845.111 (Official Build) (64-bit)

Additional context
Add any other context about the problem here.

Is your feature request related to a problem? Please describe.
Author info on the post page is occupying too much space

Describe the solution you'd like
Author info should have little info with a CTA to the author page

• the tags look like buttons, on index page. They are way too distacting
• tags on post page zenye ziko hapo kwa title hazimake sense. Normally, I want to skim through the post and if I find it interesting, check other posts with similar tags
• there is too much empty space on back button kwa single post page
• on recent articles kwa post page, the dates zikiwa on top ziko very off. I actually thought ni za card above.
• the body of post should also be clickable kwa hizo preview cards

Additional

• 80% of humans read from top to bottom
• I want to quickly skim the title and first paragraph to determine if it is worth reading. Hii imetumika for over 100 year ata kwa magazeti. Humans only take 15 seconds to make that decision.
• So put the key details on top. Sio date and time.
• unaweza weka author on top only if you think utakuwa na legitimate and well know authors/companies

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.