in
> progress patch. You might want to get in touch with him to finish it.
> Best regards,
> Ekaterina
>
> On Wed, 25 Oct 2023 at 8:04, Claude Warren, Jr via dev
> mailto:dev@cassandra.apache.org>> wrote:
>> I just had to change dependencies in Cassandra for the fir
to change dependencies in Cassandra for the first time and I
> think the documentation [1] is out of date.
>
> First I think most of the file edits are in the ".build" directory.
> Adding jars to the "lib" directory works until calling "ant realclean&
I just had to change dependencies in Cassandra for the first time and I
think the documentation [1] is out of date.
First I think most of the file edits are in the ".build" directory. Adding
jars to the "lib" directory works until calling "ant realclean", so p
As Open Collective may have back-shelved your application, you may need to
remind them that you need an account by a certain date.
On Monday, February 13, 2023 at 05:23:53 p.m. EST, Lorina Poland
wrote:
Hi all -
I have submitted an application to the Open Collective, so that we woul
Great news, indeed! Thanks for driving this, Lorina!
On Thu, 16 Feb 2023 at 19:32, C. Scott Andreas wrote:
> Thanks and congratulations Lorina!
>
> — Scott
>
> > On Feb 16, 2023, at 4:29 PM, Lorina Poland wrote:
> >
> > Good news! The Open Collective application was accepted! Step one is
> don
Thanks and congratulations Lorina!
— Scott
> On Feb 16, 2023, at 4:29 PM, Lorina Poland wrote:
>
> Good news! The Open Collective application was accepted! Step one is done.
>
> Lorina
>
>> On 2023/02/13 22:23:35 Lorina Poland wrote:
>> Hi all -
>>
>> I have submitted an application to the
Good news! The Open Collective application was accepted! Step one is done.
Lorina
On 2023/02/13 22:23:35 Lorina Poland wrote:
> Hi all -
>
> I have submitted an application to the Open Collective, so that we would
> have a funding mechanism to pay 1-2 technical writers if we are successful
> wit
Hi all -
I have submitted an application to the Open Collective, so that we would
have a funding mechanism to pay 1-2 technical writers if we are successful
with our GSoD proposal.
I have the GSoD proposal ready, and am only waiting for the first date for
submission, Feb 15, 2023. Here is a link
een thinking about a
> more standardized organization to docs, to make it simpler for users to
> find what they are looking for, separate from searching. [That's the kind
> of thing docs nerds think about.] To that end, I've created a unified
> information architecture (IA) that ca
I second Benedict, thanks Lorina
On Thu, 2 Feb 2023 at 7:54, Benedict wrote:
> This looks good to me, thanks Lorina
>
> On 1 Feb 2023, at 19:24, Lorina Poland wrote:
>
>
>
> Hey all -
>
> I presented a potential Docs Information Architecture recently, and
> promised a Doc Plan for the upcomin
This looks good to me, thanks Lorina
> On 1 Feb 2023, at 19:24, Lorina Poland wrote:
>
>
> Hey all -
>
> I presented a potential Docs Information Architecture recently, and promised
> a Doc Plan for the upcoming C* 5.0 release. Please give me feedback,
> especially if you feel that the prio
about a
>> > more standardized organization to docs, to make it simpler for users to
>> > find what they are looking for, separate from searching. [That's the
>> kind
>> > of thing docs nerds think about.] To that end, I've created a unified
>> > informa
ardized organization to docs, to make it simpler for
users to
> find what they are looking for, separate from searching. [That's
the kind
> of thing docs nerds think about.] To that end, I've created a
unified
> information architecture (IA) that can apply to
from searching. [That's the kind
> > of thing docs nerds think about.] To that end, I've created a unified
> > information architecture (IA) that can apply to any kind of
> documentation,
> > including the Apache C* docs.
> >
> > Up front, I'll say, n
Hey all -
I presented a potential Docs Information Architecture recently, and
promised a Doc Plan for the upcoming C* 5.0 release. Please give me
feedback, especially if you feel that the priorities for upcoming features
should be different than what I propose. Also understand that the priority
is
#x27;ve been thinking about a
> more standardized organization to docs, to make it simpler for users to
> find what they are looking for, separate from searching. [That's the kind
> of thing docs nerds think about.] To that end, I've created a unified
> information architecture
nd CEP-15, it became apparent that we lack any guidance on internal documentation and commenting in the “style guide” - which I also propose we rename to “Contribution Guide” or “Contribution and Style Guide" to better describe the broader role it has taken on.I have put together a starting
Thank you Benedict! Can you, please, give us comment access to the doc?
On Mon, 30 Jan 2023 at 6:14, Benedict wrote:
> During public and private discussions around CEP-15, it became apparent
> that we lack any guidance on internal documentation and commenting in the
> “style guide”
During public and private discussions around CEP-15, it became apparent that we
lack any guidance on internal documentation and commenting in the “style guide”
- which I also propose we rename to “Contribution Guide” or “Contribution and
Style Guide" to better describe the broader role i
g. [That's the kind
of thing docs nerds think about.] To that end, I've created a unified
information architecture (IA) that can apply to any kind of documentation,
including the Apache C* docs.
Up front, I'll say, not every section of this organization applies to
Apache C* docs, but
Thanks
Sharan
On 2022/10/20 07:56:57 Sharan Foga wrote:
> Hi Josh
>
> Excellent and thanks for this. I'll take a look.
>
> Thanks
> Sharan
>
> On 2022/10/18 20:35:50 Josh McKenzie wrote:
> > Hey Sharan! Documentation is near and dear to my heart; the longer I sp
Hi Ekaterina
Thanks for the suggestion! Looks like documentation is a hot topic so great
there are a few opportunities to get involved. :-)
Thanks
Sharan
On 2022/10/19 15:06:23 Ekaterina Dimitrova wrote:
> One more idea, I was looking to update the What’s new page - a few links to
> d
this hasn't been documented yet afaik.
>
> There's a preliminary documentation patch available on
> https://issues.apache.org/jira/browse/CASSANDRA-16887 if you want to take a
> stab at it.
>
> Em ter., 18 de out. de 2022 às 16:36, Josh McKenzie
> escreveu:
>
&
Hi Josh
Excellent and thanks for this. I'll take a look.
Thanks
Sharan
On 2022/10/18 20:35:50 Josh McKenzie wrote:
> Hey Sharan! Documentation is near and dear to my heart; the longer I spend on
> this project the more I think it's one of the higher leverage things we can
>
; There's a preliminary documentation patch available on
> https://issues.apache.org/jira/browse/CASSANDRA-16887 if you want to take
> a stab at it.
>
> Em ter., 18 de out. de 2022 às 16:36, Josh McKenzie
> escreveu:
>
>> Hey Sharan! Documentation is near and dear to my hea
Welcome Sharan! :)
One of the features that is going to be released in 4.1 is the ability to
add TTL to snapshots, but this hasn't been documented yet afaik.
There's a preliminary documentation patch available on
https://issues.apache.org/jira/browse/CASSANDRA-16887 if you want to take
Hey Sharan! Documentation is near and dear to my heart; the longer I spend on
this project the more I think it's one of the higher leverage things we can
invest our energy into. A general high level view of open documentation work in
the project in reverse key order can be found here:
e docs
so please can someone point me in the direction of something that needs
doing around documentation :-)
Thanks
Sharan
Hi,
I am currently working on designing a bot to support open-source software
development: the idea is that the bot can analyze code review comments, detect
those related to explaining the reasons behind the implementation choices and
suggest these reasons as source code comments. As the first
t other committers on
the project for merging docs in. A couple folks on the pmc floated the idea
of nominating the full time technical writers to committer so they could
work in tight cycles on the documentation. We could also pair them with
mentors to get through this merge and learn a bit mor
em.
>
> There's a nice project that builds on top of asciidoctor called Antora [1]
> that's specifically built to create documentation websites like ours that
> might be a good fit for our needs, but we need to evaluate it with a POC to
> know for sure.
>
> [1] http
ld be improving what we have for
4.0. Once that's released we can mess with the doc & website system.
There's a nice project that builds on top of asciidoctor called Antora [1]
that's specifically built to create documentation websites like ours that
might be a good fit for our
lly not hierarchical.
> From
> >> a user's point of view not finding information is frustrating, incorrect
> >> information is frustrating, and incomplete information is frustrating.
> >> Individual user's reaction to these frustrations will vary from taking
> it
> &
not finding information is frustrating, incorrect
>> information is frustrating, and incomplete information is frustrating.
>> Individual user's reaction to these frustrations will vary from taking it
>> in stride to abandoning a product.
>>
>> Wrong in documentat
x27;s point of view not finding information is frustrating, incorrect
> information is frustrating, and incomplete information is frustrating.
> Individual user's reaction to these frustrations will vary from taking it
> in stride to abandoning a product.
>
> Wrong in document
idual user's
reaction to these frustrations will vary from taking it in stride to abandoning
a product.
Wrong in documentation isn't analogous to incorrect code. Incorrect code breaks
something, but there are levels of wrong in docs that can still provide enough
information for user
>
> usability and ease of consumption is just as important if not more as
> correctness and coverage.
I disagree pretty strongly with this. There is negative value in
documentation that's incorrect and inaccurate. Much like comments or code:
if it's wrong, I posit that n
something you want to do without knowing what it is beforehand. Searchability
is finding information you know about using
the terms that you know. The key to effective documentation is that
information is both findable and searchable in "terms that the users know". A
simple example is
I've been mulling over this topic the past few days as we often seem to get
mired in debates over technical details of offerings without a clear value
system to weigh them against one another. In the case of documentation, I'd
propose that we think about this from the perspective of th
ent was to
> > demonstrate that my opinion is based on experience and I wasn't
> suggesting
> > we switch tooling based on a whim. I also wasn't trying to imply you
> > aren't knowledgeable about writing documentation.
> >
> > Apart from this misunder
ed on experience and I wasn't suggesting
we switch tooling based on a whim. I also wasn't trying to imply you
aren't knowledgeable about writing documentation.
Apart from this misunderstanding, I think we mostly agree. I'm not looking
to perform a migration that removes funct
Apologies, I didn't mean to upset or insult you. My intent was to
demonstrate that my opinion is based on experience and I wasn't suggesting
we switch tooling based on a whim. I also wasn't trying to imply you
aren't knowledgeable about writing documentation.
Apart from this
op. I do agree on the point on documentation though,
the asciidoc one is better (not that I find the rst one completely
inadequate
either), and I reckon it's a good argument.
So to be clear, if someone makes the change to asciidoc and it's not
botched, I
won't personally stand
Haddad wrote:
>
> I've got a bit of experience here using all three systems we're discussing
> here.
>
> * rst & sphinx: I've handled most of the doc reviews for Cassandra, written
> quite a bit of them as well, and I authored most of the documentation for
&
I've got a bit of experience here using all three systems we're discussing
here.
* rst & sphinx: I've handled most of the doc reviews for Cassandra, written
quite a bit of them as well, and I authored most of the documentation for
cqlengine [1]
* markdown: all over the pla
airly
large (and meant to grow) user facing documentation of a large and somewhat
complex software, and a bit more flexibility is of definite use imo. I truly
worry Markdown will effectively yield a lesser experience for user of the
doc.
By how much, I'm not sure, but insofar that the documentati
it. The syntax is crap and
> almost nobody knows it.
>
> I'm fine with markdown (it makes it easy for most people) and have a
> personal preference for asciidoc, since it makes it easier to generate PDFs
> and is a bit richer / better for documentation. I'd go with markdown
tooling would ease adoption of donation + prevent re-work,
> that'd be an obvious benefit to deciding on that prior.
>
> On Fri, Apr 24, 2020 at 4:19 PM Sylvain Lebresne
> wrote:
>
> > > Are there any questions or concerns about this donation?
> >
> > Gett
ri, Apr 24, 2020 at 4:19 PM Sylvain Lebresne wrote:
> > Are there any questions or concerns about this donation?
>
> Getting substantial contributions to the documentation is a great thing to
> me
> in principle.
>
> My main question was around the exact form this donation wo
> Are there any questions or concerns about this donation?
Getting substantial contributions to the documentation is a great thing to
me
in principle.
My main question was around the exact form this donation would take since
the
project has already lots of documentation. And I was about
; > could be some duplication.
>
> Absolutely. I was unclear in my original email: this is offered as a
> contribution in whatever form best works for the project, and there's
> plenty of exceptionally good documentation and work that's already been
> done in-tree. Th
>
> could be some duplication.
Absolutely. I was unclear in my original email: this is offered as a
contribution in whatever form best works for the project, and there's
plenty of exceptionally good documentation and work that's already been
done in-tree. The path forward would
Joshua,
That sounds good. But could be some duplication.
regards,Deepak
On Friday, April 24, 2020, 04:17:07 p.m. UTC, Joshua McKenzie
wrote:
To clarify intent Deepak, we're only talking about donating the Apache
Cassandra portion of the documentation, nothing else. There
like to contribute here.
> Please let me know.
>
> Manish
>
> On Fri, Apr 24, 2020 at 9:03 PM Deepak Vohra
> wrote:
> >
> >
> > While the DataStax documentation could supplement the Apache Cassandra
> documentation, DataStax is a commercial product based on o
I would like to contribute here.
Please let me know.
Manish
On Fri, Apr 24, 2020 at 9:03 PM Deepak Vohra wrote:
>
>
> While the DataStax documentation could supplement the Apache Cassandra
> documentation, DataStax is a commercial product based on open source Apache
>
To clarify intent Deepak, we're only talking about donating the Apache
Cassandra portion of the documentation, nothing else. There is no
intention whatsoever for anything DataStax branded or related to merge into
the in-tree project documentation.
On Fri, Apr 24, 2020 at 11:33 AM Deepak
While the DataStax documentation could supplement the Apache Cassandra
documentation, DataStax is a commercial product based on open source Apache
Cassandra with enhancements made to the open source Cassandra. Moreover,
DataStax documentation requires to be maintained and updated and as it
I'd like to get the docs out of Sphinx. I hate it. The syntax is crap and
almost nobody knows it.
I'm fine with markdown (it makes it easy for most people) and have a
personal preference for asciidoc, since it makes it easier to generate PDFs
and is a bit richer / better for documenta
All,
A few of us have the opportunity to offer a large portion of documentation
to the apache foundation and specifically the Apache Cassandra project as
well as dedicate a good portion of time to maintaining this going forward.
For those of you familiar, this is the DataStax sponsored / authored
My strongest apologies, this was not intended for the dev list.
There goes my habit of clearing the `to:` field to prevent accidental
sending of drafts :-(
-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additi
> I'd like to add one thing - we should probably start off with a [DISCUSS]
> thread before starting a [VOTE] to avoid noise in the voting (and make
> counting votes easier)
Having either a DISCUSS thread or an initial Consensus Approval vote,
are both ways to push for consensus. The approach to
Thanks, everyone and especially Mick for seeing this through!
Dinesh
> On Nov 6, 2019, at 8:58 AM, Mick Semb Wever wrote:
>
>
>
> On Fri, 1 Nov 2019, at 13:32, Mick Semb Wever wrote:
>> Please vote on accepting the Cassandra Enhancement Proposal (CEP)
>> document as a starting point and guid
On Fri, 1 Nov 2019, at 13:32, Mick Semb Wever wrote:
> Please vote on accepting the Cassandra Enhancement Proposal (CEP)
> document as a starting point and guide towards improving collaboration
> on, and success of, new features and significant improvements.
Thanks everyone, especially Scott
; and put them on Confluence. The outline and notes cover all of the
> > > presentation's content in detail so the delta between "being there" and
> > > "reading the notes" should be minimal.
> > > >
> > > > ___
s. I'll clean these up
> > and put them on Confluence. The outline and notes cover all of the
> > presentation's content in detail so the delta between "being there" and
> > "reading the notes" should be minimal.
> > >
> > > ___
ould be minimal.
> >
> >
> > From: Michael Shuler on behalf of Michael
> Shuler
> > Sent: Friday, November 1, 2019 9:09 AM
> > To: dev@cassandra.apache.org
> > Subject: Re: [VOTE] Cassandra Enhancement Proposal (CEP) docum
, 2019 9:09 AM
> To: dev@cassandra.apache.org
> Subject: Re: [VOTE] Cassandra Enhancement Proposal (CEP) documentation
>
> +1
>
> Scott, was your NGCC talk videoed and uploaded anywhere? I would love to
> watch, since I missed the event.
>
> Kind regards,
> Michael
>
s improving collaboration on, and
> > success of, new features and significant improvements. In combination
> with
> > the recently accepted Cassandra Release Lifecycle documentation this
> should
> > help us moving forward as a project and community.
> >
> >
> h
ith
> the recently accepted Cassandra Release Lifecycle documentation this should
> help us moving forward as a project and community.
>
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95652201
>
> Past discussions on the document/process have been touched on
ombination with the
> recently accepted Cassandra Release Lifecycle documentation this should help
> us moving forward as a project and community.
>
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95652201
>
> Past discussions on the document/process ha
09 AM
> To: dev@cassandra.apache.org
> Subject: Re: [VOTE] Cassandra Enhancement Proposal (CEP) documentation
>
> +1
>
> Scott, was your NGCC talk videoed and uploaded anywhere? I would love to
> watch, since I missed the event.
>
> Kind regards,
> Michael
>
> On 1
ading the notes"
should be minimal.
From: Michael Shuler on behalf of Michael Shuler
Sent: Friday, November 1, 2019 9:09 AM
To: dev@cassandra.apache.org
Subject: Re: [VOTE] Cassandra Enhancement Proposal (CEP) documentation
+1
Scott, was your NGCC talk videoed and
Wever" wrote:
Please vote on accepting the Cassandra Enhancement Proposal (CEP) document
as a starting point and guide towards improving collaboration on, and success
of, new features and significant improvements. In combination with the recently
accepted Cassandra Release Lifecycle document
n accepting the Cassandra Enhancement Proposal (CEP) document
>> as a starting point and guide towards improving collaboration on, and
>> success of, new features and significant improvements. In combination with
>> the recently accepted Cassandra Release Lifecycle documen
proving collaboration on, and success
> of, new features and significant improvements. In combination with the
> recently accepted Cassandra Release Lifecycle documentation this should help
> us moving forward as a project and community.
>
>https://cwiki.apache.org/confluence
e recently
accepted Cassandra Release Lifecycle documentation this should help us moving
forward as a project and community.
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95652201
Past discussions on the document/process have been touched on in a number
of threads
Please vote on accepting the Cassandra Enhancement Proposal (CEP) document as a
starting point and guide towards improving collaboration on, and success of,
new features and significant improvements. In combination with the recently
accepted Cassandra Release Lifecycle documentation this should
Hello,
I am new to the community and interested in helping with documentation update
for Cassandra 4.0 release.
I am writing to ask about the parts of the current documentation that needs to
be updated to reflect the changes and improvement made in Cassandra v4.0 before
release.
I hope to
Hello all,
I am new to the Cassandra community and would like to help with updating the
current documentation to reflect the changes and improvements made.
I would like to use this opportunity to reach out to the community of
developers to kindly highlight the necessary changes that have to
I've been trying to withdraw from the conversation since Friday.
-Original Message-
From: Josh McKenzie [mailto:jmcken...@apache.org]
Sent: Monday, March 19, 2018 9:56 AM
To: dev@cassandra.apache.org
Subject: Re: A JIRA proposing a seperate repository for the online documentation
A
>> Rahul Singh has been making a very important point that different types of
>> uses with different uses cases use the website. This is a public website;
>> not an internal site for coders.
>>
>> Kenneth Brotman
>>
>> -Original Message-
>> From: J
ith different uses cases use the website. This is a public website;
> not an internal site for coders.
>
> Kenneth Brotman
>
> -Original Message-
> From: Josh McKenzie [mailto:jmcken...@apache.org]
> Sent: Monday, March 19, 2018 7:42 AM
> To: dev@cassandra.apache.org
>
otman
-Original Message-
From: Josh McKenzie [mailto:jmcken...@apache.org]
Sent: Monday, March 19, 2018 7:42 AM
To: dev@cassandra.apache.org
Subject: Re: A JIRA proposing a seperate repository for the online documentation
Wow. Ok, let's try this again.
Josh, you made my point for me.
ken...@apache.org]
> Sent: Monday, March 19, 2018 5:27 AM
> To: dev@cassandra.apache.org
> Subject: Re: A JIRA proposing a seperate repository for the online
> documentation
>
> >
> > I've been writing html a long time; since about 1990. You're asking
>
: Josh McKenzie [mailto:jmcken...@apache.org]
Sent: Monday, March 19, 2018 5:27 AM
To: dev@cassandra.apache.org
Subject: Re: A JIRA proposing a seperate repository for the online documentation
>
> I've been writing html a long time; since about 1990. You're asking
> me to learn a w
>
> I've been writing html a long time; since about 1990. You're asking me to
> learn a weird little program, a static site generator just to change
> something I can already do without using a program at all.
You're one person among a community of back-end Java devs. If you want
people to contri
On Mon, Mar 19, 2018 at 12:41 AM, Kenneth Brotman
wrote:
> I don't know what we are doing for the website technologies right now because
> like everything else what we do is not documented anywhere. Where are the
> servers: the cloud? What server software are we running? How is the html,
> e
ve us well for now.
Kenneth Brotman
-Original Message-
From: Kenneth Brotman [mailto:kenbrot...@yahoo.com.INVALID]
Sent: Sunday, March 18, 2018 4:41 AM
To: dev@cassandra.apache.org
Subject: RE: A JIRA proposing a seperate repository for the online documentation
I don't know what we ar
bsite?
Kenneth Brotman
-Original Message-
From: Rahul Singh [mailto:rahul.xavier.si...@gmail.com]
Sent: Saturday, March 17, 2018 7:12 AM
To: dev@cassandra.apache.org
Subject: RE: A JIRA proposing a seperate repository for the online documentation
Static site generator just takes content
> Kenneth Brotman
>
>
> -Original Message-
> From: Rahul Singh [mailto:rahul.xavier.si...@gmail.com]
> Sent: Saturday, March 17, 2018 5:57 AM
> To: dev@cassandra.apache.org
> Subject: RE: A JIRA proposing a seperate repository for the online
> documentation
&g
bsite that is dynamic and multi-media
rich?
Kenneth Brotman
-Original Message-
From: Rahul Singh [mailto:rahul.xavier.si...@gmail.com]
Sent: Saturday, March 17, 2018 5:57 AM
To: dev@cassandra.apache.org
Subject: RE: A JIRA proposing a seperate repository for the online documentation
I
form. On the other hand. I [insert f-bomb] hate writing HTML / CSS, or
restructured text. Markdown is much easier. Hugo is one of many that if setup
right, it can save a ton of time and make it more accessible for people to
contribute.
There is a difference however in developer documentation for
.
-Original Message-
From: beggles...@apple.com [mailto:beggles...@apple.com]
Sent: Friday, March 16, 2018 3:16 PM
To: dev@cassandra.apache.org
Subject: Re: A JIRA proposing a seperate repository for the online documentation
It would probably be more productive to list some specific concerns you have
or me to do so. Let's see what we
decide to do going forward for the website.
Kenneth Brotman
(Cassandra coder?)
-Original Message-
From: Eric Evans [mailto:john.eric.ev...@gmail.com]
Sent: Friday, March 16, 2018 7:59 AM
To: dev@cassandra.apache.org
ible for me to do so. Let's see what we decide to
do going forward for the website.
Kenneth Brotman
(Cassandra coder?)
-Original Message-
From: Eric Evans [mailto:john.eric.ev...@gmail.com]
Sent: Friday, March 16, 2018 7:59 AM
To: dev@cassandra.apache.org
Subject: Re: A JIRA prop
t: Thursday, March 15, 2018 9:24 AM
> To: dev@cassandra.apache.org
> Subject: Re: A JIRA proposing a seperate repository for the online
> documentation
>
> Murukesh is correct on a very useable, pretty standard process of
> multi-versioned docs.
>
> I’ll put my thought
vote?
Kenneth Brotman
-Original Message-
From: Jon Haddad [mailto:jonathan.had...@gmail.com] On Behalf Of Jon Haddad
Sent: Thursday, March 15, 2018 9:24 AM
To: dev@cassandra.apache.org
Subject: Re: A JIRA proposing a seperate repository for the online documentation
Murukesh is correct on a
t;> one version done several different ways by now.
>>
>> A website with several versions of documentation is going to have
>> sub-directories for each version of documentation obviously. I've offered
>> to create those sub-directories under the "doc"
On Fri, Mar 16, 2018 at 0:19 Kenneth Brotman
wrote:
> Help me out here. I could have had a website with support for more than
> one version done several different ways by now.
>
> A website with several versions of documentation is going to have
> sub-directories for
Help me out here. I could have had a website with support for more than one
version done several different ways by now.
A website with several versions of documentation is going to have
sub-directories for each version of documentation obviously. I've offered to
create thos
1 - 100 of 136 matches
Mail list logo
