thinkjrs / lottamob Goto Github PK

The stock logos for corporates are garbage for this context. Let's remove them.

Describe the bug
The newsletter signup component is displaying which is a bit prematurely. We don't have/want that setup yet.

Screenshots

Additional context
This is likely a regression from whence the component appeared in renders.

Is your feature request related to a problem? Please describe.
Clicking on research, blog, or article links are the only way to travel to an individual piece of content as a user, at the moment. This should change.

Describe the solution you'd like
As was planned, we should add the appropriate sections for research, blog, and article posts on the front of the landing page, below the immediate fold.

In particular, we need:

• research display section
• blog display section
• article display section

These should auto update from the latest introduced/published content from the CMS and use the same/exactly similar strategy/functions to accomplish these updates (on build).

Currently the markdown component from react-markdown does not play properly with Tailwindcss typography for headers. As of this moment, using # or ## to indicate a normal markdown header will display as standard inline-text.

Pro-tip: Avoid inline headers until I have this implemented.

What's coming

Sending body content from the sanity studio input box (see below) w/header markdown indications will render properly, with acceptable styling.

Image reference

The body "input" box with text below will not currently render # heading marks.

Example bad rendering:

Which should look more like ...

Is your feature request related to a problem? Please describe.
Lighthouse rightly complains that there is no content security policy enabled for this site. We should implement this to prevent things like XSS attacks.

Fortunately, there is no user input on this site, yet, so the lack of CSP is not an actual security issue.

Describe the solution you'd like
The above stated, we need to add in a CSP so that only those specific directives are allowed. This will help prevent a security issue in the event we add user input down the road.

Describe alternatives you've considered
As this is how the web works, there are no alternatives.

Additional context

From lighthouse:

Helpful resource link: https://web.dev/csp-xss/?utm_source=lighthouse&utm_medium=lr

Is your feature request related to a problem? Please describe.
Right now we have some images w/text uploaded for research, as opposed to the blog or article section, which have typical static images.

Describe the solution you'd like
This doesn't need to be an image and should be a styled box w/text & background color overlaying it.

• Add text using title param
• Add text using author param
• Add styled box/bg image

Describe the bug
We need to cleanup the labeling for issue templates herein as they currently do not say "lottamob", the name of this repo.

The new blog should get an mdx-embed implementation so that we can link to videos hosted externally.

Describe the solution you'd like
Add and implement https://www.npmjs.com/package/mdx-embed.

See https://www.thvu.dev/ for details, as they've implemented using the proper template herein.

Let's have direct links to article content (files) on the introductory page site and the on the link article themselves.