Open freetonik opened 3 years ago
@freetonik Excellent, I'm in agreement with the goal for the guide.
Few more loose thoughts:
To view source CMD+SHIFT+U
in one browser vs To view source CONTROL+SHIFT+U
in another. At first consider just writing the guide for say FireFox.I don't know if it would be pedagogically correct but I like the idea of starting with an 'invalid' fragment in an HTML file, example.html
like
This is my first webpage
And eventually building up with incremental explanation to something like:
<html>
<head><title>Hello!</title></head>
<body>
<h1>Hello, world</h1>
<p>This is <strong>my</strong> first webpage</p>
<style>
body {background: red}
</style>
</html>
I would consider moving these out of the initial scope of the CSS guide into the Where next section
- Typography, accessibility, contrast
- Media queries explained via necessity for mobile/desktop responsivity
The ultimate goal is to excite a bit of wonder at the possibilities of the web, I suppose.
Hi,
Consider settling on a cross-platform minimal text editor with HTML syntax highlighting, to recommend/require for the guide? (nothing ideal comes to mind, frankly)
Yeah, nothing ideal comes to mind indeed. I suppose it's safe to recommend VS Code. While not minimal, it's easy to install and works out of the box with everything needed for HTML.
As for the browser: ideally we create a system that will adjust the guide based on the browser/platform the student is using, e.g. To view source CMD+SHIFT+U in one browser vs To view source CONTROL+SHIFT+U in another. At first consider just writing the guide for say FireFox.
Good idea! Will do.
I don't know if it would be pedagogically correct but I like the idea of starting with an 'invalid' fragment in an HTML file
These are exactly my thoughts behind the Browser as text file viewer
part of the outline: start with plain text, demonstrate that the browser can actually render it as is without problems, then explain why and how proper HTML structure is needed.
Blot has the ability to 'write' stuff into the folder of the blog. Could we take advantage of this during the guide? Could the interactive aspects of the guide (embedded text editor / browser?) actually interact with the user's folder?
Interesting! Something like this?:
One problem I see is keeping text editors and files in sync. To avoid this and simplify things, alternative logic:
In terms of an exercise, something which would be useful to me would be to teach users how to use the developer tools to determine which styles are applied to an element, and how to edit those styles.
Good idea, will incorporate this.
I would consider moving these out of the initial scope of the CSS guide into the Where next section
Agreed.
Browser as text file viewer
– perfect! I'm not a connoisseur of intro-to-HTML courses but I do search for some every so often when someone asks me for a recommendation: I haven't come across one that tackles the Browser as text file viewer
nicely. Very goodalternative logic
proposal sounds great. One note: I definitely don't consider it a requirement for the first release. Just wanted to raise it as a potential idea down the line
Hey @davidmerfield , below is a draft outline of the proposed HTML/CSS guide for Blot users. The goal is to quickly cover the basics and provide starting points for further self-exploration. By the end of the guide, the user should be able to make basic HTML pages with styling, and at the very least, be able to ask questions in order to learn about more advanced topics.
Let me know what you think. Thanks!
<style>
tag