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

Malformatted documentation issues aggregation #5253

Closed
JAremko opened this issue Feb 25, 2016 · 8 comments
Closed

Malformatted documentation issues aggregation #5253

JAremko opened this issue Feb 25, 2016 · 8 comments

Comments

@JAremko
Copy link
Collaborator

JAremko commented Feb 25, 2016

Here I will link issues and refer links in README.org files that looks ugly when viewing via GitHub

The list:

@JAremko JAremko changed the title Malformatted links in the Spacemacs documentation Malformatted documentation aggregation issue Feb 25, 2016
@JAremko JAremko changed the title Malformatted documentation aggregation issue Malformatted documentation issues aggregation Feb 25, 2016
@TheBB
Copy link
Collaborator

TheBB commented Feb 26, 2016

Malformed link in Vinegar layer's README.org when viewing via GitHub

@TheBB
Copy link
Collaborator

TheBB commented Feb 26, 2016

this link probably should be reformatted - it looks weird.

@TheBB
Copy link
Collaborator

TheBB commented Feb 26, 2016

I think : should be removed here and here for the consistency. Also it will make solving #4399 easier.

@TheBB
Copy link
Collaborator

TheBB commented Feb 26, 2016

Same with the go layer, Haskell, js, lua... and IPython Notebook layer has this Micro-state: =ipython-notebook= paragraph. Might be we should stick to a-z A-Z 0-9 paragraphs? This way they will be more readable, searchable and can work on the GitHub.

@TheBB
Copy link
Collaborator

TheBB commented Feb 26, 2016

Wakatime layer's table of contents is broken on GitHub.

@TheBB
Copy link
Collaborator

TheBB commented Feb 26, 2016

The documentation doesn't show anything usefull via GitHub

@TheBB
Copy link
Collaborator

TheBB commented Feb 26, 2016

(All comments above originally by @JAremko in the linked issues.)

@JAremko
Copy link
Collaborator Author

JAremko commented Feb 26, 2016

And who's spamming now 😄

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

No branches or pull requests

2 participants