PR sent [1]. If nobody objects I'll merge this in a few days assuming lazy
consensus.


Justin

[1] https://github.com/apache/activemq-website/pull/151

On Tue, Feb 25, 2025 at 10:18 AM Justin Bertram <jbert...@apache.org> wrote:

> It's worth noting that the link to the HTML documentation on the download
> page [1] goes directly to the docs with no frame. Perhaps we should just
> remove the frame construct altogether and take this same approach from the
> doc landing page [2].
>
> Keep in mind that the API documentation for all the components (e.g.
> Artemis [3], Classic [4], NMS [5], & CMS [6]) has this same continuity
> issue. So maybe it's just not that big of a deal.
>
> This solution would get my vote at this point. It's simple, effective, and
> has precedent. I can work up a PR if folks are amenable.
>
>
> Justin
>
> P.S. For years JavaDoc used frames but that was dropped by default in Java
> 11 [7].
>
> [1] https://activemq.apache.org/components/artemis/download/
> [2] https://activemq.apache.org/components/artemis/documentation/
> [3]
> https://activemq.apache.org/components/artemis/documentation/javadocs/javadoc-latest/
> [4]
> https://activemq.apache.org/components/classic/documentation/maven/apidocs/index.html
> [5]
> https://activemq.apache.org/components/nms/msdoc/1.6.0/vs2005/Output/html/N_Apache_NMS.htm
> [6]
> https://activemq.apache.org/components/cms/api_docs/activemqcpp-3.9.0/html/
> [7] https://bugs.openjdk.org/browse/JDK-8202961
>
> On Tue, Feb 25, 2025 at 9:40 AM Arthur Naseef <artnas...@apache.org>
> wrote:
>
>> As someone who has written one-page-apps, I see how we have ended up with
>> (at least some) one-URL-for-all solutions.  For one-page apps, that one
>> URL
>> is OK (although even then having individual URLs is a good thing for many
>> reasons).
>>
>> But yeah, sometimes over-simplification happens.
>>
>> In this case, the pages are documentation and direct linking them is
>> valuable, especially since finding specific content can take a little
>> digging.
>>
>> Art
>>
>>
>> On Mon, Feb 24, 2025 at 8:40 PM Arjun Ray <ara...@gmail.com> wrote:
>>
>> > TOn Mon, 24 Feb 2025 14:44:42 -0700, Arthur Naseef
>> > <artnas...@apache.org> wrote:
>> >
>> > | I recently used the Artemis documents here:
>> > | https://activemq.apache.org/components/artemis/documentation
>> > |
>> > | And noticed that, upon navigating to a specific page, the broker still
>> > | shows this fixed URL.  This is problematic for sharing specific
>> content
>> > | from the site.
>> >
>> > Yet another battle in a war of long standing, that people who believe
>> > in URLs as independent locators of resouces (the original vision of
>> > the "world wide web") have been slowly losing, to those who prefer
>> > URLs not to point to resources, but as gateways to scripting gimmicks.
>> >
>> > | Can we update the site to show the URL to which the user navigated?
>> >
>> > More fancy-shmancy scripting may make this possible, but the current
>> > "design" is intended to prevent that.  The layout is based on the idea
>> > of displaying "content" within a scrolling box on _this_ page itself.
>> > That's why the location bar doesn't change: you're still on the same
>> > page.  You don't navigate elsewhere; instead stuff is fetched from
>> > elsewhere and displayed here.
>> >
>> > To see stuff at the elsewhere directly, and thus have URLs that can be
>> > shared, start here:
>> >
>> >    https://activemq.apache.org/components/artemis/documentation/docs
>> >
>> > (As inspection of the page source reveals.)
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscr...@activemq.apache.org
>> > For additional commands, e-mail: dev-h...@activemq.apache.org
>> > For further information, visit: https://activemq.apache.org/contact
>> >
>> >
>> >
>>
>

Reply via email to