Publishing with content.
More questions added. Answers pending. Added See Also items
Publishing after many changes. One image removed due to error. Simpler images used. Updated milestones with citations.
Updated refs/citations to correct format. Replacing two refs that with links.
Publishing. Removed one image. Added two images. Added one question. Updated See Also.
Added item to Further Reading
Thanks. Once published, new changes go live immediately. No need to "publish again".
One comment was pending. I have added citations to the Milestones. Rest of the rework is fine, thanks. Please publish again.
OK, I will finish the rework as per the comments. Should I leave the references rework until you suggest how to improve them ?
One thing I forgot: The convention is to write milestones in present tense. Example: "Python 2.0 is released. The development of the language becomes more open and community driven."
The article reads well. I think it can be published after minor changes. 1. Milestones need citations. 2. Image in Summary is okay for a blog as a teaser image but in Devopedia it doesn't add much value. Anyway, can retain it if you wish. 3. Visualiza ...
Nice write up. Hope you have noted the sources so that you can add them as refs and citations. The content looks fine. I will do a more detailed review when the citations are in place.
Could you update the format of references? Study the format from the article on Flask. Reference should include author name, year of publication, date of publication, name of website, access date, etc.
please check and suggest improvements... i lost count of how much is changed since your last message :(
1. The graph in summary can be moved to a milestone for year 2017. Summary can focus on the main aspects of the language. Actually, the last three paragraphs of your summary are okay. 2. JS logo can be in Summary. 3. Answers can't easily be verified e ...