974321 - Create makeprompt tags for Training content

Status: RESOLVED FIXED

(Webmaker Graveyard :: MakeAPI, defect)

Description

[Laura Hilliger [:epilepticrabbit]]

For the training content, we prompt people to make stuff using our tools. I would like to have a way to show the user all of the prompts on webmaker.org via a search. 

I experimented by tagging one make "makeprompt1", but, naturally every time someone remixes it, their make is added to the search:

https://webmaker.org/en-US/search?type=tags&q=makeprompt1

Can we set up a few tags (makeprompt, makeprompt-1, makeprompt-2) that I can assign in the back end, which don't get copied on remix (this is how it works for webmaker:teach-1 or webmaker:privacy-1, I think?)

What makes sense to me:
--User should be able to see ALL makeprompts for training
--all make prompts for a specific module (e.g. "module1-makeprompt1, module1-makeprompt2")

We'll have about 9 make prompts per module.

too complicated? Advice?

Comment 1

[Cassie McDaniel [:cassiemc]]

Not sure what you're trying to accomplish exactly. This seems a bit like a workaround and there may be a better ux and technical solution. 

Can we back up a step and describe what you want users to be able to do (which I understand a bit of from the above), and then what you would like to do on the backend as the training "coordinator"?

Comment 2

[Laura Hilliger [:epilepticrabbit]]

Sure!

The user sees a bit of text that says "Make this thing..." and a button that indicates "Stuff other people have made" or "here's a template/example". When the user clicks the button, they're taken to a specific set of makes on webmaker.org. Which they can then interact with as normal.

I/Team have the ability to say what makes are in that specific set, and in what order, instead of everything made on webmaker with that tag (e.g. remix cancer). 

Just like the privacy page: https://webmaker.org/privacy-makes
or the teach page currently.

I think this is, in some way, connected to bug 887568 (which is iceboxed, sadly) or the custom galleries bug that I can't find. We don't have a way to surface good content without this work around.

Comment 3

[William Duyck [:fuzzyfox]]

This could also be solved TTT platform side as well using the existing functionality of the new makegalleries (iirc) so I guess a piece of this is where we want users to see these makes and how that affects user flow/experience between systems.

(IIRC the galleries make use of the same process available in the makeapi client, where you can list make IDs or URLs, and create a gallery of just those makes.)

Comment 4

[Pomax]

the dependency bug has been uniceboxed, cade can you see whether this is now a doable thing?

Comment 5

[Chris DeCairos (:cade)]

I'm not clear on the requirements of this bug. 

Why not just use name-spaced (application) tags? i.e. `webmaker:makeprompt-1`, `webmaker:makeprompt-2`? Application tags are not applied to remixes - unless the remixing user is an administrator.

Alternatively, as Fuzzyfox mentioned, you could use the Make Gallery generating code to create makes of make-galleries with custom searches

Comment 6

[Laura Hilliger [:epilepticrabbit]]

Ok, happy to use application tags. We're building in a pull here: https://github.com/p2pu/school-of-webmaking/issues/65

Question: We will pull into training 4 separate times (one for each module). How do I tag separately for each module (they have 3 or 4 makes each)? 

Would it be:
Makes in Module 1 tagged with:
webmaker:makeprompt-1, webmaker:makeprompt-2, webmaker:makeprompt-3, 

in Module 2:
webmaker:makeprompt-4, webmaker:makeprompt-5...

or more like:
module 1:
webmaker:makeprompt-1-1, webmaker:makeprompt-1-2, webmaker:makeprompt-1-3
module 2:
webmaker:makeprompt-2-1, webmaker:makeprompt-2-2

Sorry for the confusion, just not sure the best way to set this up.

Comment 7

[Chris DeCairos (:cade)]

Either of those tagging patterns will serve your purpose. I think the second style might be a bit easier to work with. "webmaker:makeprompt-<module>-<makenum>"

Search for each module separately, including each makeprompt tag in the search. i.e. "webmaker:makeprompt-1" OR "webmaker:makeprompt-2"

Then sort by the tags client-side if order matters. If it doesn't then you probably don't even need to number the app tags, just specify which module it belongs to "webmaker:makeprompt-1"

Comment 8

[Laura Hilliger [:epilepticrabbit]]

Hi again Cade!

Thanks for the prompt responding. I went with "webmaker:modulename-makeprompt-orderingNumber", so :

webmaker:exploring-makeprompt-1

But the ordering doesn't seem to work. On this page: http://training.webmakerprototypes.org/en/building/make/ I have -1, -2 and so on. You said "order on the client side", so I'm guessing I need to add something to the js. As I'm not a coder, maybe you could tell me what to add?

THis is what I've got:

<script type="text/javascript">
			var gallery = new MakeGallery(
			{
				tagPrefix: "webmaker:building-makeprompt",
				limit: 6
			},
			".make-gallery",
			{
	    		apiURL: "https://makeapi.webmaker.org",
                hidden: ["tags"]
			});
</script>

Comment 9

[Laura Hilliger [:epilepticrabbit]]

also, if you happen to know why the display for individual makes is funky, like they aren't the proper height, that'd be helpful!

Comment 10

[Chris DeCairos (:cade)]

So I don't think that's possible right now with the Make Gallery. We may need to build in an option to pass in a JavaScript function that can manually sort the makes before HTML is generated.

The height issues are the content of the makes overflowing their containers. The CSS may need tweaking