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

Handle /release requests #209

Merged
merged 9 commits into from
May 20, 2017

Conversation

MartinMalinda
Copy link
Contributor

@MartinMalinda MartinMalinda commented Mar 27, 2017

should fix #185

  • get latest project version when visiting /release
  • add unit and/or acceptance test
  • make sure that links on /release also link to /release (for SEO reasons)
  • get LTS version when visiting /lts

@sivakumar-kailasam
Copy link
Member

@MartinMalinda I'm unsure how but would it be possible to research on how the /cuurent paths show up on search engine results first?

@MartinMalinda
Copy link
Contributor Author

@sivakumar-kailasam I think I read that there is a plan to have no-follow instruction for robots on all but latest project-version. I think @acorncom mentioned it.

@MartinMalinda
Copy link
Contributor Author

MartinMalinda commented Mar 27, 2017

But besides that, if the guides and external sources will mostly link to current, then it should appear on top.

Maybe we could also have 301 redirect on the latest version to the current url. (probably not a good idea)

@acorncom
Copy link
Member

I think I read that there is a plan to have no-follow instruction for robots on all but latest project-version

Yes, I think that's what we're going to need to do. We'll likely just handle that via a robots.txt file for now ...

@sivakumar-kailasam
Copy link
Member

Do bots lookup robots file in subpaths too?

@acorncom
Copy link
Member

@sivakumar-kailasam Don't believe robots.txt files are looked up anywhere but root. We'll need to handle that here as I've currently done: https://github.com/emberjs/website/blob/master/source/robots.txt

@acorncom
Copy link
Member

@MartinMalinda I imagine you're just starting to recover from EmberConf like the rest of us 😀 But thought I'd poke my head in here to see if we need to do anything else here?

Was talking to Robert Jackson and seems like it might be wiser to shift to a /release link instead of a /current link here (as current could mean either the latest release or the latest LTS release). In the long run, we may also want to have a /lts link too ... Thoughts?

@MartinMalinda
Copy link
Contributor Author

Yeah, I got excited by Glimmer and invested my "evening/weekend" time into it lately :). I'll try to finish this PR in upcoming days though. Moving from current to release is fine but I am not sure about lts. I guess jsonapi-docs would have to generate isLTS property on project-version model..?

@sivakumar-kailasam
Copy link
Member

@MartinMalinda I can see how we can add it to the model but we can probably just hardcode it in the app as a config value given that it changes only few times a year.


export default Ember.Helper.extend({

'-routing': inject.service(),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@@ -2,6 +2,7 @@

module.exports = function(environment) {
var ENV = {
ltsVersion: '2.8.3',
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we consider having short circuit to a env variable? That'd probably make it easier to restart app without having to elevate he app.

@MartinMalinda MartinMalinda changed the title [WIP] handle /current requests Handle /release requests Apr 20, 2017
@toddjordan
Copy link
Contributor

one thing I noticed is if you go to /release it gets redirected, but if you go to /release//, it keeps the release in the path. Is redirecting when just going to /release intentional?

@toddjordan
Copy link
Contributor

otherwise looks good. I'm going to merge and we can update later if need be.

@toddjordan toddjordan merged commit ffd2eb5 into ember-learn:master May 20, 2017
toddjordan added a commit to toddjordan/ember-api-docs that referenced this pull request May 24, 2017
toddjordan added a commit that referenced this pull request May 24, 2017
MartinMalinda added a commit to MartinMalinda/ember-api-docs that referenced this pull request Jun 27, 2017
MartinMalinda added a commit to MartinMalinda/ember-api-docs that referenced this pull request Jun 30, 2017
MartinMalinda added a commit to MartinMalinda/ember-api-docs that referenced this pull request Jul 1, 2017
MartinMalinda added a commit to MartinMalinda/ember-api-docs that referenced this pull request Jul 11, 2017
Gaurav0 pushed a commit to Gaurav0/ember-api-docs that referenced this pull request Sep 16, 2019
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

Successfully merging this pull request may close these issues.

Add a /current route that we can use in various places
4 participants