Workspaces and Articles
-
I just discovered the new Workspaces feature. I see that CodeProject has created a workspace for each of my articles. Is there any relationship between the workspaces and the articles they were created for? Is there a link between the two? Or are they totally separate entities?
-
I just discovered the new Workspaces feature. I see that CodeProject has created a workspace for each of my articles. Is there any relationship between the workspaces and the articles they were created for? Is there a link between the two? Or are they totally separate entities?
Article and workspace are distinct entities, and we are linking them together. Currently the links are very trivial (we create workspace for each feature, with few links between them). In nearby future we'll extend that, though. So, for example it will be possible to attach existing workspace to new article. Generally, you are invited to create workspace for each your project, private or public. With each workspace containing the project repositories and/or tasks lists (and more, in future).
-
Article and workspace are distinct entities, and we are linking them together. Currently the links are very trivial (we create workspace for each feature, with few links between them). In nearby future we'll extend that, though. So, for example it will be possible to attach existing workspace to new article. Generally, you are invited to create workspace for each your project, private or public. With each workspace containing the project repositories and/or tasks lists (and more, in future).
It would be nice if the article text could be represented within the repository somehow - maybe in a similar way that GitHub renders README files, a file in the root of the repository called 'article' could be rendered as HTML for the artcle, the method used to render it depending on its file extension (for example,
.htm/.htmlare raw HTML,.mdis Markdown, etc)?Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p CodeProject MVP for 2010 - who'd'a thunk it!
-
It would be nice if the article text could be represented within the repository somehow - maybe in a similar way that GitHub renders README files, a file in the root of the repository called 'article' could be rendered as HTML for the artcle, the method used to render it depending on its file extension (for example,
.htm/.htmlare raw HTML,.mdis Markdown, etc)?Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p CodeProject MVP for 2010 - who'd'a thunk it!
Presenting article within workspace (and slightly more) is our plan for the immediate future. With some luck this will be deployed later this week, next one at worst.
-
Presenting article within workspace (and slightly more) is our plan for the immediate future. With some luck this will be deployed later this week, next one at worst.
Ah, cool!
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p CodeProject MVP for 2010 - who'd'a thunk it!
-
Article and workspace are distinct entities, and we are linking them together. Currently the links are very trivial (we create workspace for each feature, with few links between them). In nearby future we'll extend that, though. So, for example it will be possible to attach existing workspace to new article. Generally, you are invited to create workspace for each your project, private or public. With each workspace containing the project repositories and/or tasks lists (and more, in future).
Thanks for the reply! So then, to update an article I would go through the same process as before? I was wondering if just updating the workspace (pushing an updated repo to the workspace) would allow the changes to show up in the article. i.e. are article revisions handled the same way as before or is there some integration with workspaces when revising an article?
-
Thanks for the reply! So then, to update an article I would go through the same process as before? I was wondering if just updating the workspace (pushing an updated repo to the workspace) would allow the changes to show up in the article. i.e. are article revisions handled the same way as before or is there some integration with workspaces when revising an article?
Currently the article update will be as before. You'll have the option to update it from your workspace, though, too (using similar HTML editor). Git-versioning of article text is something which we do not plan in nearby future. At least yet :)
-
Currently the article update will be as before. You'll have the option to update it from your workspace, though, too (using similar HTML editor). Git-versioning of article text is something which we do not plan in nearby future. At least yet :)
ok thanks! got it.