the documentation site is not available

[wenbinyu-PU]

I just found out that the documentation site is not available. Do you know why? @unitasium @duhd1993 Is it because I changed the name to iVABS? I changed it back and could not get the documentation site back either.

[duhd1993]

It's case-sensitive. This might be why I initially used ivabs. Reason why it still doesn't work when you change it back might be just delay.
https://wenbinyugroup.github.io/iVABS/
We can also consider using a subdomain of analyswift.

[wenbinyu-PU]

Great, it is available now. What is the advantage of using a subdomain of AnalySwift?

[duhd1993]

I feel it's not very intuitive to change to uppercase when you type a url. The domain part is case-insensitive.
BTW. google already learned the lower case url. It will take a while for it to change to upper case iVABS.

[wenbinyu-PU]

Yes, however, usually people don't type a url. Often we just click the link. Rarely we type. My concern is that the ranking we build up with ivabs is now lost. We need to accumulate again. Is there a way to redirect https://wenbinyugroup.github.io/ivabs/ also to https://wenbinyugroup.github.io/iVABS/? Another issue is that we have iVABS, a VABS-based Design Framework - iVABS 0.8 documentation<https://wenbinyugroup.github.io/iVABS/> Do we really need to attach - iVABS 0.8 documentation, or this part can be deleted. Just keep iVABS, a VABS-based Design

[wenbinyu-PU]

One more related issue is that the link under the repository does not work. I tried to change the readme file. It is still not working.

[duhd1993]

One more related issue is that the link under the repository does not work. I tried to change the readme file. It is still not working.

This is because the automatic build is set to push to gh-pages branch. But Su has configured the site to gh-pages-new branch. I don't know if he added something different. It seems the main branch might be out of date. We need confirmation from him.

Is there a way to redirect https://wenbinyugroup.github.io/ivabs/ also to https://wenbinyugroup.github.io/iVABS/?

Yes. but we need to create a ivabs repo and set up a redirect from there. We can keep it for some time until google recognize the new site. Currently google points to the old one and it leads to a 404 error.

[wenbinyu-PU]

Is the re-direction automatic? If yes, please create the new repo to avoid the 404 error. From: Haodong DU ***@***.***> Sent: Friday, February 9, 2024 11:37 PM To: wenbinyugroup/iVABS ***@***.***> Cc: Yu, Wenbin ***@***.***>; Author ***@***.***> Subject: Re: [wenbinyugroup/iVABS] the documentation site is not available (Issue #57)

…

---- External Email: Use caution with attachments, links, or sharing data ---- One more related issue is that the link under the repository does not work. I tried to change the readme file. It is still not working. This is because the automatic build is set to push to gh-pages branch. But Su has configured the site to gh-pages-new branch. I don't know if he added something different. It seems the main branch might be out of date. We need confirmation from him. Is there a way to redirect https://wenbinyugroup.github.io/ivabs/ also to https://wenbinyugroup.github.io/iVABS/? Yes. but we need to create a ivabs repo and set up a redirect from there. We can keep it for some time until google recognize the new site. Currently google points to the old one and it leads to a 404 error. - Reply to this email directly, view it on GitHub<#57 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ASUPJ6NDVEPDVEBYLOQMQ3LYS32NJAVCNFSM6AAAAABDCM7H42VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZWHA2TSMZVGQ>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[duhd1993]

It's not very automatic but can be done https://finisky.github.io/en/migrate-github-pages-by-301-redirects/
it's a tradeoff when you host on github pages and use its domain. github does not let you customize a lot of things

[wenbinyu-PU]

If it is not too much work, please get it done.

[duhd1993]

I propose the following solution to keep the google rank @wenbinyu-PU @unitasium

1. Temporarily set the repo name back to ivabs
2. Set the pages to custom domain ivabs.analyswift.com. Github will do a 301 redirect and google would recognize it.
3. After some time when google fully indexed the new domain, we can change the repo name to iVABS to avoid confusion.

[wenbinyu-PU]

1. Ok, I have change it back.
2. The main concern here is that iVABS was mainly developed by Purdue. Just emailed Allan.

[wenbinyu-PU]

@unitasium @duhd1993 after careful consideration, I think we can keep ivabs as the repo name according what Su suggested. Then we don't need a subdomain.

However, sometimes through google, I found the version number attached to a page see below picture. Is it automatic? I will suggest no version number attached to it to keep consistency and have the same page better remembered/ranked by search engine.