Hello!
Please tell me about your approach.
---
I am working everyday on the project Web As You Wish. As I work, I adjust some definitions.
What I have at this very moment:
- everything happens on your browser, I am amazed like the tool (webpage) itself is becoming lightweight and simple
- the tool (webpage) itself is being constructed in vanilla HTML/CSS; but I am using a small trick the HTML e CSS is fragmented in dozens of source files (easy and safe to edit each one) that I merge in the final tool
- making it work on smartphones is not a goal, but may happen (not sure), of course that is not the adequate device
- as the opposite of the initial plan, there will be no need for JavaScript (probably)
- vanilla HTML and CSS (100% readable and short)
- the minimal subset of CSS as possible: robust/intuitive/pragmatic pattern; for example, everywhere: box-sizing: border-box
- avoiding CSS inheritance as possible (we want to change one thing without breaking other)
- all font-sizes are 'rem' (thank you, Jason Knight)
- instead of CSS flexbox, it uses auto-adjusted blank spacers (media query under the hood)
- resulting website granted to look fine on IPone5 (320px wide); no need for horizontal scroll
- resulting website granted to look fine on standard laptop (around 1300px wide)
- the both above are the main references; anything between should look fine (maybe using customizable spacers here and there)
- for wider screens, or the user don't want the webpage to fill the whole screen (1300px is OK) or he will zoom it (this may change)
What are my anguishes:
- there are 2 ways to go:
A) the tool is VERY opinionated, you don't insert your own HTML/CSS *code*; that's good because there will be zero chance that you break something (of course, you always can edit the resulting webpage somewhere else; the bad side is that I will have to give a LOT of fonts and predefined models)
B) the tool is liberal and accepts insertion of your own HTML/CSS *code*; this saves me a LOT of work, but I bet that, most of the time, the inserted CSS rules will conflict with my pattern
I am inclined to go the 'A' way. I don't need to offer every possible model of the universe. If we can fast and easily construct 90% of the existing websites in plain HTML/CSS... we have a winner!
fonts: (at start) I will offer the most used fonts, and create in the tool a feature for insertion of custom font code (@font-face); (future) offer directly all fonts
- market:
this will be an open source tool, free to use for everyone, except some giants that run thousands/millions of websites
- help:
help is very welcome and needed, especially for constructing models (I am a VERY bad designer; no, wait... I am not a designer at all); help on programming is welcome also, but the fact is that there is not much to program, the trouble is constructing the CSS patterns/models
---
When I have the early prototype, I will create a GitHub project and warn you here in these replies.
Thanks
