RobertHarvey is totally right: it depends. It could be a good solution but it is a terrible solution also for some projects.
In you question you state:
He has created a small website (there are apparently no dynamic contents)
Based on that he chose the wrong solution. Now you also note that there are animations. So maybe, if those are exceptional, it might be a good solution. Let's state those animation could also be made with normal solutions.
Whether it is good or right is then simple: If it should work like a normal website, so with a good ranking in search engines, good accessibility and all other standard webdevelopers take care of it is just wrong. You build a website with a goal. If that is: Have normal people visit it to subscribe/buy/view etc. it won't meet that goal.
His arguments:
Websites with a high amount of users do this to prevent server overloading.
Yes, but this is a small website right? http://c2.com/cgi/wiki?PrematureOptimization
It is easier to create new sections.
Likely he is unaware of other solutions. No problem, it's his first one. This is something where training / reading could do a lot.
It is easier to translate, as translations, texts and almost everything is loaded from a JSON.
Same here, localisation is something much more complex than just translating some pieces of text anyway. Education is here also the key.
You can expand more sections directly from a JSON file.
Might be correct, seems simple to do. If a user has to do it then it directly becomes more difficult. With a database for example it might be possible to create a form for that.
Everything is smooth, as you don't move to another page.
This is true but not undoable with other solutions. Loading pieces of content with ajax (with changing the browser history) might solve this well. https://developer.mozilla.org/en/docs/DOM/Manipulating_the_browser_history
To take this into a broader level: It is nonsense to build a dedicated framework if it is just a simple site. Use the basics or an existing system for it. On the other side, it's a nice learning experience. We all tried to build a CMS once right? ;) His arguments are not strong, if he want to work more in this area more knowledge would be advisable.
RobertHarvey is totally right: it depends. It could be a good solution but it is a terrible solution also for some projects.
In you question you state:
He has created a small website (there are apparently no dynamic contents)
Based on that he chose the wrong solution. Now you also note that there are animations. So maybe, if those are exceptional, it might be a good solution. Let's state those animation could also be made with normal solutions.
Whether it is good or right is then simple: If it should work like a normal website, so with a good ranking in search engines, good accessibility and all other standard webdevelopers take care of it is just wrong. You build a website with a goal. If that is: Have normal people visit it to subscribe/buy/view etc. it won't meet that goal.
His arguments:
Websites with a high amount of users do this to prevent server overloading.
Yes, but this is a small website right? http://c2.com/cgi/wiki?PrematureOptimization
It is easier to create new sections.
Likely he is unaware of other solutions. No problem, it's his first one. This is something where training / reading could do a lot.
It is easier to translate, as translations, texts and almost everything is loaded from a JSON.
Same here, localisation is something much more complex than just translating some pieces of text anyway. Education is here also the key.
You can expand more sections directly from a JSON file.
Might be correct, seems simple to do. If a user has to do it then it directly becomes more difficult. With a database for example it might be possible to create a form for that.
Everything is smooth, as you don't move to another page.
This is true but not undoable with other solutions. Loading pieces of content with ajax (with changing the browser history) might solve this well. https://developer.mozilla.org/en/docs/DOM/Manipulating_the_browser_history
To take this into a broader level: It is nonsense to build a dedicated framework if it is just a simple site. Use the basics or an existing system for it. On the other side, it's a nice learning experience. We all tried to build a CMS once right? ;) His arguments are not strong, if he want to work more in this area more knowledge would be advisable.
RobertHarvey is totally right: it depends. It could be a good solution but it is a terrible solution also for some projects.
In you question you state:
He has created a small website (there are apparently no dynamic contents)
Based on that he chose the wrong solution. Now you also note that there are animations. So maybe, if those are exceptional, it might be a good solution. Let's state those animation could also be made with normal solutions.
Whether it is good or right is then simple: If it should work like a normal website, so with a good ranking in search engines, good accessibility and all other standard webdevelopers take care of it is just wrong. You build a website with a goal. If that is: Have normal people visit it to subscribe/buy/view etc. it won't meet that goal.
His arguments:
Websites with a high amount of users do this to prevent server overloading.
Yes, but this is a small website right? http://c2.com/cgi/wiki?PrematureOptimization
It is easier to create new sections.
Likely he is unaware of other solutions. No problem, it's his first one. This is something where training / reading could do a lot.
It is easier to translate, as translations, texts and almost everything is loaded from a JSON.
Same here, localisation is something much more complex than just translating some pieces of text anyway. Education is here also the key.
You can expand more sections directly from a JSON file.
Might be correct, seems simple to do. If a user has to do it then it directly becomes more difficult. With a database for example it might be possible to create a form for that.
Everything is smooth, as you don't move to another page.
This is true but not undoable with other solutions. Loading pieces of content with ajax (with changing the browser history) might solve this well. https://developer.mozilla.org/en/docs/DOM/Manipulating_the_browser_history
To take this into a broader level: It is nonsense to build a dedicated framework if it is just a simple site. Use the basics or an existing system for it. On the other side, it's a nice learning experience. We all tried to build a CMS once right? ;) His arguments are not strong, if he want to work more in this area more knowledge would be advisable.
RobertHarvey is totally right RobertHarvey is totally right: it depends. It could be a good solution but it is a terrible solution also for some projects.
In you question you state:
He has created a small website (there are apparently no dynamic contents)
Based on that he chose the wrong solution. Now you also note that there are animations. So maybe, if those are exceptional, it might be a good solution. Let's state those animation could also be made with normal solutions.
Whether it is good or right is then simple: If it should work like a normal website, so with a good ranking in search engines, good accessibility and all other standard webdevelopers take care of it is just wrong. You build a website with a goal. If that is: Have normal people visit it to subscribe/buy/view etc. it won't meet that goal.
His arguments:
Websites with a high amount of users do this to prevent server overloading.
Yes, but this is a small website right? http://c2.com/cgi/wiki?PrematureOptimization
It is easier to create new sections.
Likely he is unaware of other solutions. No problem, it's his first one. This is something where training / reading could do a lot.
It is easier to translate, as translations, texts and almost everything is loaded from a JSON.
Same here, localisation is something much more complex than just translating some pieces of text anyway. Education is here also the key.
You can expand more sections directly from a JSON file.
Might be correct, seems simple to do. If a user has to do it then it directly becomes more difficult. With a database for example it might be possible to create a form for that.
Everything is smooth, as you don't move to another page.
This is true but not undoable with other solutions. Loading pieces of content with ajax (with changing the browser history) might solve this well. https://developer.mozilla.org/en/docs/DOM/Manipulating_the_browser_history
To take this into a broader level: It is nonsense to build a dedicated framework if it is just a simple site. Use the basics or an existing system for it. On the other side, it's a nice learning experience. We all tried to build a CMS once right? ;) His arguments are not strong, if he want to work more in this area more knowledge would be advisable.
RobertHarvey is totally right: it depends. It could be a good solution but it is a terrible solution also for some projects.
In you question you state:
He has created a small website (there are apparently no dynamic contents)
Based on that he chose the wrong solution. Now you also note that there are animations. So maybe, if those are exceptional, it might be a good solution. Let's state those animation could also be made with normal solutions.
Whether it is good or right is then simple: If it should work like a normal website, so with a good ranking in search engines, good accessibility and all other standard webdevelopers take care of it is just wrong. You build a website with a goal. If that is: Have normal people visit it to subscribe/buy/view etc. it won't meet that goal.
His arguments:
Websites with a high amount of users do this to prevent server overloading.
Yes, but this is a small website right? http://c2.com/cgi/wiki?PrematureOptimization
It is easier to create new sections.
Likely he is unaware of other solutions. No problem, it's his first one. This is something where training / reading could do a lot.
It is easier to translate, as translations, texts and almost everything is loaded from a JSON.
Same here, localisation is something much more complex than just translating some pieces of text anyway. Education is here also the key.
You can expand more sections directly from a JSON file.
Might be correct, seems simple to do. If a user has to do it then it directly becomes more difficult. With a database for example it might be possible to create a form for that.
Everything is smooth, as you don't move to another page.
This is true but not undoable with other solutions. Loading pieces of content with ajax (with changing the browser history) might solve this well. https://developer.mozilla.org/en/docs/DOM/Manipulating_the_browser_history
To take this into a broader level: It is nonsense to build a dedicated framework if it is just a simple site. Use the basics or an existing system for it. On the other side, it's a nice learning experience. We all tried to build a CMS once right? ;) His arguments are not strong, if he want to work more in this area more knowledge would be advisable.
RobertHarvey is totally right: it depends. It could be a good solution but it is a terrible solution also for some projects.
In you question you state:
He has created a small website (there are apparently no dynamic contents)
Based on that he chose the wrong solution. Now you also note that there are animations. So maybe, if those are exceptional, it might be a good solution. Let's state those animation could also be made with normal solutions.
Whether it is good or right is then simple: If it should work like a normal website, so with a good ranking in search engines, good accessibility and all other standard webdevelopers take care of it is just wrong. You build a website with a goal. If that is: Have normal people visit it to subscribe/buy/view etc. it won't meet that goal.
His arguments:
Websites with a high amount of users do this to prevent server overloading.
Yes, but this is a small website right? http://c2.com/cgi/wiki?PrematureOptimization
It is easier to create new sections.
Likely he is unaware of other solutions. No problem, it's his first one. This is something where training / reading could do a lot.
It is easier to translate, as translations, texts and almost everything is loaded from a JSON.
Same here, localisation is something much more complex than just translating some pieces of text anyway. Education is here also the key.
You can expand more sections directly from a JSON file.
Might be correct, seems simple to do. If a user has to do it then it directly becomes more difficult. With a database for example it might be possible to create a form for that.
Everything is smooth, as you don't move to another page.
This is true but not undoable with other solutions. Loading pieces of content with ajax (with changing the browser history) might solve this well. https://developer.mozilla.org/en/docs/DOM/Manipulating_the_browser_history
To take this into a broader level: It is nonsense to build a dedicated framework if it is just a simple site. Use the basics or an existing system for it. On the other side, it's a nice learning experience. We all tried to build a CMS once right? ;) His arguments are not strong, if he want to work more in this area more knowledge would be advisable.
@RobertHarvey is totally right. ItRobertHarvey is totally right : it depends. It could be a good solution but it is a terrible solution also for some projects.
In you question you state:
He has created a small website (there are apparently no dynamic contents)
Based on that he chose the wrong solution. Now you also note that there are animations. So maybe, if those are exceptional, it might be a good solution. Let's state those animation could also be made with normal solutions.
Whether it is good or right is then simple: If it should work like a normal website, so with a good ranking in search engines, good accessibility and all other standard webdevelopers take care of it is just wrong. You build a website with a goal. If that is: Have normal people visit it to subscribe/buy/view etc. it won't meet that goal.
His arguments:
Websites with a high amount of users do this to prevent server overloading.
Yes, but this is a small website right? http://c2.com/cgi/wiki?PrematureOptimization
It is easier to create new sections.
Likely he is unaware of other solutions. No problem, it's his first one. This is something where training / reading could do a lot.
It is easier to translate, as translations, texts and almost everything is loaded from a JSON.
Same here, localisation is something much more complex than just translating some pieces of text anyway. Education is here also the key.
You can expand more sections directly from a JSON file.
Might be correct, seems simple to do. If a user has to do it then it directly becomes more difficult. With a database for example it might be possible to create a form for that.
Everything is smooth, as you don't move to another page.
This is true but not undoable with other solutions. Loading pieces of content with ajax (with changing the browser history) might solve this well. https://developer.mozilla.org/en/docs/DOM/Manipulating_the_browser_history
To take this into a broader level: It is nonsense to build a dedicated framework if it is just a simple site. Use the basics or an existing system for it. On the other side, it's a nice learning experience. We all tried to build a CMS once right? ;) His arguments are not strong, if he want to work more in this area more knowledge would be advisable.
@RobertHarvey is totally right. It depends. It could be a good solution but it is a terrible solution also for some projects.
In you question you state:
He has created a small website (there are apparently no dynamic contents)
Based on that he chose the wrong solution. Now you also note that there are animations. So maybe, if those are exceptional, it might be a good solution. Let's state those animation could also be made with normal solutions.
Whether it is good or right is then simple: If it should work like a normal website, so with a good ranking in search engines, good accessibility and all other standard webdevelopers take care of it is just wrong. You build a website with a goal. If that is: Have normal people visit it to subscribe/buy/view etc. it won't meet that goal.
His arguments:
Websites with a high amount of users do this to prevent server overloading.
Yes, but this is a small website right? http://c2.com/cgi/wiki?PrematureOptimization
It is easier to create new sections.
Likely he is unaware of other solutions. No problem, it's his first one. This is something where training / reading could do a lot.
It is easier to translate, as translations, texts and almost everything is loaded from a JSON.
Same here, localisation is something much more complex than just translating some pieces of text anyway. Education is here also the key.
You can expand more sections directly from a JSON file.
Might be correct, seems simple to do. If a user has to do it then it directly becomes more difficult. With a database for example it might be possible to create a form for that.
Everything is smooth, as you don't move to another page.
This is true but not undoable with other solutions. Loading pieces of content with ajax (with changing the browser history) might solve this well. https://developer.mozilla.org/en/docs/DOM/Manipulating_the_browser_history
To take this into a broader level: It is nonsense to build a dedicated framework if it is just a simple site. Use the basics or an existing system for it. On the other side, it's a nice learning experience. We all tried to build a CMS once right? ;) His arguments are not strong, if he want to work more in this area more knowledge would be advisable.
RobertHarvey is totally right : it depends. It could be a good solution but it is a terrible solution also for some projects.
In you question you state:
He has created a small website (there are apparently no dynamic contents)
Based on that he chose the wrong solution. Now you also note that there are animations. So maybe, if those are exceptional, it might be a good solution. Let's state those animation could also be made with normal solutions.
Whether it is good or right is then simple: If it should work like a normal website, so with a good ranking in search engines, good accessibility and all other standard webdevelopers take care of it is just wrong. You build a website with a goal. If that is: Have normal people visit it to subscribe/buy/view etc. it won't meet that goal.
His arguments:
Websites with a high amount of users do this to prevent server overloading.
Yes, but this is a small website right? http://c2.com/cgi/wiki?PrematureOptimization
It is easier to create new sections.
Likely he is unaware of other solutions. No problem, it's his first one. This is something where training / reading could do a lot.
It is easier to translate, as translations, texts and almost everything is loaded from a JSON.
Same here, localisation is something much more complex than just translating some pieces of text anyway. Education is here also the key.
You can expand more sections directly from a JSON file.
Might be correct, seems simple to do. If a user has to do it then it directly becomes more difficult. With a database for example it might be possible to create a form for that.
Everything is smooth, as you don't move to another page.
This is true but not undoable with other solutions. Loading pieces of content with ajax (with changing the browser history) might solve this well. https://developer.mozilla.org/en/docs/DOM/Manipulating_the_browser_history
To take this into a broader level: It is nonsense to build a dedicated framework if it is just a simple site. Use the basics or an existing system for it. On the other side, it's a nice learning experience. We all tried to build a CMS once right? ;) His arguments are not strong, if he want to work more in this area more knowledge would be advisable.