-
Notifications
You must be signed in to change notification settings - Fork 803
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
Experimentation: non technical homepage #646
Comments
I think we should also use an illustration to explain what is Asciidoctor, something like: AsciiDoc syntax comes in, HTML5 comes out, easy! |
Why not :)
I think we could use http://gist.asciidoctor.org for the "try-it" button
even though this application will ask for a GitHub account (but this is not
mandatory).
Le 13 janv. 2017 5:41 PM, "rockyallen" <[email protected]> a écrit :
… [image: try2]
<https://cloud.githubusercontent.com/assets/5837117/21937211/4aed9dbe-d9ae-11e6-98ce-6de5d5e92f6a.png>
Same idea, but even simpler. Is there an online editor/preview for the
Try-it button?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#646 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAUV3Bmid0DHegBOl1RB3hAvIEizqsI7ks5rR6kvgaJpZM4Lir-K>
.
|
This would be good opportunity to improve navigation and make it feel more like an integrated website:
Asciidoctor (=home page) |
Current situation
The current homepage introduces a lot of technical details. If you are a technical person, this is good because, you can start right away and download the
asciidoctor
Gem or checkout the source from GitHub.On the contrary, if you are a non technical person, you will most likely move on... It's a pity, because we now have "low barriers" tools that are using Asciidoctor. For instance, I think a non technical person can install the Atom editor and the AsciiDoc preview package without too much trouble. Or write some AsciiDoc in Microsoft Notepad 🙈 and then use the Chrome extension.
Proposal
I've removed all the technical details except the source code block in the AsciiDoc syntax example.
The structure of the page is:
Basically:
Let me know what you think 😉
The text was updated successfully, but these errors were encountered: