Closed abettermap closed 3 years ago
EDIT: added projects
section above.
@rperlin-ela let me know what you think on:
nvm on the "won't translate" thing, at least for some of them. Celtic would now be /projects/celtic
i believe.
I think we can leave the shortcodes and I'll deal with them as I move stuff over.
Great if you can "translate" all the projects. So all good on "languages, children, variations"?
These are all pseudo-redirects, no longer needed, so I guess for consistency we translate them to their full URLs https://elalliance.org/koda https://elalliance.org/kratylos https://elalliance.org/tibetan
https://elalliance.org/2013/03/breton is an old post which go with the posts, but https://elalliance.org/2012/projects/circassian and https://elalliance.org/2012/projects/languages can be axed, redundant bits from old structure, or I guess replaced with https://elalliance.org/languages and https://elalliance.org/projects/circassian if that's what we're doing
languages-2 is old junk, can axe.
Did "Programs" URL matching fall into place? All the projects/ ones should be the same deal as before. I assume now it's good practice to use hyphens between words, like /arts-and-culture instead of /artsandculture? Some of these should be straightforward, like https://elalliance.org/programs/maps > https://elalliance.org/our-work/maps, but others I know are trickier like https://elalliance.org/programs/documentation > /how-we-work/language-documentation
So should I just go in and do some "Replace in Database (URLs) of as much of this as I can figure out, with newer absolute paths? Am I understanding right?
Ok, I think I got most of your very useful list— mostly replacing with relative links.
Nice, have you been testing any afterward? I've mostly been testing the super-custom stuff but not old posts or pages.
On Sat, May 22, 2021 at 9:28 PM rperlin-ela @.***> wrote:
Ok, I think I got most of your very useful list— mostly replacing with relative links.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Endangered-Language-Alliance/ela-website/issues/6#issuecomment-846491209, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABF6MB67S4MBZUG7TDHFNB3TPBR3TANCNFSM442SMOUA .
Yep, spot-testing and seems good
On May 23, 2021, at 11:36 AM, Jason Lampel @.***> wrote:
Nice, have you been testing any afterward? I've mostly been testing the super-custom stuff but not old posts or pages.
On Sat, May 22, 2021 at 9:28 PM rperlin-ela @.***> wrote:
Ok, I think I got most of your very useful list— mostly replacing with relative links.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Endangered-Language-Alliance/ela-website/issues/6#issuecomment-846491209, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABF6MB67S4MBZUG7TDHFNB3TPBR3TANCNFSM442SMOUA .
— 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/6#issuecomment-846581957, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMNKB5GRMBE32X7CMXR3YI3TPEOGRANCNFSM442SMOUA.
migration from old wp went well overall but still have a few steps/questions...
Shortcodes
should we do a wholesale find/replace/delete on things like
[wptabs]
and similar? or leave it intact since it kinda-sorta helps to see the tab headings and content during the conversion from old language page-pages to new custom Language post type? i believe i've done all the manual hand-jamming i'm going to do and ball will soon be in Ross's court so i have no skin the game, but i would lean towards keeping them intact and then when we think the migration is "done" i can search the DB and find/replace then?Old links/route structure
To replace?
should i replace these to match the new structure? this is a consolidated list and there are many instances using these links, but i imagine mostly old blog posts.
blog post? project? not sure
it's got a year but no month. maybe this was a redirect?
old posts
who what why how etc.
and children:
top-level (but shouldn't be?)
languages, children, variations
i'm not going to touch these. i'm not familiar enough with the old structure to spend time reviewing each one, so hopefully Ross and i can find/replace over zoom or, ideally, Ross does it. maybe some just won't translate though? e.g.
https://elalliance.org/languages/celtic
is just not going to have an equivalent in the new setup?languages-2 ???
programs
same comment as languages above.
Related
Read more auto-gen
the wp auto-generated "Read more..." functionality is great but it might not point to what we expect (hard to explain), and we also don't want to see it in all cases. i'm hoping it will just go away if excerpts are manually written (as opposed to wp using a truncated version of Editor contents), so just a heads-up that if you don't want to see the auto Read More, try creating an excerpt manually first. i know there are a lot of old posts, so i'm reluctant to prescribe changing them ALL, so let's see how it's going first.
wp content site vs. current live site vs. deploy
we've got a hodge podge mix of these so let's take note where they occur and i'll fix as we go. eventually when we're live-live, everything except images and other stuff in the wp media library (which will always point to the wp content site) should point to https://elalliance.org or a relative path.