4 ms·
On the landing page, I think a simple hero diagram would be helpful because this appears to be an uncommon approach that mashes-up familiar terms. I mean I ha
by brudgers 3y ago
On the landing page, I think a simple hero diagram would be helpful because this appears to be an uncommon approach that mashes-up familiar terms.
I mean I have some familiarity with "dynamic websites" and "just SQL Queries" but no clear picture of the mechanics.
When I hit a landing page, my first questions are:
What is it?
What does it do?
Should I care about it enough to invest more time?
I clicked "try it out" but it didn't start to answer my questions...instead it asked me questions.
Anyway, Congratulations on launching. I know that's hard.
- lovasoa 3y agoThis is a very good point, and I think I have a hard time explaining how it works technically without it sounding more complicated than it actually is. The diagram is a good idea, I'll do it. For a simple explanation, what do you think about: SQLPage is a web server that runs .sql files to answer web requests. For every request, it runs the SQL statements in the requested file one by one, passing the HTTP request parameters as SQL statement parameters. Then, it passes the results returned by the database to pre-defined HTML components to create a good-looking webpage that is streamed back to the user's web browser.
- zigh 3y agoThat explanation made it easier to understand, but I found the GitHub Readme much better explains everything. The little video and example helped a lot.
- lovasoa 3y agoI'll try to include more of the technical contents from github on the landing page, without making it too obscure for neophytes.