digitalmars.D - [WORK] [IMPORTANT] [URGENT] ddox generation
- Andrei Alexandrescu (9/9) Mar 10 2015 Hey folks, a while ago I raised the point about the bad rendering of
- Vladimir Panteleev (5/13) Mar 10 2015 This has already been fixed in git. But there is another (small)
- Andrei Alexandrescu (2/15) Mar 10 2015 Whew! Thanks, I trust you two will take this home. -- Andrei
- Vladimir Panteleev (14/29) Mar 10 2015 Details:
- Vladimir Panteleev (5/35) Mar 17 2015 4. Druntime doesn't build any more for me.
- Walter Bright (7/14) Mar 10 2015 While we're at it:
- Jacob Carlborg (6/14) Mar 11 2015 @Andrei, would some browser testing help here? It's possible to check if...
- Vladimir Panteleev (8/28) Mar 11 2015 chmgen has some linting functionality (improved in the latest
- Jacob Carlborg (5/12) Mar 11 2015 These things need to be built by the auto tester, and warnings turned
- Walter Bright (3/9) Mar 12 2015 https://issues.dlang.org/show_bug.cgi?id=14280
- Joakim (3/19) Mar 15 2015 Hmm, this happened once before, maybe it recurred?
- Martin Nowak (5/10) Mar 11 2015 We either have to update dpl-docs in lockstep with dlang.org or
- H. S. Teoh via Digitalmars-d (21/30) Mar 11 2015 IMO, we really should have a staging website that is used for reviewing
- Vladimir Panteleev (5/14) Mar 19 2015 This problem has now been resolved. The link was stale so is now
Hey folks, a while ago I raised the point about the bad rendering of ddox-generated pages, for example: http://dlang.org/library/std/algorithm/findSplit.html Google returns such links so it's important the pages look professional. Could somebody fluent with ddox get on this sooner than ASAP please? This is important and urgent, even more so than a blocker on the release because it's already out there. cc Sönke Andrei
Mar 10 2015
On Wednesday, 11 March 2015 at 05:15:08 UTC, Andrei Alexandrescu wrote:Hey folks, a while ago I raised the point about the bad rendering of ddox-generated pages, for example: http://dlang.org/library/std/algorithm/findSplit.html Google returns such links so it's important the pages look professional. Could somebody fluent with ddox get on this sooner than ASAP please? This is important and urgent, even more so than a blocker on the release because it's already out there.This has already been fixed in git. But there is another (small) regression in git, because of which I haven't updated the website yet, and I've already pinged Martin about it.
Mar 10 2015
Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> On 3/10/15 10:21 PM, Vladimir Panteleev wrote:On Wednesday, 11 March 2015 at 05:15:08 UTC, Andrei Alexandrescu wrote:Whew! Thanks, I trust you two will take this home. -- AndreiHey folks, a while ago I raised the point about the bad rendering of ddox-generated pages, for example: http://dlang.org/library/std/algorithm/findSplit.html Google returns such links so it's important the pages look professional. Could somebody fluent with ddox get on this sooner than ASAP please? This is important and urgent, even more so than a blocker on the release because it's already out there.This has already been fixed in git. But there is another (small) regression in git, because of which I haven't updated the website yet, and I've already pinged Martin about it.
Mar 10 2015
On Wednesday, 11 March 2015 at 05:21:27 UTC, Vladimir Panteleev wrote:On Wednesday, 11 March 2015 at 05:15:08 UTC, Andrei Alexandrescu wrote:Details: 1. Original problem: https://issues.dlang.org/show_bug.cgi?id=14150 https://github.com/D-Programming-Language/dlang.org/pull/901 2. A segmentation fault / infinite loop in dpl-docs: (this stalled deployment of 1. for a few weeks) https://issues.dlang.org/show_bug.cgi?id=14258 https://github.com/D-Programming-Language/dlang.org/pull/925 3. Regression with automatic expansion of the navigation menu: https://github.com/D-Programming-Language/dlang.org/pull/907#commitcomment-10120008 I was going to file a regression if I didn't hear from Martin in 24h.Hey folks, a while ago I raised the point about the bad rendering of ddox-generated pages, for example: http://dlang.org/library/std/algorithm/findSplit.html Google returns such links so it's important the pages look professional. Could somebody fluent with ddox get on this sooner than ASAP please? This is important and urgent, even more so than a blocker on the release because it's already out there.This has already been fixed in git. But there is another (small) regression in git, because of which I haven't updated the website yet, and I've already pinged Martin about it.
Mar 10 2015
On Wednesday, 11 March 2015 at 05:27:58 UTC, Vladimir Panteleev wrote:On Wednesday, 11 March 2015 at 05:21:27 UTC, Vladimir Panteleev wrote:4. Druntime doesn't build any more for me. https://issues.dlang.org/show_bug.cgi?id=14291 Will it ever end?On Wednesday, 11 March 2015 at 05:15:08 UTC, Andrei Alexandrescu wrote:Details: 1. Original problem: https://issues.dlang.org/show_bug.cgi?id=14150 https://github.com/D-Programming-Language/dlang.org/pull/901 2. A segmentation fault / infinite loop in dpl-docs: (this stalled deployment of 1. for a few weeks) https://issues.dlang.org/show_bug.cgi?id=14258 https://github.com/D-Programming-Language/dlang.org/pull/925 3. Regression with automatic expansion of the navigation menu: https://github.com/D-Programming-Language/dlang.org/pull/907#commitcomment-10120008 I was going to file a regression if I didn't hear from Martin in 24h.Hey folks, a while ago I raised the point about the bad rendering of ddox-generated pages, for example: http://dlang.org/library/std/algorithm/findSplit.html Google returns such links so it's important the pages look professional. Could somebody fluent with ddox get on this sooner than ASAP please? This is important and urgent, even more so than a blocker on the release because it's already out there.This has already been fixed in git. But there is another (small) regression in git, because of which I haven't updated the website yet, and I've already pinged Martin about it.
Mar 17 2015
On 3/10/2015 10:15 PM, Andrei Alexandrescu wrote:Hey folks, a while ago I raised the point about the bad rendering of ddox-generated pages, for example: http://dlang.org/library/std/algorithm/findSplit.html Google returns such links so it's important the pages look professional. Could somebody fluent with ddox get on this sooner than ASAP please? This is important and urgent, even more so than a blocker on the release because it's already out there.While we're at it: http://dlang.org/ Note that there are no navigation links to the "how to use dmd" pages, like: http://dlang.org/dmd-windows.html These used to be there, but have vanished at some point in the last couple months. This is embarrassingly awful.
Mar 10 2015
On 2015-03-11 06:27, Walter Bright wrote:
While we're at it:
http://dlang.org/
Note that there are no navigation links to the "how to use dmd" pages,
like:
http://dlang.org/dmd-windows.html
These used to be there, but have vanished at some point in the last
couple months.
This is embarrassingly awful.
Andrei, would some browser testing help here? It's possible to check if
some parts of the site is present and visible, i.e. a link or some text.
With links it's also possible to check if they lead to the correct page.
--
/Jacob Carlborg
Mar 11 2015
On Wednesday, 11 March 2015 at 07:22:41 UTC, Jacob Carlborg wrote:On 2015-03-11 06:27, Walter Bright wrote:chmgen has some linting functionality (improved in the latest version), it does warn about this: Warning: Page not in navigation: dmd-freebsd.html Warning: Page not in navigation: dmd-linux.html Warning: Page not in navigation: dmd-osx.html Warning: Page not in navigation: dmd-windows.html Of course, nobody actually pays attention to these warnings.While we're at it: http://dlang.org/ Note that there are no navigation links to the "how to use dmd" pages, like: http://dlang.org/dmd-windows.html These used to be there, but have vanished at some point in the last couple months. This is embarrassingly awful.Andrei, would some browser testing help here? It's possible to check if some parts of the site is present and visible, i.e. a link or some text. With links it's also possible to check if they lead to the correct page.
Mar 11 2015
On 2015-03-11 08:24, Vladimir Panteleev wrote:chmgen has some linting functionality (improved in the latest version), it does warn about this: Warning: Page not in navigation: dmd-freebsd.html Warning: Page not in navigation: dmd-linux.html Warning: Page not in navigation: dmd-osx.html Warning: Page not in navigation: dmd-windows.html Of course, nobody actually pays attention to these warnings.These things need to be built by the auto tester, and warnings turned into errors. -- /Jacob Carlborg
Mar 11 2015
On 3/10/2015 10:27 PM, Walter Bright wrote:
While we're at it:
http://dlang.org/
Note that there are no navigation links to the "how to use dmd" pages, like:
http://dlang.org/dmd-windows.html
These used to be there, but have vanished at some point in the last couple
months.
This is embarrassingly awful.
https://issues.dlang.org/show_bug.cgi?id=14280
Who wants to take this on?
Mar 12 2015
On Thursday, 12 March 2015 at 09:00:29 UTC, Walter Bright wrote:On 3/10/2015 10:27 PM, Walter Bright wrote:Hmm, this happened once before, maybe it recurred? http://forum.dlang.org/thread/m91cce$1oir$1 digitalmars.comWhile we're at it: http://dlang.org/ Note that there are no navigation links to the "how to use dmd" pages, like: http://dlang.org/dmd-windows.html These used to be there, but have vanished at some point in the last couple months. This is embarrassingly awful.https://issues.dlang.org/show_bug.cgi?id=14280 Who wants to take this on?
Mar 15 2015
On Wednesday, 11 March 2015 at 05:15:08 UTC, Andrei Alexandrescu wrote:Google returns such links so it's important the pages look professional. Could somebody fluent with ddox get on this sooner than ASAP please? This is important and urgent, even more so than a blocker on the release because it's already out there.We either have to update dpl-docs in lockstep with dlang.org or use separate stylesheets in dpl-docs that might lack behind to avoid this in future.
Mar 11 2015
On Wed, Mar 11, 2015 at 04:49:53PM +0000, Martin Nowak via Digitalmars-d wrote:On Wednesday, 11 March 2015 at 05:15:08 UTC, Andrei Alexandrescu wrote:IMO, we really should have a staging website that is used for reviewing changes, esp. large-scale changes like ddox, before we push it to the official website. This isn't the first time an embarrassing change made it to the official website before it was caught. Each time, it causes a mad scramble to get it fixed, and we end up adopting last-minute hack solutions because of the time pressure rather than engineering a proper solution from the start. (And by staging website I don't mean somebody's personal copy of dlang.org with proposed changes layered on top, I mean an actual, fully-functional deployment of dlang.org that incorporates all current PRs and polished as if it were the actual website, except that it's at a non-official address. The official dlang.org website would be rsync'd from this website at periodic intervals when we are confident that any large-scale embarrassing issues have been ironed out. The staging website would have a suitable robots.txt to prevent Google from indexing it as official material, so that the unwary don't accidentally stumble into it.) T -- Nothing in the world is more distasteful to a man than to take the path that leads to himself. -- Herman HesseGoogle returns such links so it's important the pages look professional. Could somebody fluent with ddox get on this sooner than ASAP please? This is important and urgent, even more so than a blocker on the release because it's already out there.We either have to update dpl-docs in lockstep with dlang.org or use separate stylesheets in dpl-docs that might lack behind to avoid this in future.
Mar 11 2015
On Wednesday, 11 March 2015 at 05:15:08 UTC, Andrei Alexandrescu wrote:Hey folks, a while ago I raised the point about the bad rendering of ddox-generated pages, for example: http://dlang.org/library/std/algorithm/findSplit.html Google returns such links so it's important the pages look professional. Could somebody fluent with ddox get on this sooner than ASAP please? This is important and urgent, even more so than a blocker on the release because it's already out there. cc SönkeThis problem has now been resolved. The link was stale so is now a 404, search engines should re-index and remove those pages hopefully soon.
Mar 19 2015