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

missing steps in documentation #64

Open
andrew-g-za opened this issue Aug 31, 2019 · 3 comments
Open

missing steps in documentation #64

andrew-g-za opened this issue Aug 31, 2019 · 3 comments

Comments

@andrew-g-za
Copy link
Contributor

I've opened this issue to see if there is something i can help with.

So far while working through the guide i've noticed small steps have been omitted (noticeably from step 5 onward).
My question is if this is intentional - i.e. left to the reader as an exercise, omitted to save space, or if its just a small oversight?

For example:

  • step 5 - did not show the necessary changes to the index.ftl template to display the 'backup' button
  • step 5 - mentions a new query - all-pages-data - but omits the changes to the SqlQueries enumeration and the database verticle loadSqlQueries method.
  • step 6 the apiGetPage method requires a new database service method fetchPageById that is not mentioned at all (along with the corresponding changes to the db-queries.properties file, SqlQueries enum etc)

Hopefully by this point in the tutorial the reader should be reasonably comfortable making the necessary changes without being show explicitly, so perhaps all that is required is a tip / note to remind the reader to make the changes on their own, rather than discovering something is missing when their IDE complains?

I'm happy to help out with some changes if you like - just let me know what sort of style to follow - full step-by-step instructions or just a reminder.

@jponge
Copy link
Member

jponge commented Sep 2, 2019

Some items may be missing due to the code base evolving, so yes please propose changes. Sometimes a note/reminder is enough, sometimes text should be added.

@andrew-g-za
Copy link
Contributor Author

andrew-g-za commented Sep 2, 2019

Thanks @jponge - i'll use my judgement and make the changes I think match the circumstance. This week is pretty busy for me, so it will probably only be toward the end of next week or the week after.

@jponge
Copy link
Member

jponge commented Sep 2, 2019 via email

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

2 participants