haxefoundation / haxe.org Goto Github PK

Currently we generate contribution links with line numbers on the page. This causes a lot of files to change whenever a line is added or removed from the .tex.

We should instead generate this link during the HTML conversion, using the information from sections.txt.

I've heard from several people that there are issues downloading the Haxe Windows installer when avast is running.

Hi

I believe that the page Who uses Haxe should go to the menu "community" since it has nothing to do with the foundation - at least in some cases

If you have any content for the "games" use case page, please leave a comment here.

We are looking for:

• Testimonials / Quotes: If you have used haxe for creating games and it has been awesome, leave a short 1 sentance quote, with your name, company and URL.
• Showcase: If you have a game you would like included in the showcase, please include the name of your game, an image for the carousel, and a 1 line description.
• Popular Libraries: If there's a library that is used by a large number of Haxe game developers and we've left it out, let us know.
• Tutorials: if you have a tutorial, please supply a link, a title, and a 1 line description.

Please note we are not going to guarantee that items posted here will be included.

Once we have enough content we can close this issue.

I think we lack a good page on how one can contribute to Haxe, or at least I didn't find one.

I believe it deserves an individual menu item that links to a page listing what can be done i.e.

• Report issues (a link to https://github.com/HaxeFoundation/haxe/issues, short description on how to create useful issues)
• Fix existing issues and contribute new code. We currently have a short "buildiing instructions" page, however it doesn't describe stuff like Neko installation and HAXEPATH/HAXE_STD_PATH env variables. A short intro into both OCaml and Haxe code structure would help a lot as well.
• Write documentation for the code (some style guide would be nice).
• Write content for the site ("contribute here" links are awesome, also need some info on how to add a new page).
• Mention "satellite" projects that could use some love, i.e. haxelib, hxcpp, hxcs, hxjava.
• Anything I forgot?

If you have any content for the "desktop apps" use case page, please leave a comment here.

We are looking for:

• Testimonials / Quotes: If you have used haxe for creating desktop apps and it has been awesome, leave a short 1 sentence quote, with your name, company and URL.
• Showcase: If you have an app you would like included in the showcase, please include the name of your app, an image for the carousel, and a 1 line description.
• Popular Libraries: If there's a library that is used by a large number of Haxe app developers and we've left it out, let us know.
• Tutorials: if you have a tutorial, please supply a link, a title, and a 1 line description.

Please note we are not going to guarantee that items posted here will be included.

Once we have enough content we can close this issue.

HaxeFoundation/haxe#3662

If you have any content for the "cross platform APIs" use case page, please leave a comment here.

We are looking for:

• Testimonials / Quotes: If you have used haxe for creating cross platform APIs and it has been awesome, leave a short 1 sentence quote, with your name, company and URL.
• Showcase: If you have an API example you would like included in the showcase, please include the name of your API, an image for the carousel, and a 1 line description.
• Popular Libraries: If there's a library that is used by a large number of Haxe app developers and we've left it out, let us know.
• Tutorials: if you have a tutorial, please supply a link, a title, and a 1 line description.

Please note we are not going to guarantee that items posted here will be included.

Once we have enough content we can close this issue.

On the main page, the A taste of Haxe section looks quite bad (at least for me):

IIRC this was different, i.e. shorters tabs and syntax highlighting.

Compare:

https://github.com/HaxeFoundation/HaxeManual/blob/master/md/manual/dictionary.md
http://haxe.org/manual/dictionary.html

It should be enough to add some margin between the individual paragraphs.

On that note, the HTML version does not allow anchor links like the markdown version does: https://github.com/HaxeFoundation/HaxeManual/blob/master/md/manual/dictionary.md#compiler-flag

These appear in quite a few places in the manual.

Hello @ncannasse, I took a look at the proto, and I think it's going in the right direction. My background is in design, and I hope you don't mind a little criticism. (it's kind of what we do).

The first and major piece, is the site branding. I would suggest going with Haxe Foundation for the main header bar, and then let "Haxe, The Cross-platform Toolkit" be the hero like it is now. This is a kind of metaphor that "Haxe is under this foundation, we care for it, and will continue to make sure its great with your help." I think maybe this is why you are still letting the Haxe Foundation section be "TODO" right now. It doesn't belong in the footer, but the very top as the brand, and at the very bottom with the date, copyright, or company citation.

For the navbar, I would suggest this:
{Logo} - Haxe Foundation - Products - Documentation - Get Involved - haxelib

• {Logo}: link to the home page.
• Haxe Foundation: Direct link the foundation site, that uses the same navbar, also a dropdown to drill down to specific pages on that site. Maybe the same as the nav on haxe-foundation.org right now, but with About changed to Mission.
• Products: Direct link to a page devoted to the different parts of the toolkit, also a dropdown to drill down to specific tools (haxe, neko, haxelib, etc.)
• Documentation: Direct link to Getting Started page, also a dropdown for try.haxe, the haxe API, and more important pages that are all really a form of documentation.
• Get Involved: This verbiage is very common, but I'm not really sure of it. Maybe Community is still just as good. It is a direct link to a page devoted to the overall haxe community online, including a section for the legacy presence, apps, and other items that will eventually be phased out. Overall it should be a list of links, but the hero of this page should only sell the most important places the core team spends most of their time (Github, Google Group, Google+, IRC, etc.)
• haxelib: This one is questionable, and may only belong in the Products dropdown, but I believe it is very important for discovery and should be on the main nav. It can just link to the haxelib site, which eventually can be designed with the same navbar and scheme.

The goal here of course is to create a cohesive brand that may be a conglomerate of multiple sites, but are tied together by the navbar.

The Admin item should be moved to the right of the search bar. If this site is going to host users and profiles, this is the location in the navbar that item should remain, and eventually become a dropdown. The search bar can be slightly smaller as well.

For the rest of the content hierarchy, I see what you are going for and agree. Start with high-level, then get to the details. This will make even more sense after removing the foundation section at the bottom, and letting the details finish out the main page.

As for sizing, the navbar is fine, but I would go bigger for the hero section. If the treatment of this section now is meant to be a kind of overlay that sits on top of a hero image, then each item just needs more space between it, making the section bigger of course.

Please feel free to contact me directly if you are interested. If you completely disagree with these comments, I would appreciate more info on the direction you are going for or would prefer. I might even be able to create a mockup.

I would for the "download" link in the menu to remain a plain button, not a dropdown. So maybe at the top of the download list page?

This is just so I don't forget about it; I'll handle it.

On the front page in text "Feel free to contact us for any inquiry regarding Haxe usage." , 'contact us' link lead to http://haxe.org/contact.html and 404 error . Maybe correct one is http://haxe.org/foundation/contact.html ?

Can replace some files off Google references, because every time you open a Web site very slow

Started a few days ago, our County has not open Google

If you have any content for the "mobile" use case page, please leave a comment here.

We are looking for:

• Testimonials / Quotes: If you have used haxe for creating mobile apps and it has been awesome, leave a short 1 sentence quote, with your name, company and URL.
• Showcase: If you have an app you would like included in the showcase, please include the name of your app, an image for the carousel, and a 1 line description.
• Popular Libraries: If there's a library that is used by a large number of Haxe app developers and we've left it out, let us know.
• Tutorials: if you have a tutorial, please supply a link, a title, and a 1 line description.

Please note we are not going to guarantee that items posted here will be included.

Once we have enough content we can close this issue.

I'd like to work on this over the weekend, but have a few questions re: strategy.

With the manual, we have a Github hook set up so any "push" event will get the site to pull down the latest markdown content, convert it to HTML, and keep a copy for any requests to /manual/*

For the site, I do not want to fully automate this, as we have a mix of content and code/design - sometimes we may want to merge a pull request but preview it before going live.

I propose:

• Having two branches, "master" and "staging".
• Any pull requests which are simple content changes go to "master"
• Any pull requests which involve changing code or stylesheets go to "staging"
• Github links "master" with the live site, so a push/merge on master will trigger an update of the live site.
• Github links "staging" with staging.haxe.org (or similar) and we can preview changes there after a push/merge to the staging branch.
• If we like what we see on staging, we merge into master.

Does this sound like an acceptable workflow?

cc @ncannasse @Simn

Having a click to open the dropdown menus for the site nav is a very clumsy interaction. Please change this to hover. And allow a click to propagate to the first item in the dropdown. Just to make sure It's not really a question of supporting touch devices either, it should be on hover for desktop, and remain on tap for devices.

Documentation -> Introduction -> Editors and IDEs is really hard to find, it should be either moved directly under Documentation or to a new section tools which could be added to the main navigation, see https://www.dartlang.org/ as an example.

It may be useful to provide links to nightly builds on the downloads page or some dedicated page.

Congrats on launching the new site!

I noticed that my name is spelled wrong in a few places. It's Jonathan, not Johnathan.

We might want to add some more emphasis on GitHub:

• on /download page (currently link to release tag only, maybe add a "Sources" section)
• on http://haxe.org/foundation/open-source.html (link to HaxeFoundation Github account)

On the home "Read more about our Paid Support Plans, help support Haxe development by donating to the Haxe Foundation"

Support and Donate are going to / instead /foundation

This part of manual is empty. Need details for every target:

1. for targets like Java via hxjava or C++ via hxcpp;
2. for targets-combos via big frameworks like Lime, (OpenFL), Snõwkit, Kha;

I copy/pasted some code examples to try.haxe.org, maybe we can create some "try it yourself"-buttons in the manual to it, so people can play around with it?

http://haxe.org/manual/lf-pattern-matching-enums.html
http://try.haxe.org/#F3bdC

http://haxe.org/manual/lf-pattern-matching-variable-capture.html

1. http://try.haxe.org/#e0769
2. http://try.haxe.org/#6cDE8

http://haxe.org/manual/lf-pattern-matching-structure.html
http://try.haxe.org/#45a59

http://haxe.org/manual/lf-pattern-matching-array.html
http://try.haxe.org/#Ad79A

http://haxe.org/manual/lf-pattern-matching-or.html
http://try.haxe.org/#C6DB8

http://haxe.org/manual/lf-pattern-matching-guards.html
http://try.haxe.org/#56dac

http://haxe.org/manual/lf-pattern-matching-tuples.html
http://try.haxe.org/#75b88

http://haxe.org/manual/lf-pattern-matching-extractors.html
1 http://try.haxe.org/#0dBb3
2 http://try.haxe.org/#cF0d6
3 http://try.haxe.org/#0A434

http://haxe.org/manual/lf-pattern-matching-introduction.html
http://try.haxe.org/#0d550 (btw does not give the error "This pattern is unused")

http://haxe.org/manual/lf-condition-compilation.html
http://try.haxe.org/#Aa2D7
http://haxe.org/manual/lf-access-control.html
example 1 http://try.haxe.org/#bc3D0
example 2 http://try.haxe.org/#c6a3c

http://haxe.org/manual/lf-metadata.html
http://try.haxe.org/#41Dc3 (does not seem to trace all values btw)

http://haxe.org/manual/lf-function-bindings.html
http://try.haxe.org/#a3D77

http://haxe.org/manual/lf-iterators.html :
example 1 http://try.haxe.org/#a658A
example 2 http://try.haxe.org/#2fAab

http://haxe.org/manual/lf-array-comprehension.html
example 1 http://try.haxe.org/#B70AD
example 2 http://try.haxe.org/#fbF84

http://haxe.org/manual/lf-string-interpolation.html :
http://try.haxe.org/#1fd11

http://haxe.org/manual/lf-static-extension-in-std.html :
http://try.haxe.org/#1fd11

http://haxe.org/manual/lf-static-extension.html :
http://try.haxe.org/#9098E

It is on the download list: http://haxe.org/download/list/

But not on the page for 3.1.3: http://haxe.org/download/version/3.1.3/

Comparison to 3.1.0: http://haxe.org/download/version/3.1.0/

If you have any content for the "web" use case page, please leave a comment here.

We are looking for:

• Testimonials / Quotes: If you have used haxe for creating a website or web-app and it has been awesome, leave a short 1 sentance quote, with your name, company and URL.
• Showcase: If you have a website you would like included in the showcase, please include the name of your game, an image for the carousel, and a 1 line description.
• Popular Libraries: If there's a library that is used by a large number of Haxe web developers and we've left it out, let us know.
• Tutorials: if you have a tutorial, please supply a link, a title, and a 1 line description.

Please note we are not going to guarantee that items posted here will be included.

Once we have enough content we can close this issue.

The ê in @waneck's name is broken on the history page:

Probably applies to other special chars too.

I trying to get the website running locally, but the build instructions seems incomplete. I'm not 100% sure where to apply your tink_core version modification and i'm also getting

src/Tasks.hx:3: characters 7-29 : Class not found : ufront.tasks.UFTaskSet

when running ufront b --debug

GitHub-flavored-markdown automatically turns URLs into clickable links, as in step 1 and 2 on this page.

On the actual site however, these are plain text.

This is not a priority, but maybe we could have tag dates on http://haxe.org/download/list/

Release Notes for 3.1.3 references http://haxe.org/file/CHANGES.txt which no longer exists. Maybe redirect /file to old.haxe.org as well ?

API docs are not up-to-date with Haxe 3.1.3 which is the latest Haxe release.

For example this page http://api.haxe.org/haxe/Json.html doesn't mention the new Json.stringify space argument.

More on that, it would be nice if API doc specified the Haxe version used to build that doc.

At the bottom of the Download page (or before release notes ?) we should mention that the latest Haxe GIT versions are available on http://build.haxe.org

A page on haxe.org listing various tweets about people who had a nice experience with Haxe, using tweeter widget. One example:
https://twitter.com/sashmackinnon/status/471411076211294208

It's like a lot of quotes in various contexts, but feel more "real"

We would like to measure the number of downloads, if possible through google analytics, I'm not sure what's the best option for this

If you have any content for the "command line apps" use case page, please leave a comment here.

We are looking for:

• Testimonials / Quotes: If you have used haxe for creating command line apps and it has been awesome, leave a short 1 sentence quote, with your name, company and URL.
• Showcase: If you have an app/tool you would like included in the showcase, please include the name of your app/tool, an image for the carousel, and a 1 line description.
• Popular Libraries: If there's a library that is used by a large number of Haxe CLI developers and we've left it out, let us know.
• Tutorials: if you have a tutorial, please supply a link, a title, and a 1 line description.

Please note we are not going to guarantee that items posted here will be included.

Once we have enough content we can close this issue.

Hi,

It would be very useful to have url that always points to the latest stable haxe binaries (a separate one for each platform), so automated scripts (e.g. chef) could get and install it.

I know that http://builds.haxe.org/ has a constant link to latest nightly build, but there is no link to latest stable one.

Thank you

To make the website come up nicely in Google, and be shareable on Facebook/Twitter you should implement at least these metatags (in the <head>)

<title>Already there</title>
<!-- Google -->
<meta name="description" content="Page description. No longer than 155 characters." />

<!-- Twitter card -->
<meta name="twitter:card" value="Page description. No longer than 155 characters.">

<!-- OpenGraph -->
<meta property="og:title" content="Title Here" />
<meta property="og:type" content="article" />
<meta property="og:url" content=" http://www.example.com/" />
<meta property="og:image" content=" http://example.com/logo.jpg" />
<meta property="og:description" content="Page description. No longer than 155 characters." /> 

Given that we loose the navigation bar, I think we should open api.haxe.org in another page/tab

https://github.com/HaxeFoundation/haxe.org/blob/master/www/website-content/pages/documentation/introduction/building-haxe.md

Many Haxe related google searches are pointing to "old.haxe.org/*" addresses. This is probably because I did a blanket redirect for most of the pages on the old site, and any SEO reputation (inbound links etc) is being applied to the redirected URL, even if better content exists on the new site.

I'm going through now and creating some specific redirects from old link addresses to new addresses, for example:

/doc/build -> http://haxe.org/documentation/introduction/building-haxe.html

I'm hoping that over the next few weeks as google trawls all the 3rd party websites and finds links to /doc/build that it will assign that reputation to the new address, rather than the old.haxe.org address.

If anyone has SEO expertise I would appreciate any input / guidance.

When importing a page (particularly from the manual) it is possible for there to be invalid HTML (or for markdown to produce invalid HTML).

Currently we parse this as XML on the server, and so when invalid (X)HTML fails to parse, we end up with a blank page.

Because we only manipulate the Xml to make cosmetic changes, a workaround could be to fall back to parsing the broken HTML direct to the browser, which will probably do a reasonable job of displaying it.

it would be great to provide the manual as a downloadable pdf. It would be nice to generate a new pdf link (with date) whenever the manual has changed.

that would be great ;)

Only on this page if you scroll down you get a big white blank
http://haxe.org/use-cases/

After a fresh import of the manual any cached pages remain cached, so the updates cannot be seen.

I'm a newcomer to Haxe and was trying to create a JSGenerator to suit my needs but I found that some API elements listed on the website are not available in the released stable version of Haxe. Namely:

• JSGenApi.hasFeature() (does not exist in 3.1.3)
• Context.defined() (does not exist in 3.1.3 but is actually Context.getDefines() in the haxe master branch)

Email I received:

Hey folks of Haxe,
i just downloaded the latest haxe windows installer but suddenly avira told me, there would be a virus in it. Crypt.Xpack.81397 to be correct.
I then went to the irc and asked some beings there and they gave me a link to older builds to check them and on every installer i picked avira said the same virus would be on.

But the binaries seems to be fine for antvir.
Probably its an antivir issue, but neverthenless people may turn off if they encounter the same issue.

bye
chris

On this page: http://api.haxe.org/haxe/io/Input.html there is a link to SocketInput, but this class does not seem to exists any longer. Link is: http://api.haxe.org/sys/net/_Socket/SocketInput.html