Skip to content

New wiki : Issues and suggestions #6946

Open
raisedadead opened this Issue · 12 comments

4 participants

@raisedadead
Free Code Camp member

The new wiki is just great.

A few things to discuss though refering to the screenshot below:

1

1. Need to fix the titles
The titles appear twice in some of the entries, because one is rendered from the file name and the other is from the # heading used by the author in the article itself.

This should be an easy fix, by removing the # heading and adding a one liner intro text? or may be just removing.

2. Broken Images
Of course in some of the articles the images were relatively linked to the .md file and the github wiki worked, this has to be replaced.

Since you guys have worked on this maybe you could suggest how it works so the links can be fixed. One thing that I can say is making them absolute paths but I am concerned about breaking things.

3. Update Wiki Contribution guidelines
We may need to revisit the wiki contribution guidelines so that the new articles are inline with what the styling if the new wiki, for example Point 1 about titles.

Other general guidelines such as Image sizes, using markdown styling, etc

Trivial things:

Consider a different font style:

This might be just me, but IMHO the white space and the thin font is actually not going so well.

Consider increasing the width of the panel on wide screens?

Okay I know I am just being picky on this one, but it would help in more readability, of course we can let this one go if its too costly UX wise. :wink:

Please add other points that I might have missed above.

And amaaaaazing work on the new wiki, I just love this! @SaintPeter @hallaathrad @awesomeaniruddh and others, You all rock :sparkles: !!
@raisedadead
Free Code Camp member

Not to mention if you guys agree, I can take up fixing some of the things :wink:

@SaintPeter
Free Code Camp member

We have some substantial refactoring to do on the Wiki, including what you describe. This is going to involve some architectural changes. Really appreciate the offer, but let us hack on it a bit before we release the hounds.

I'm about to file an issue that describes what I'm thinking. Feel free to follow along. ;)

@raisedadead
Free Code Camp member

Oh that's cool! Thanks :+1:

@QuincyLarson

@raisedadead @SaintPeter what's the status of this issue? Have all of these problems been solved?

@hallaathrad
Free Code Camp member

subscribing :+1:

@raisedadead
Free Code Camp member

@hallaathrad @SaintPeter If we could discuss this whenever you have some time, It would be great if any of you can brief me on the current architecture, and any plans or things you are already working? I'll try and help

@raisedadead
Free Code Camp member

ToDo: consider wiki issue FreeCodeCamp/wiki#364, while working on this.

@hallaathrad
Free Code Camp member

Pull request #6938 may solve part of this.

@hallaathrad
Free Code Camp member

Relevant comment by @d3ddd at #7475

Is there a way to search the wiki for "frozen" or "stuck" or "reset" and have this wiki article return as a result?

Reposting here to keep alive while closing that one.

@raisedadead
Free Code Camp member

Taking additional issue from #7486 as mentioned by @jstoebel

When I pull up the wiki sidebar, and click Template, nothing happens. The request gets no response

fcc_screencap

@raisedadead
Free Code Camp member
@raisedadead
Free Code Camp member

@evaristoc found that the wiki redirects the camperbot link on the main page at freecodecamp.github.io/wiki redirects to the beta page of freecodecamp.

Adding it to this for future.

@raisedadead raisedadead added the wiki label
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.