master for home page

[kberry]

I made various updates to the conf home page which got overwritten. I suppose you (Paulo) had your own copy and just edited/uploaded it as you needed to. Since you don't like to use RCS, we need some other system to avoid losing work.

[pauloney]

Yaics! This was not supposed to happen. I guess we talking about these three files: {program,index,sponsor-incl}.html ?

sponsor-incl.html: I did see that you changed it, Carleton Prod. Ctr. add I guess, and I did not edit it. Can we verify that what is in there is correct right now?

index.html: Did you do anything here?

program.html: Is there any way we can recover things from here? I definitely want all of it migrated to pres.dat.

[kberry]

I'm only talking about the home page (index.html). I made some minor text changes that later got overwritten. It's not important to recover those changes (whatever they were :). I only want to be clear in the future about where the master is. Without rcs, or git, or something, it would seem impossible to avoid clashes. I did not touch your program.html, and sponsor-incl.html is not used by your index.html. (Although, as I wrote in a separate issue, I think it would be better if your index.html just linked to sponsor.html instead of duplicating the information, slightly differently.) Of course the "not overwriting" is a general problem, in principle. -k

[pauloney]

On Thu, Aug 11, 2022 at 3:24 PM kberry ***@***.***> wrote: I'm only talking about the home page (index.html). I made some minor text changes that later got overwritten. It's not important to recover those changes (whatever they were :). I only want to be clear in the future about where the master is. Without rcs, or git, or something, it would seem impossible to avoid clashes.

Agreed. That page needs to go under GitHub (on my view). Any overwriting was real unlucky accident, because I made a point ot editing that page in only a few seconds and leave it.

I did not touch your program.html, and sponsor-incl.html is not used by your index.html. (Although, as I wrote in a separate issue, I think it would be better if your index.html just linked to sponsor.html instead of duplicating the information, slightly differently.)

I am deeply interested in the two issues you bring up: 1- That structurally the sponsor part should be a small snippet, easy to edit and included by the bigger index.html. In fact index.html has been programmed to be fully modular without the need of much editing. The problem this year is that we were caught with too little time to deal with it ... The page became ready only minutes before the Conference started and I ended up editing it a few times during it ... 2- If the sponsors should be included in the main page or a page by itself that we link to. I don't have an specific preference, but we have a wonderful guy on UX/UI joining forces with us on development and hopefully he can chime on that. Paulo Ney

…

Of course the "not overwriting" is a general problem, in principle. -k — Reply to this email directly, view it on GitHub <#13 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAR7WYWWYMH4UOWMOHX7JU3VYV4QTANCNFSM56GF2D5Q> . You are receiving this because you commented.Message ID: ***@***.***>

[kberry]

That page needs to go under GitHub (on my view). It's fine with me to use this github repo for *.html, instead of RCS. 1- That structurally the sponsor part should be a small snippet, If you need changes to sponsor-incl.html to work with your index.html, just tell me. I agree it would be ideal to #include sponsor-incl.html on your index.html, as I do on my simple version -- that's why I write the sponsor list as an include file in the first place. 2- If the sponsors should be included in the main page or a page by itself For some months at the beginning of the conference cycle, the separate sponsors page is useful as an easy place to point potential sponsors to. Better than one section on the index page which, whether yours or mine, necessarily has lots of other info on it. -k