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

The documentation should be structured better #19

Closed
peter-b opened this issue Oct 23, 2015 · 5 comments
Closed

The documentation should be structured better #19

peter-b opened this issue Oct 23, 2015 · 5 comments
Assignees

Comments

@peter-b
Copy link
Contributor

peter-b commented Oct 23, 2015

The top-level README file (which is also shown on the package page) needs to be more helpful. Specifically:

  • Installation instructions need to be more prominent, and need to link to the Atom documentation for "how to install packages". Optional dependency packages need to be listed with links to the appropriate packages' pages.
  • Add links to the package pages and/or documentation for Atom features that the package integrates with, including indentation, auto-completion, snippets, and linting.
  • Provide very basic instructions for downloading/extracting LiveCode Server for LCS linting support.
@peter-b
Copy link
Contributor Author

peter-b commented Oct 23, 2015

Given the feedback on the 0.6.0 release our documentation is unclear enough to basically be a bug. 😭

@montegoulding
Copy link
Member

One option would be to include the server engine in the package so it works out of the box. It does mean maintaining that though.

@peter-b
Copy link
Contributor Author

peter-b commented Oct 24, 2015

@montegoulding I don't think that it's very practical to include the server engine in the package 😨! I think the correct thing here is to make the server engine easier to install into the system path, possibly by proving both "Install Shell Commands" and "Install LiveCode Server" functions in the IDE somewhere. I've been meaning to file an IDE feature request for a while, so I'll make that a higher priority.

@peter-b peter-b added this to the v0.6.1 milestone Oct 24, 2015
@montegoulding
Copy link
Member

Yes please!

@peter-b peter-b self-assigned this Oct 24, 2015
@peter-b peter-b modified the milestone: v0.6.1 Oct 27, 2015
@peter-b
Copy link
Contributor Author

peter-b commented Oct 29, 2015

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