acemang
posted this
04 May 2021
I think the "easy" workaround is to create two different websites and create 2 buttons on both pages to change to the another page.
The problem is that If one have a problem or have something that needs to be changed the work doubles because now you have two identical pages. if you have 4 or 5 languages the work 4x or 5x.
One of the solutions is Nicepage had to have an internal database. Any time we entered a text field, that field is inserted in that database for prime language. If we added more languages new fields are created in the database to insert the text there. Nicepage could have a menu to edit all the texts in a page. To easy edit multiple languages. This needs to make core changes to Nicepage if it was not thought since the beginning. I'm a programmer so I'm not talking this with random thoughts. The problem will be more complex if we add support for Wordpress and the rest witch I don't dominate and I don't even care. I loved Nicepage part that you can export to a normal html website. Only noobs go for Wordpress websites and people that don't have a clue what well code is written that make an impact on the client. Google made AMP version for a reason they have all the statists they need to invest on that.
Nicepage focus on so many different things you can't be good at all, same time, with so little investment in development.
If this problem have 2 years I think I'm wasting my time with your product. I'm testing it, and I'm a consultor in 2 companies that I can advice them to buy your product. I would buy it if it answer all normal problems that are in 90% of websites.
I really think you have a potential product in the way, but it's not ready for me right now. Only for simple websites that require not many questions. I never done an app (I made mobile apps) that have 1 single language. I can't believe that Americans think only English matters, "let's focus on that".
To create a website from scratch takes time, and yours is a good solution to reduce time and costs. Your in the good path but can't take 2 years to be polite and do nothing about a core function.
I think the "easy" workaround is to create two different websites and create 2 buttons on both pages to change to the another page.
The problem is that If one have a problem or have something that needs to be changed the work doubles because now you have two identical pages. if you have 4 or 5 languages the work 4x or 5x.
One of the solutions is Nicepage had to have an internal database. Any time we entered a text field, that field is inserted in that database for prime language. If we added more languages new fields are created in the database to insert the text there. Nicepage could have a menu to edit all the texts in a page. To easy edit multiple languages. This needs to make core changes to Nicepage if it was not thought since the beginning. I'm a programmer so I'm not talking this with random thoughts. The problem will be more complex if we add support for Wordpress and the rest witch I don't dominate and I don't even care. I loved Nicepage part that you can export to a normal html website. Only noobs go for Wordpress websites and people that don't have a clue what well code is written that make an impact on the client. Google made AMP version for a reason they have all the statists they need to invest on that.
Nicepage focus on so many different things you can't be good at all, same time, with so little investment in development.
If this problem have 2 years I think I'm wasting my time with your product. I'm testing it, and I'm a consultor in 2 companies that I can advice them to buy your product. I would buy it if it answer all normal problems that are in 90% of websites.
I really think you have a potential product in the way, but it's not ready for me right now. Only for simple websites that require not many questions. I never done an app (I made mobile apps) that have 1 single language. I can't believe that Americans think only English matters, "let's focus on that".
To create a website from scratch takes time, and yours is a good solution to reduce time and costs. Your in the good path but can't take 2 years to be polite and do nothing about a core function.
Last edited 04 May 2021 by acemang