recurse-community-portfolio
recurse-community-portfolio copied to clipboard
jasonaowen
Discover all the things Recursers have built!
Make it easier for new contributors to learn how to contribute by expanding the documentation, including by adding detail around database migrations (particularly in light of #103), the HTML templating...
Instead of bare IDs, user and project pages should also have [slugs](https://en.wikipedia.org/wiki/Clean_URL#Slug) that include the user or project name.
Following the installation instructions to set up a developer instance leaves the developer with a mostly empty database, which makes it hard to work on a number of issues -...
@j9peters A user with private profile visibility cannot view their own name in project listings when they are logged in. "Anonymous" is shown instead. In the following code from DisplayAuthor.java,...
Add the [Twitter and Facebook meta tags](https://css-tricks.com/essential-meta-tags-social-media/) that allow shared URLs to be better displayed on those platforms. This is particularly important for the home page, projects, and users; minorly...
Allow users to upload images, or enter URLs which the application then fetches, and store them "locally". On Heroku, that would probably mean in S3; if we switch to a...
Allow tags to have some kind of community wiki description, where anyone can edit a tag's description. See, for example, Stack Overflow.
The edit button is very near to the visibility status, which makes it look like that's the only thing the edit button would affect.  Occurs on both the author...
Markdown links without a protocol, like `[Portfolio](github.com/jasonaowen/recurse-community-portfolio/issues/new)`, do not render as a link. Figure out why and fix it, maybe by defaulting to `https://`.
Add a page that includes the licenses of all of our dependencies (as managed by gradle and, someday, npm - #70). Those licenses should be automatically gathered and the page(s)...