Hi there, we were thinking about opening up starter projects for community contribution I'd gladly welcome more starter projects, if anything!
Let's just look at a few ideas first. Remixing has been an important part of Hopscotch.
From Hopscotch's blog: Build Responsibly (it is from a while back but it has relevant general ideas):
Branching is a generative action for the community
. With branching, the end of one person’s project is the beginning for someone else, so this cycle of creation and play can continue to build on itself indefinitely. Liking, while a positive reinforcement for the author, doesn’t have the same rich and productive benefit for the community.
Branching [...] typically requires more effort on the part of the brancher
. If you’re branching a project, it’s likely you want to look “under the hood” and learn from the code or you want to share your ideas and add to the project.
[...] competition reduced collaboration, one of the most effective and fun ways to learn.
(I am just providing this as ideas for reflection )
If you are interested in more, here is some from another community, but it captures the same fundamental ideas
Creator's Code on Paper:
Great creative environments don’t happen by accident. They’re a mix of the people that inhabit them, and the structure of the place where those people gather. They’re the open mic night where newbies take the stage right after practiced masters. We want to make a place where you feel safe standing where you are, but are also inspired and encouraged to go somewhere you’ve never been.
Have humility. Paper is a place where someone who joined yesterday can remix the works of masters. The best artists understand that they always have something to learn.
Start conversations. We don’t want Paper just to be a gallery where you can’t touch anything. Paper is a place for conversation. Instead of thinking “What can I make to blow everyone away?” try “What would make a bunch of people inspired to remix me?”
A concern I was reflecting on myself was that I was finding myself looking less behind the scenes for projects and yet I learnt so so much from doing this when I first came onto Hopscotch.
We voted in polls on project interaction and this is one example:
(It is not about people in particular or anything in the least — I am just showing the results of a poll. Feel free to go and vote in it by the way.)
Now with that said, people have expressed interest in making starter projects I stress that we might not be able to get to look at everything.
If you are interested in creating a starter project, the starter project should
- Have simple directions to prompt the Hopscotcher
- Have code that and clear to follow through and understand
- Be open-ended: there are a number directions in which you can take the project
- Be fun to play and remix
I think in addition, it would be nice if:
- the project also stands on its own
- the project's code is set out in a way that makes sense: Will other people be able to work out what is going on in the code clearly? Do the variable names and object names describe what they're used for?
- If I want to change code for the main character, I might expect to look in the main character's code for example.
- I find it easier to look for code when the objects are in the same place as they are on the screen, just of the association with position (I don't have to go looking for the object) but may just be personal
This seems to be expanding into making your code easier for others to read, a large focus of coding actually :)
Hmm I wish these were friendlier terms, but this is from a programming book:
Write Programs for People First, Computers Second
The computer doesn't care whether your code is readable. It's better at reading binary machine instructions than it is at reading high-level language statements. You write readable code because it helps other people to read your code.
Readable code doesn't take any longer to write than confusing code does, at least not in the long run. It's easier to be sure your code works if you easily read what you wrote. [...] But code is also read during reviews. It's read when you or someone else fixes an error. It's read when the code is modified [and] when someone tries to use part of your code in a similar program.
Making code readable is [...] part of the development process, and favoring write-time convenience over read-time convenience is a false economy. [...] go to the effort of writing good code, which you can do once, rather than the effort of reading bad code, which you'd have to do again and again.
Not the main focus of this though
Edit in some ideas! These are free to use and free to make
- the start of a movie, but you remix your own ending
- Design your own card
- Design your own t-shirt (we previously had one of these actually)
- 'Welcome, my Hopscotch username is' template
- Home screen for a game
- Website Templates
- Mini Arcade Template with games
- A Website with a mini arcade in it
This also correlates a lot to @Rawrbear's Idea List of Doom! We created a ton of ideas for projects, so feel free to check it out here.
Thanks a lot to everyone who's been interested — it was more than I could have expected