It wasn't excel, but I 100% used google sheets as a database...it's a miracle it works, and it's running on a fairly prominent site (a version of it anyway). I hated myself the whole time I was coding it, but it worked, and the client didn't care.
In all seriousness, this crosses my mind every now and then and I always wonder how viable it would be as a solution. If you’re dealing with very simple flat data, it does have some built-in pros if you have clients who are already familiar with Google Sheets and most likely wouldn’t log in to a CMS to make updates, but have some data on a website that needs to change somewhat regularly (I.e. prices, dates).
High adoptability and built-in access control are nice, but obvi it’s not really meant to be used that way so lack of support and potential for breakage may negate that I guess.
You’re not wrong…and in all seriousness, this was a case where the design led to most of the issues (building a periodic table is a mess to start with). I’ve had the same thought as you…most folks know spreadsheets at least well enough to enter their data, so the training should be minimal at best.
That said, it’s not at all WYSIWYG, and any styling would need whoever’s doing the entry to know at least a little bit of HTML and/or CSS…but if you’re doing a static site where the content is more or less stable, it’s not the worst idea.
It wasn't excel, but I 100% used google sheets as a database...it's a miracle it works, and it's running on a fairly prominent site (a version of it anyway). I hated myself the whole time I was coding it, but it worked, and the client didn't care.
In all seriousness, this crosses my mind every now and then and I always wonder how viable it would be as a solution. If you’re dealing with very simple flat data, it does have some built-in pros if you have clients who are already familiar with Google Sheets and most likely wouldn’t log in to a CMS to make updates, but have some data on a website that needs to change somewhat regularly (I.e. prices, dates).
High adoptability and built-in access control are nice, but obvi it’s not really meant to be used that way so lack of support and potential for breakage may negate that I guess.
Anyhows, thanks for sharing your project!
You’re not wrong…and in all seriousness, this was a case where the design led to most of the issues (building a periodic table is a mess to start with). I’ve had the same thought as you…most folks know spreadsheets at least well enough to enter their data, so the training should be minimal at best.
That said, it’s not at all WYSIWYG, and any styling would need whoever’s doing the entry to know at least a little bit of HTML and/or CSS…but if you’re doing a static site where the content is more or less stable, it’s not the worst idea.
There are 5 rules now... :D
For the curious (or those who want to point & laugh 😆), this is one of two here that are built the same way.
This was such an annoying project…the build was insane, but dealing with governmental entities? Nah, I’m ALL KINDS of good! 😂
fdrlibrary.org/New-Deal-Periodic-T...