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

Address Milestones, Versions, and Components in a more intelligent way #41

Open
rcherny opened this issue May 22, 2013 · 3 comments
Open

Comments

@rcherny
Copy link
Contributor

rcherny commented May 22, 2013

Near, long term, and future are nice and all, but I'd almost prefer to draw a distinction between the framework, the content, and the presentation.

Food for thought.

@ghost ghost assigned rcherny May 22, 2013
@dpashkevich
Copy link

I would also think about the organization of translations in the repo right away. I mean, where would they live and how would they be versioned. I guess they whould be connected to the main project versions so that you know which version of the original doc you are viewing in translation.

@rcherny
Copy link
Contributor Author

rcherny commented Aug 11, 2013

Need to distinguish from #40

@rcherny
Copy link
Contributor Author

rcherny commented Nov 8, 2014

@dpashkevich makes an excellent observation. The translations can easily be an older version, or I could even see a disconnect / newer version thing happening (though rare).

@rcherny rcherny modified the milestone: Standards.Future Aug 25, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants