retoor/devplacepy
1
0
Fork 1
Code Issues 1 Pull Requests 4 Actions Packages Projects Releases Wiki Activity

Introduce Yourself Popup #175

New Issue
Open
opened 2026-09-27 08:03:39 +02:00 by retoor · 3 comments
retoor commented 2026-09-27 08:03:39 +02:00
Owner
Copy Link
Copy Source

Summary

Introduce Yourself Popup

Steps to Reproduce

Please implement a nice popup window using existing base components in a dry way that will ask the user to create a introduction to user self. It should provide some examples of what to write to make it low effort for users while still being provided with the interesting information. I think it should show after every 24h once and max ten times. When then still ignored, it should become a small link / notice on the profile page that the user did not introduce himself yet. If it did, there will be a link to the introduction post instead. Keep it n kind they the post can be deleted and they it should have consequences for the link and introduced status. The popup should literally never done back when it was once disabled in any scenario. It must be friendly and make clear what kind of community we are. Small enough to build relationships by design. Literally all functionality providing this, is already implemented. Preference is a dry solution unless a dry solution would break not de isolated module functionality. Do not reinvent the wheel. Basic workflow for providing new features of devplace should be executed for perfect integration.

Expected Behaviour

Not provided.

Actual Behaviour

Not provided.

Environment

Not provided.

Reported by retoor via DevPlace.

## Summary Introduce Yourself Popup ## Steps to Reproduce Please implement a nice popup window using existing base components in a dry way that will ask the user to create a introduction to user self. It should provide some examples of what to write to make it low effort for users while still being provided with the interesting information. I think it should show after every 24h once and max ten times. When then still ignored, it should become a small link / notice on the profile page that the user did not introduce himself yet. If it did, there will be a link to the introduction post instead. Keep it n kind they the post can be deleted and they it should have consequences for the link and introduced status. The popup should literally never done back when it was once disabled in any scenario. It must be friendly and make clear what kind of community we are. Small enough to build relationships by design. Literally all functionality providing this, is already implemented. Preference is a dry solution unless a dry solution would break not de isolated module functionality. Do not reinvent the wheel. Basic workflow for providing new features of devplace should be executed for perfect integration. ## Expected Behaviour Not provided. ## Actual Behaviour Not provided. ## Environment Not provided. --- *Reported by **retoor** via DevPlace.*
retoor commented 2026-09-27 08:12:54 +02:00
Author
Owner
Copy Link
Copy Source

Ticket 175 like it's nothing. TypoSaurus will soon have it's last final rewrite because now, now I know the right choices to make. I believe in writing everything yourself but the ultimate result would be one Muse agent. Just poll tickets. Claim it with a comment. Fetch the claimed ticket and just checkout a new repository instance and let Muse execute the Claude workflow. It's fast, cheap, perfect. I have no idea how to improve that. Still, will literally hack the process memory for one tiny change that meta as only one does not allow. Optimists.

Posted by retoor via DevPlace.

Ticket 175 like it's nothing. TypoSaurus will soon have it's last final rewrite because now, now I know the right choices to make. I believe in writing everything yourself but the ultimate result would be one Muse agent. Just poll tickets. Claim it with a comment. Fetch the claimed ticket and just checkout a new repository instance and let Muse execute the Claude workflow. It's fast, cheap, perfect. I have no idea how to improve that. Still, will literally hack the process memory for one tiny change that meta as only one does not allow. Optimists. --- *Posted by **retoor** via DevPlace.*
retoor commented 2026-09-27 08:16:13 +02:00
Author
Owner
Copy Link
Copy Source

@Lensflare / @blindxfish this a good introduce yourself flow for the site? I do want to enable the process also for existing users. Lensflare has nothing to do with photography for example. It was the name of his cat.

Posted by retoor via DevPlace.

@Lensflare / @blindxfish this a good introduce yourself flow for the site? I do want to enable the process also for existing users. Lensflare has nothing to do with photography for example. It was the name of his cat. --- *Posted by **retoor** via DevPlace.*
retoor commented 2026-09-27 19:58:25 +02:00
Author
Owner
Copy Link
Copy Source

IMO its nice to make people introduce themselves.

Posted by blindxfish via DevPlace.

IMO its nice to make people introduce themselves. --- *Posted by **blindxfish** via DevPlace.*
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
typosaurus retoor
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: retoor/devplacepy#175