pouët.net

ps: splendid initiative with the 14-day-crash-course! ♥

But please change "Day 1 - What's a Demoscene" to "Day 1 - What is the Demoscene"

I´m saying that because there have been people already that said things like "These people released a demoscene with..." or "i made a little Demoscene here" when they wanted to refer to "demos" and we really don´t want the people to get this wrong on Day 1 already, right? The Demoscene is singular, never plural.

After this last sentence of Day 1:

On this first day of the rest of your life you should probably google a bit more about the demoscene and watch some demos!

you should put a nice link...i´d like to propose this one...easy accessable/browsable (youtube) and has most newer Demos:
https://www.youtube.com/user/Annikras


Typos: needed fixes in BIG letters

Day 1:
Given all this knowledge, your mission, should you SHOULD to accept it

Day 2:
but it obviously takes some hefty amMount

Day 4:
Storing the function steps required to recreate the instruments proceduralLy <- missing letter L in "procedurally"
takes less space thAn storing the entire sample. <- A instead of E

Day 5:
You'll need to learn about variables, functions, classes, data structures, loops and algorIthms <- I instead of Y in "algorithms"

you should focus on the language you're most interested or coMfortable with.

graphical canvas for you to GET dirty with pixels <- missing word

You should do demos as it feels more natural to you <- i would use MOST instead of MORE here, just a suggestion

Day 6:
There are many types of tools, some are comMercial

Day 8:
I dont know, but this seems not to be a real sentence at all:

Building up a bunch of different effects and then trying to find a soundtrack to glue them all together into something nice.

I´d change it to:
Build up a bunch of different effects and then try to find a soundtrack to glue them all together into something nice.


That´s it...atleast what i found while just reading it through once.
I am just trying to help, so please don´t think i want to blame you or sth! ;) I am just a good proof-reader as typos directly jump into my face somehow.

All in all i love what you have there so far!
I will pinpoint newbies to this for sure in the future! :)

hardy: the title is purposedly wrong because a newb doesn't know the difference. in the actual text i make a distinction to what is a demo or entry and what is the demoscene in itself. i might fix it though, let me think about it.

thanks for the other typo finds and suggestions, i'll go through them on the next text revision :)

i guess i should also have a list of reviewers somewhere to credit this kind of help :)

Just in case you missed this when the new page started :)


And any graphician who provides a better logo will earn my undying thanks!

ps, drift, I finally watched the relevant part of MDT! Thanks very much for the publicity!

I have an initial metadata list and would appreciate any feedback on whether the listed fields would be useful in searching for resources.

Yes, let's make sure to alienate people right off the bat by making them feel stupid for getting something wrong. Sounds like the perfect way to onboard people.

(FYI: getting stuck up on minutiae like this is what hurts all subcultures, including our own)

"Oh, you make those demoscenes? Super cool, tell me mo.."
"THEY'RE CALLED DEMOS! NOT DEMOSCENES!"

No thanks. :)

gloom: Sure, let's not be dicks to people who get the terminology wrong. But if we can avoid laying the traps that create that confusion in the first place, that's got to be a good thing, no?

(personally I *like* the quirky wording of "What's a Demoscene"... but I suspect the quirkiness will be lost on the people the document is aimed at.)

What gasman said, and in addition it might stick to the reader's brain while reading so it will possibly just amplify the effect of remembering the "wrong" wording.

wrote a couple more chapters. almost done with first draft. think it might be a bit too boring to read. not sure what to do to spice it up a bit. maybe rewrite some of the more boring parts? also thinking of asking a scener to do an illustration for each of the chapters. and turn the .md into a webpage.

ps: illustrations and web both sound good. Maybe a walkthrough of a small js demo tying the chapters together? Canopy might have something. Also, somebody released a nice underwater-themed js demo in the last year or so, but I don't remember who. I recall he did three demos with increasing levels of sophistication.

When you switch to a web page, would you be willing to put each chapter in its own htm so I could index them individually?

anchors on one same page not good enough?

Could the anchors include some with a defined format, e.g., for day 3, not just #gfxintro but also #start_doc03 or something? I would like to tag each day with the relevant metadata, and I can do that as long as I have consistent markers. Then I can read the all-in-one htm, split it at //a[starts-with(@name, 'start_doc')], and index each chunk individually. Sound reasonable?

yeah, should be doable

first post mentioned branch's video but not a link, so here it is, for archival purposes only :D
https://www.youtube.com/watch?v=ZuOUynjAcOM

finished the 1st draft of teach yourself demoscene in 14 days

have to do a full review and think a little on what could be improved / rewritten.

started asking for graphician to do some images to include in it.

will turn it into .html with chapter anchors eventually

\o/

I've got a few articles about our Pico-8 demo here. As most of that community isn't familiar with demos there's a brief bit about the scene, how different classic effects work and what a basic demo engine should contain.

This might be out of scope but I did a video on how Amiga tracker chipmods are made. It's here

4mat: thanks for the links (and the music :) )! The video is certainly within the scope of howto, and I'll add it to the index... as soon as I replace the dead PSU in my dev machine :/ .

cxw: just realized that github.com markdown viewer page already has markers by default

https://github.com/psenough/teach_yourself_demoscene_in_14_days/blob/master/README.md#day-6---tools-and-resources

so technically, it's already a webpage with anchors for each chapter, no need to reinvent the wheel unless it's to give it some sort of stylish look.

proper link actually should be:
https://github.com/psenough/teach_yourself_demoscene_in_14_days#day-1---demoscene

4mat: links added!

ps: Nice! I'll hack on an indexer for GH md with anchors. Thank you!

all: I have the first version of search working on my local machine - code is at github if anyone cares. ;)

I will post again when it's live on the web! In the meantime, I still welcome any assistance, e.g., getting all the links from this thread into the sources page or critiquing the metadata list.

Getting closer - now on Bitbucket, split off from the framework. Live on planet-d soon!

Beziers galore: https://pomax.github.io/bezierinfo/