Ask coding questions

← Back to all posts
Repl.it — Why can't we have lengthy descriptions on spotlight pages?
fuzzyastrocat (1850)

This is a meta-question. Could there be some kind of feature on replit where we could have a lengthy description on a spotlight page? Or maybe a way to "link together" a spotlight page and a corresponding repl talk post?

I ask this because I'm getting more and more comments on my programs wondering about how to use them or about things not seeming to work right. Even though I've explicitly addressed all these issues in the repl talk posts for these projects, it seems many people are getting to things directly through the spotlight/apps interface (which I like the idea of, don't get me wrong) and so they end up asking already answered questions.

I know I could just put the link to the repl talk post in the repl's description, but people would just skip right over that. However, some kind of eye-catching feature to have a longer description would get people to check it out before they ask questions.

Does this idea make sense in your opinion? Is there something I've overlooked that would solve this, or maybe a better way to address the issue?

Comments
hotnewtop
FlaminHotValdez (694)

or just turn off the repl's spotlight page

FlaminHotValdez (694)

@fuzzyastrocat OK wait no you can't...However, what you CAN do is turn off comments.

fuzzyastrocat (1850)

@FlaminHotValdez Eh, then people would get mad that I'm blocking them out probably but thanks for the idea

RoBlockHead (521)

Spotlight pages are designed to put the Repl in focus, not a long essay about the repl. This is by design.

fuzzyastrocat (1850)

@RoBlockHead Then I think spotlight should be removed because that doesn't work with the new apps interface. You can't throw complex software at people without any explanation and expect them to use it just fine. (Some things like games work fine without this, but lots of other things don't.)

RoBlockHead (521)

@fuzzyastrocat if you need a long explanation, just use a readme file

fuzzyastrocat (1850)

@RoBlockHead See my response to Coder100's comment about that.

Coder100 (18238)

Ideally, you would want to put this in either your code (readme.md) or embedded inside the website.

The description is meant to be like a 'blurb' to say what it does, not how to use it. That is the difference between apps and repl talk.

In my opinion it encourages people to describe usage on their repl more lol

fuzzyastrocat (1850)

@Coder100 I never said that I thought the description should be how to use it, I'm saying there should be something else that does describe how to use it. (I agree about the blurb thing.)

As for embedded in the website, that's not always possible. Case in point: someone asked "Why is Askew showing up all blank here?" That's because you can only run it from the fullscreen .repl.co link — but of course, I can't put that on the site itself since it won't run if you don't go to that specific site.

As for embedded in the repl in a readme, that's a good point. However I'm not thrilled with the way repl handles that since the readme always shows up as a tiny little area (vertically that is) at the bottom of the repl's spotlight view, which most people (me included) will just ignore. If repl wants to do that, they should make the readme take up the entire repl area when previewing it.

Coder100 (18238)

@fuzzyastrocat yeah maybe
that's why the get help exists

fuzzyastrocat (1850)

@IronStarkMan Ahh that, I thought Coder100 was referring to a feature on Spotlight pages to 'get help' about the repl. I just posed this question here to see if I had missed something or if there was a better way to do it.

TsunamiOrSumth (545)

i dont really see a need to put longer descriptions, as there probably isnt much need to fill such a large space, but they could implement attached links (etc. github, talk post)

fuzzyastrocat (1850)

@TsunamiOrSumth That would be my preferred solution as well, though I think adding a space for a lengthier description could essentially merge repl talk's "share" function and the spotlight pages.