search

nextcloud / website

An attempt to build a new website (obsolete)
7 stars 4 forks source link

changes to implement #4

Open jospoortvliet opened 6 years ago

jospoortvliet commented 6 years ago

As long as this isn't done, there will be changes I made on the old website that have to be implemented here, too. A list to track the changes:

Espina2 commented 6 years ago

@jospoortvliet if will handle this page by page, and switch page by page, this will never be the case. Because when we switch the page, we no longer will be doing modifications on the old site.

But it all dependents in how you guys plan to make the switch, if incrementally (I prefer that) or switch all the website at once.

I prefer incrementally, because we can refactor all the old code for something that are actually maintainable. We can even tweak the design of the pages. :)

If we try to replace the whole website at time, we have to do a massive copy paste and bunch of weird hacks to make the things work.

jospoortvliet commented 6 years ago

I agree - and if we then switch the most used pages first, it is best for the load on the server, too. @MorrisJobke what do you think?

MorrisJobke commented 6 years ago

I prefer incrementally, because we can refactor all the old code for something that are actually maintainable. We can even tweak the design of the pages. :)

I would vote also for a step by step thing. We can start small and map URL by URL to the new static code.

I agree - and if we then switch the most used pages first, it is best for the load on the server, too. @MorrisJobke what do you think?

Doesn't really matter as of now. Best would be to start with the more static (content wise) pages first and gather some experience.