Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reformatting skin element list pages #2589

Open
NoffyNoffeh opened this issue Sep 20, 2019 · 4 comments
Open

Reformatting skin element list pages #2589

NoffyNoffeh opened this issue Sep 20, 2019 · 4 comments
Assignees

Comments

@NoffyNoffeh
Copy link
Contributor

image

Current organization of skin elements is very tedious to parse, probably need to aim for more tables organized similar to old wiki.

@cl8n cl8n modified the milestones: Candidate Issues, October 2019 Sep 20, 2019
@cl8n
Copy link
Member

cl8n commented Oct 22, 2019

did u want to do this urself ?

@sr229
Copy link
Contributor

sr229 commented Oct 22, 2019

@dorothy3242 I suggest when opening issues like this, you have to implement fixes yourself since some of us are busy in other areas of the wiki.

@peppy
Copy link
Member

peppy commented Oct 22, 2019

That's not how github issues work. Issues are made to document issues, not "only made if the reporter is going to fix it".

@RockRoller01
Copy link
Contributor

So, I have given this a try and run into some formatting problems. You can not put multiple lines into a single field, making it so that you can not put the notes into the table at all. This is fine for things like e.g. the default numbers since they all share the same notes
image
But for things like the hitcircle elements its a major problem, leaving you with an essay long list
image

If anyone got an idea on how to deal with this please let me know, otherwise I will drop this, since this would just transform the article from one mess into another

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants