Code Monkey home page Code Monkey logo

website's People

Contributors

abeaumont avatar andreasdotorg avatar baragent avatar cgay avatar fracek avatar fraya avatar hannesm avatar housel avatar micrypt avatar pedro-w avatar promovicz avatar robdaemon avatar timclicks avatar waywardmonkeys avatar wvdschel avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

website's Issues

Add top-level "Contribute" page

Add a top level page that discusses how to contribute to the project.

It should link to the Github issue tracker for filing a new bug. It should also link to the Github issue tracker search results for "Easy" and all bugs.

About: History page

Let's create a history page that goes over the history of Dylan and Open Dylan. Would also be nice to include some of the old screenshots of stuff from the Apple Dylan days.

Footer on big monitors (or short pages)

Cgay reported this a couple of weeks ago, on big monitors the footer was in the middle of the page. If you have a small monitor you can see what I mean on the about page.

Abeaumont (IIRC) linked to this page, where they use a sticky footer with boostrap and a fixed navbar.

To achieve that result we need to wrap the navbar and container in a wrap div and add a bit of css.

To do this we can:

  1. define a new theme and layout by modifying the basic theme
  2. change the current layout, open the wrap in the header block and close it in the footer block.

I implemented option 2 in a feature branch in my fork (commit) but I don't know if putting the open/close tags in two different blocks will cause any problem in the future.

Website revamp checklist

I need a place to put a checklist of things I want to do before I consider my current "revamp" of the website to be complete. This is that place.

  • Redo the front page in the style described by Jost Grant. Quoth he...
    • Also, think frontpage ideally would be more of a 'pitch' of what OD is, links to various social media places (github org, here, etc), and like download link / setup instructions, etc
    • I think there's a tendency in / on technically aimed sites to to try to introduce people into concepts and/or documentation asap -- but really, what you're doing is trying to retain attention and interest first and foremost.
    • I think when you're looking into a new language (I know this from my own experience when I was younger), there's a lot of social aspects to the presentation that can easily just put it into 'disqualifying' territory because people are fickle and expect "enough familiarity" that it's not so scary or 'hard' feeling and/or the tagline / ethos wasn't pervasive enough. There's obviously a LOT more than that, but even little things like that really do matter. Namely, because there's so much competition out there with a LOT more word-of-mouth / social capital to play with
  • Adjust URLs on docs.opendylan.org machine
    • / is main site, including /tour, /hacker-guide, etc.
    • /books/ for dpg and drm
    • /package/foo/ for packages
    • /downloads/ migrated over from opendylan.org
  • Repoint www.opendylan.org and opendylan.org's address records to my machine. It'll be easier for me to manage the playground and website in one place. Maybe abeaumont would like to turn down the current opendylan.org machine?
  • Run make linkcheck and correct the errors.
  • Deploy dpg changes automatically in update.sh
  • Get plantuml extension working again.
  • Link to History page from the All Documentation page.
  • Make the Playground accessible from the site again.
  • Add some redirects from old URLs. e.g. /documentation/library-reference/ to /library-reference/

Doc pages should have standard site menu

If you click the Documentation link in the top horizontal site menu and then click into one of the doc sections like Library Reference, there's no way to get back to the main site other than editing the URL or clicking the back button enough times. The menu should remain visible while reading the docs.

In a similar vein, the "Docs" link in "Docs ยป Dylan Library Reference" takes you to the Dylan Library Reference. I think it should take you to the main Documentation page.

Cheatsheet for tables

We should add a cheatsheet about tables and their usage.

  • How to make a top level table
  • How to make a table with the table() macro
  • Different types of tables

dependabot alerts

Just to log that I dismissed all the dependabot alerts relating to obsolete jquery versions; hopefully they will not re-appear now as the offending file has been removed from master and (AFAIK) dependabot only scans the master branch. ๐Ÿคž

Left nav overlaps main content

Moving this here from dylan-lang/opendylan#1289. May be related to #51 but I can't quite tell.

The History web page at normal 0% magnification has the left nav overlapping the main text:
overlapping

When I use Ctrl-+ four times it seems to switch to some other mode (mobile?) and the overlapping goes away:
non-overlapping

Notes from @pedro-w:

(should be on the https://github.com/dylan-lang/website project I suppose)
I see the website is using css from 'bootstrap-responsive' and the media queries change the style at the following widths

  • below 480px - a 'phone-like' style
  • up to 768px - left nav on top (OK)
  • up to 980px - left nav on left (OK)
  • above this - left nav overlaps (not OK)

I can look at this in a more detail to figure it out. Note the css file is quite old (bootstrap 2.3.1 is from 2013)

Based on modifying styles 'by hand' in the Developer tools, I think the navigation elements need to be in a div of class row-fluid rather than row. The source of this is in source/history/index.rst, line 3.
There may well be other instances of this, e.g. Documentation and Participate.

Short summary of features

@cgay suggested this on IRC, Rust website has a list of the language features. We could put something like that above the code carousel.

If you are okay with this please write the list of the features.

Deployment

Work with prom to get the site to auto-build & update when an update is pushed to Github.

Change "all news" button

I really don't like the "All news" button at the bottom of the index page, just looks ugly in that color / whatever.

โ€” Bruce on IRC

DRM links

There are a bunch of links to the DRM. We should either handle those with inter-sphinx or write our own extension to Sphinx so that we have syntax to make this easy.

can not build

~/lang/dylan/website master
make
sphinx-build -b html -d build/doctrees source build/html
Running Sphinx v1.3.1

Extension error:
Could not import extension dylandomain.dylandomain (exception: No module named 'dylandomain')
Makefile:29: recipe for target 'html' failed
make: *** [html] Error 1

The "edit source" widget doesn't work

For example, if you are on https://opendylan.org/getting-started-cli/hello-world.html the edit source widget (a pencil icon) links to https://github.com/dylan-lang/website/edit/master/source/getting-started-cli/hello-world.rst. It should link to https://github.com/dylan-lang/opendylan/edit/master/documentation/getting-started-cli/source/hello-world.rst

This is undoubtedly something that stems from the submodules and symlinks used to organize the website repo, and it might be fixed as a side-effect of integrating the website repo into opendylan repo. (Or integrating the documentation directory into the website repo.)

The /about/ pages aren't linked (in a useful way)

The entire /about/examples/ set of pages doesn't seem to be linked from anywhere. This is a nice overview of the language and should probably be linked from the Learning section of the documentation page at the very least.

Theme

Modify a theme to have a look at least similar the current site. I'm inclined to just change the top bar, not how the page is laid out. I'd also like to remove some of the links that are specific to documentation (next, prev, index).

I'm not inclined to add the Yahoo site search and instead put a Github ribbon in that corner.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.