Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automate the process of publishing blog posts #13870

Closed
dionysuzx opened this issue Jun 3, 2023 · 1 comment · Fixed by #14561
Closed

Automate the process of publishing blog posts #13870

dionysuzx opened this issue Jun 3, 2023 · 1 comment · Fixed by #14561

Comments

@dionysuzx
Copy link
Collaborator

dionysuzx commented Jun 3, 2023

Summary

We have attempted this before by querying ARWeave. Please see:

The reason we reverted this change was because it was taking way too long to load the mirror blog posts. It caused the first-page-load to be a very subpar experience as it made the API calls.

Definition of done

option 1

  • not significantly impact the initial page load
  • update the website homepage within a 24 hour window of publishing a blog post

option 2

  • implementing an approach that deprecates the need for this

Some ideas:

  • Have a cron schedule / nightly that queries the API and rebuilds the blog posts locally, perhaps a sed replace over the file BlogSection.tsx, and re-publishes the website.
  • Completely move to another blogging platform -> this would warrant discussion with the team and some clear arguments of why the change could be beneficial
    • Some reasons it could be beneficial: improvement in SEO on our site, could look more official having the blog on a proper taiko.xyz domain
  • Chat with @je4nt0nic / team to see if we even need blog posts on the home page or if we should put something else there.
@dantaik
Copy link
Contributor

dantaik commented Jul 15, 2023

Is this done, @d1onys1us ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants