Skip to content

Notices Link in footer #609

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

Closed
wants to merge 9 commits into from
Closed

Notices Link in footer #609

wants to merge 9 commits into from

Conversation

AlixPexton
Copy link

1 new page with a brief description of recommended use of the terms and
logos plus a link to it is the site navigation.

1 new page with a brief description of recommended use of the terms and
logos plus a link to it is the site navigation.
($H3 Naming)
($P
"D Programming Language" is the full name of the language, this can be
shortened to "DLang" when brevity is required. The use of an uppercase L is
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This doesn't reflect current usage, where "D" is the name of the language, which (quite rarely) is rendered as "DLang"/"dlang"/… for clarity in ambiguous contexts. See e.g. http://dlang.org or http://dconf.org/2014/schedule/index.html for real-world examples.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This isn't necessarily about establishing what current usage is, rather than stating what it should be when talking about D in formal contexts.

Reworded the opening paragraph to better reflect current of names for D.

Added the original SVG graphic to the repo and updated the link.
@sigod
Copy link

sigod commented Jul 7, 2014

Why formatting of SVG so different from original one?

Also, don't forget to change links.

@AlixPexton
Copy link
Author

@sigod I'm trying to convey that the logo is not that image and that image is not the logo. The image incorporates the logo into a shiny button. The description is of the logo without the "button chrome" around it. The logo for D will not be changing in the foreseeable future, this drive is towards seeing it used in more ways and forms than just a single image that is 8 years old.

And yes the updated PR changed the link.

@ghost
Copy link

ghost commented Jul 7, 2014

And what authority do you have to say the logo won't change? This page is as interesting as an EULA popup.

@AlixPexton
Copy link
Author

@AndrejMitrovic No authority, just passing the sentiment along. Walter does not want the LOGO to change (his foot seems pretty close to the floor on the issue), that is not the same as saying that the IMAGE that is used to brand the website and other things D will never change. This is not the start of an attempt to rebrand D nor to freeze its current branding forever. I hoped only to clarify what elements of the current brand identity should be kept and used as inspiration for material that is used to promote D in the future.

Until the debate over which parts of the image are essential to the logo has been fully settled, and the copyright issues hopefully resolved, I'm fine with this page should remaining a EULAesque place holder.

I want to move forward with creating material that promotes D with a common face, but designing something wholly new is not an option. In order to progress, what can and cannot be changed need to be established, and I hoped that what I had described was acceptable, based on the recent newsgroup discussion.

Re-reading the newsgroup, the idea of a d logo with reversed colours
seems less resolved than I recalled, so I have culled the offending
paragraph pending further discussion.
@ghost
Copy link

ghost commented Jul 8, 2014

his foot seems pretty close to the floor on the issue

Walter has changed his opinion plenty of times. If we had a better looking logo and people liked it (e.g. positive feedback on reddit / HN / etc) he'd change his mind pretty quickly. That's just how things work around here.

But why do you have to talk like a damn lawyer? It really pisses me off.

@AlixPexton
Copy link
Author

I don't mean to come across like a lawyer, but how would you prefer someone, who wants to put effort into giving D a more professional front, to communicate?

I was one of the designers who shared new logo designs, the most I can say of the feedback is that it was mixed, but the most important part was that Walter felt it was a lot of effort that could be better used elsewhere. So, as I still want to contribute to D, this is what I'm offering to do.

At the end of the day, it doesn't matter if the logo changes or not, dlang.org will still need a page about branding, stating what the D related logos and trademarks are and how they can be used. I hope you can see that I am only trying to contribute something that is valuable to the future of D.

If I had not been using D since the very first compiler release (and following it with interest even before that) I might be frightened off by this hostility, but I want to see D succeed!

Added para about SafeD. More about Phobos/Deimos. More precise colors.
Clearer logo usage guidlines. USian spelling :(
The debugger.html file isn't finding its way to the server, but its just
a shim that redirects to the wiki, so why not link directly?
This reverts commit 7b9e2d4.
@@ -199,6 +199,7 @@ $(NAVBLOCK_HEADER $(TOCHEADER Documentation),

$(TOCENTRYTH howtos.html, Helps for using D, How-tos, $(CATEGORY_HOWTOS $(SUBNAV_HOWTOS)))
$(TOCENTRYH articles.html, Articles, $(CATEGORY_ARTICLES $(SUBNAV_ARTICLES)))
$(TOCENTRYH branding.html, Branding, $(CATEGORY_BRANDING $(SUBNAV_BRANDING)))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this really belongs in the top level, left side navigation. It seems more appropriate to have in the footer.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe that it is important enough to be in the sidebar, considering how redundant the links currently in the footer are.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMHO it doesn't belong in the sidebar or footer at all. I think making the page easily discoverable would send the wrong message, that D is too concerned with issues such as branding than actual quality of the language or implementation.

What other programming languages advertise a page like this on their home pages?

I suppose it could be useful to have some agreed-upon conventions written down, but they are more useful to people within the community, people working on projects related to the language itself. For such cases, we can post a link to the page in the discussion whenever the situation arises.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Python.org has a "python logo" link in the footer of their landing page (which is actually a site map). So that's one. Its a different because they are in a better position legally speaking, with their branding.

You make it sound like you think the dlang.org is something put together for outsiders and all the community activity goes on elsewhere. I think dlang.org should face both ways, and so it is the perfect place for a document like this.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I also think we shouldn't insert a link to "branding" in a very visible place.

@CyberShadow
Copy link
Member

Python.org has a "python logo" link in the footer of their landing page (which is actually a site map). So that's one. Its a different because they are in a better position legally speaking, with their branding.

Not quite the same thing. The link is in a footer among dozens of other links, not as visible as dlang.org's sidebar. The page also describes the logos - the policy for using them is a second link off that page.

There also doesn't appear to be consensus on whether this page actually accurately describes consensus. The only "branding"-related advice I know that actually comes from Walter and has consensus is to add "Written in the D Programming Language" at the top of .d files.

I think this pull should only be merged with Walter / Andrei's OK. An alternative would be to just place the page on the wiki.

Turns out the spell check in my code editor broke when I set it to USian
English >< Thanks to CyberShadow for pointing out the obvious ones!
@AlixPexton
Copy link
Author

@CyberShadow There isn't enough to say at this time to justify 2 pages. Python doesn't have as much to explain about its name(s) either. Even if D were in the same position as Python branding wise, it wouldn't be appropriate to copy their page.
If/when the issues with the copyright of the logo are resolved and there are more promotional images to share, then the legal stuff will get more boring and can be moved to a sub section of the terms and conditions (which also still needs to be written).

Putting "Written in the D Programming Language" at the top of each source file is a good start, but when people come to look for information about D, most are not going to start with source files, they are going to look at web pages. There are a lot of other Ds out there, I'm surprised that there aren't more false positives. I doubt there are (m)any people that think D2 is out of date because they found D4 and started learning about that instead, but that doesn't mean there isn't confusion.

Putting it on the wiki would mean that anyone could come along and change it without it being reviewed, That is not a good idea.

shortened to "DLang" when brevity is required. (The use of an upper case L is
recommended to avoid confusion with symbols that resemble a lower case l.
The use of all lower case for the abbreviated form should be restricted to
web addresses such as in links to ($LINK dlang.org).)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That should be $(LINK dlang.org).

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, shame its not the only ddoc tag I screwed up ><

fixed

@andralex
Copy link
Member

I'm not sure what to make of this. It's a bit sudden compared to the rest of the site, and deals with matters I know next to nothing about. Leaving it to others, with the mention that I think it would be overkill to link this prominently from the home page.

not. embarrassing. at. all.
@AlixPexton
Copy link
Author

@andralex I'm not 100% sure what you mean by sudden in this context. I'm guessing overly terse or formal, which was not a concious decision but I do feel the tone is appropriate to the content.

Moved link from sidebar to footer. Changed the page's title to Notices
with a top level heading for Branding so other notices can be added in
the future.
@AlixPexton
Copy link
Author

I'm reluctantly conceding that the sidebar is the wrong place for this, so I've made two changes. I moved the link to the footer and I relabelled the page as "Notices".
dlang.org should have proper pages for Terms&Conditions/Policies, and I see the heading "Notices" as a suitable umbrella for both these and branding. When there are more notices they can have a page each, and the notices page can index them.
I think it would be better to publish this first notice by itself than to delay further by waiting for more notices to be composed.

@AlixPexton AlixPexton changed the title Added a page on Branding Notices Link in footer Jul 26, 2014
@andralex
Copy link
Member

andralex commented Jan 9, 2015

I'll close this for now. Please reopen if warranted.

@andralex andralex closed this Jan 9, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants