ah yeah I just noticed that last night, actually coming from the the footer, the new pages made the amount links wider causing some to run off the page at medium screen sizes. Need to adjust. Made an issue, assume out of scope here

remove psuedo selector

Can we get a script to automate this ? So a single person can run it all in seconds, at the cost of a few minutes/hours of dev. That would be a huge man/hour gain.

remove trailing slash

For sure, I added it here for now, but will make an issue to replace it globally as it is being used in a lot of places

var name change

make strapi url a variable

What's the workflow to take this on?

fix image height

fix quote lint issue

fix '

update job post copy

fit image better

In D14215#317696, @Mengerian wrote:

Noticed a few weirdnesses the look like broken images

from here: http://51.68.37.192:41826/blog/ecash-aliases-development-sneak-peek-june-2023

Weirdly cropped image here: http://51.68.37.192:41826/blog/what-the-future-holds-for-ecash

And another broken-looking image here: http://51.68.37.192:41826/blog/ecash-monthly-recap-may-2023

check build status

check build status

check build status

@bot preview-e.cash

@bot preview-e.cash

add alt to image

lol fair enough, was a bad name

rename dateConvert

In D14157#316364, @bytesofman wrote:

at this point in the stack -- blog links are expected to 404? still pending a logic to add those pages at build time?

define featured post and post at top

@bot preview e.cash

remove date format

@bot preview e.cash

update test

So the main value of hosting somewhere else is so the blog authors have a user friendly CMS to make the posts

move return inside try

rebase with master

add data shape test and improve for loop variable

In D14105#315068, @bytesofman wrote:

Why do we want to fetch every single blog post?

Seems like paginated return would be useful to load only enough blog posts for the current page.

As the blog grows, quickly impractical to have an API loading hundreds of posts on page load when the user can only read one at a time.

update function comment

fix

ah sure, those styles were only being applied to the mining section, but bad idea because if another section is added it will not be the last child anymore.
Broke it out to be specific to the mining section

create seperate styled component for the mining section

remove button change

In D14098#314941, @bytesofman wrote:

this page:

e.cash:

not related to thsi diff, but seems like the images are much bigger on our current landing page. Since we are already loading large images, should allow them to be as large as possible on the page.

@bot preview-explorer

Okay added. I did npm run lint already, it didnt throw any errors for me though

format function