search

Endangered-Language-Alliance / ela-website

Endangered Language Alliance website
1 stars 0 forks source link

Post-post launch tasks #36

Open abettermap opened 3 years ago

abettermap commented 3 years ago
abettermap commented 3 years ago

@rperlin-ela

I would be down to explain and implement that last item in the next few weeks if you're interested. The current setup is kinda defeating the purpose of using NextJS for a static site. I understand that you're doing a lot edits currently due to the migration, but at some point I imagine it will level out and the content won't be THAT dynamic that it needs to rebuild pages on the fly.

Your new workflow would be:

  1. Do some occasional weekly or biweekly content edits as needed. If they're daily and need to be published immediately, then my proposed approach will be semi-annoying (and will also burn up Netlify bandwidth).
  2. Once you're at a good stopping point and ready to publish (and you could even edit a couple pages, wait a few days, then edit some more), you'd go to netlify and click a button to re-deploy. It'll fetch your freshy fresh content and build the site anew, without taxing the user to wait for any background fetching anymore.

Slightly more work for you, but not terrible if you publish infrequently. Happy users though!

Let me know if you're interested. It also doesn't have to be "heavy-handed across the board" either. I could set it to, say, only build Home when a new build is triggered, but continue the refetching approach with Language instance pages, for example. I think it's one line of code per scenario (basically the scenarios I explained in my sitemap GH comment about priorities): Home, language landing, language instance, project landing, etc.

Personally I'd just leave it as is for a few weeks and once things stabilize then switch it over to the user-friendlier approach. If you anticipate editing a bunch of pages in one of the scenarios above, I could make just that scenario refetch and keep all the rest manual.

Options! 🤗

rperlin-ela commented 3 years ago

Sounds good, thanks. Yep, editing will definitely slowly down to weekly or biweekly or less. In fact I bet this coming week will be the last heavy week, if that, of edits.

I would want things to be as simple as possible, but I could probably get down with the tradeoff of doing the one extra step (for a new post, too?) if it makes things faster and lighter for the user. Let me know when you’re ready to work through it (except Aug 6-18)

On Jul 18, 2021, at 10:04 PM, Jason Lampel @.***> wrote:

@rperlin-ela https://github.com/rperlin-ela I would be down to explain and implement that last item in the next few weeks if you're interested. The current setup is kinda defeating the purpose of using NextJS for a static site. I understand that you're doing a lot edits currently due to the migration, but at some point I imagine it will level out and the content won't be THAT dynamic that it needs to rebuild pages on the fly.

Your new workflow would be:

Do some occasional weekly or biweekly content edits as needed. If they're daily and need to be published immediately, then my proposed approach will be semi-annoying (and will also burn up Netlify bandwidth). Once you're at a good stopping point and ready to publish (and you could even edit a couple pages, wait a few days, then edit some more), you'd go to netlify and click a button to re-deploy. It'll fetch your freshy fresh content and build the site anew, without taxing the user to wait for any background fetching anymore. Slightly more work for you, but not terrible if you publish infrequently. Happy users though!

Let me know if you're interested. It also doesn't have to be "heavy-handed across the board" either. I could set it to, say, only build Home when a new build is triggered, but continue the refetching approach with Language instance pages, for example. I think it's one line of code per scenario (basically the scenarios I explained in my sitemap GH comment about priorities): Home, language landing, language instance, project landing, etc.

Personally I'd just leave it as is for a few weeks and once things stabilize then switch it over to the user-friendlier approach. If you anticipate editing a bunch of pages in one of the scenarios above, I could make just that scenario refetch and keep all the rest manual.

Options! 🤗

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Endangered-Language-Alliance/ela-website/issues/36#issuecomment-882175035, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMNKB5AASNXBAXC2VPPQL4TTYOB3FANCNFSM5ASWCD4A.

abettermap commented 3 years ago

Sweet. Sounds like a plan. And yes you'd have to run it manually for brand new pages.

It would be more than one step for you but not much:

  1. production deploys
  2. Click the newest one
  3. Click Retry deploy

I think that's about it.

rperlin-ela commented 3 years ago

Relevant to this, I feel the biggest challenge with the site right now is that it's not clear when/if changes we make in WP are going to update. If doing what you've described here would fix that, I'm all in, ready any time. We're not making changes that frequently now and I'll gladly do that extra step in order to have predictability that our WP edits are going to go right through.

If this is a separate issue, then I would prioritize this instead, can give examples of recent edits I'm not seeing despite trying different browsers, private windows, clearing cache etc.

rperlin-ela commented 3 years ago

Just a note that posts for Latest seem to be published right off with no issue— it's edits to Pages and Languages, maybe other things, that at least seem not to go through.

abettermap commented 3 years ago

Hey I'm heading to Denver for bday weekend and will look into this next week or weekend, but feel free to try this.

https://app.netlify.com/teams/info-upes7g/builds/6121a54ee5a50900090ab4ec

Give it a good five minutes.

rperlin-ela commented 3 years ago

The master is in the building — that there seems to have done the trick.

Happy birthday!