It would be nice to add some transitions and/or transforms to our themes. It will make them more modern and fun to use.

The implementation of steemitboard badges on the trollfell theme profile page, has out of date images, cached by steemitimages.

Instead of resizing using steemitimages like this...

https://steemitimages.com/50x60/http://steemitboard.com/@{steem_profile_username}/votes.png

Just use...

http://steemitboard.com/@{steem_profile_username}/votes.png

And resize using CSS. This will also give some flexibility in responsive design if done right.

Add @mention support to steem module using a function.

Apply this function to:

• Profile about section.
• Steem post body
• Comment body

We need to create generic classes and tag HTML elements in theme templates with them. This will enable easier theme and palette creation and maintenance.

To make this work, a set of common css classes and ids for use in templates for use in layout themes and colour schemes. We already have some stand html ids that are used. We should probably start documenting these in the wiki.

This job will require:

• Adding a pallete folder
• Adding a pallete\chocorange folder
• Adding a pallete option to config/json
• Loading the correct pallete during config parsing, similar to layout themes
• Create a few palletes to choose from
• Replace color styling from the layout themes

This module will interact with the bitshares api.

The module will accept parameters for:

• A static file containing the html for the campaign description.
• Name of the bitshares account to measure.
• Name of the bitshares token being measured.
• The goal the campaign wants to raise.

The module will then display:

• The description file specified.
• A progress bar.
• Donation link.

By default we were hiding post thumbnails in css and then using jquery to show them for posts that have them. This prevented the display of broken image thumbnails beside posts that don't have one.

This was working but something broke it, and now no thumbnails display ever.

This needs fixing before release of beta.

Global steem settings should include options for green, amber and red lists of users to display in comments and post listings.

Users in the red list should never show in comments, or in post listings.

Users in the amber list should show in comments, but not post listings if a Green list is set.

If a Green is set, only the users in it should show in post listings.

Or something along these lines. Maybe needs thinking about.

Probably depends on completion of #29.

Add option to store the config in EOS. Local config would then contain only reference to the EOS data. Editor would save changes to EOS.

Write a module that pulls the content of a steem blockchain to display three types of content. Allow themes to specify custom templates.

Profile

Get profile data for a specified user and display.

Post

Get post by specified post id. Turns the markdown into html if necessary, and displays the results in the content area.

Post listing

Get a post listing by tag or user.

Will require

• The steem javascript api library
• Possibly some javascript markdown parser

We have chosen an official theme naming convention of fictional place names from sci-fi, fantasy and mythology.

We need to rename 'simple', 'anton', 'dana' and 'henrik' themes to use names from the naming convention.

Any new 'official' themes should then be named according to the convention.

Suggested new names:

• 'simple' to be renamed 'metaverse' (in reference to Snow Crash)
• 'dana' to be renamed 'trollfell' (in reference to Katherine Langrish)
• 'anton' to be renamed 'fluxstate' (in reference to Shadowrun games)

• Create a code folder and move existing files into it. (@DanaVarahi or me)
• Create a sites folder and move miblodge\projectb files into it. (@DanaVarahi or me)
• Create a docs folder with a copy of blockpress, as a demo of the code working on github pages. Enable github pages for this repository. (@DanaVarahi or me)
• @hkjn to create a folder for his scripts.

This should be the first job done after initial beta download release.

Add some theme options in the config that supporting themes can use if they support those features. These features will remain when changing theme to another theme that supports them. Non supporting themes will simply ignore these settings.

These will initially include:

• Banner image. Defined by url or file path.
• Site image. Defined by url or file path.

Adding them will include:

• Adding the default settings to config.json
• Adding support for these features to at least one theme.

Show steemit board badges to steem profile page.

Badge selection should be configurable.

Create post listings for tags.

Add tags list to post page, linking to the tag post listing page.

Use the CryptoCompare API to generate a module with the top 50 or so coins/tokens and display in a table with a number of columns such as 'coin', 'price', 'marketcap' and 'liquidity'.

Should also cross reference each coin against its tag in steem to see how many topics, comments and highest reward, using the steem api. This will require columns for 'topics', 'comments' and 'highest reward'.

Put all the data in a jQuery DataTable. Allow the table to be ordered by any column.

Display post comments under post, if template has steem_post_comments id in a tag.

Link to comment author profiles.

To make it easier to theme the menu for flex wrap and other styling issues, change over to using divs rather than horizontal lists.

• Me to change init.js to load the menu
• @DanaVarahi to update themes to work with updated html

Look for a custom_config.json first and only load the default config.json if it isn't found. That way the config file for a particular site won't be overwritten when upgrading to latest code versions.

Rather than hardcoding a site tagline in the theme template, it would be good to be able to define it in the config.

This will load into an optional area of the theme template, taglineArea, but only in themes that choose to support it. In other words it will be an optional theme feature.

The wiki says a tutorial to create a custom config file will be written once issue #3 has been closed. Well that issue is now closed so it is time to write that tutorial.

Use Ethereum javascript API to create a module for ethereum.

Perhaps a donation tool with total raised and target?

At the moment a users posts, as viewed on either the post listing page, or their profile page, excludes resteems. It would be good if it could optionally include them.

Social menu icons are broken at the moment.

It would also be good if palettes could customise the hue of social media icons so that it fits with the colour scheme.

Make sure all the themes have responsive design features enabled and functional.

• metaverse theme
• trollfell theme
• fluxstate theme
• amber theme

Blockpress needs improvement to its themes to fully demonstrate customisation possibilities.

• Demonstrate embedded jQuery and js
• Sidebar menu
• Upsidedown theme

Hello, i just checked your lovely project and i discovered you have some sections missing out like FAQ, about us, contact us and privacy policy. If you dont mind i will like to write that for you.
My email: [email protected]

Once job #3 has been done:

• Package the site up in zip and tar.gz downloads.
• Add instructions to the wiki to download, install and configure

When a user scrolls to the end of any post listing, we should automatically load more.

I think perhaps we can do away with post counts, and just keep loading more until no more are visible on the page. When user scrolls to end, more load. Maybe we can always load 10 at a time. Something like that.

Header image in trollfell theme is currently embedded in the template. We want it to load from the config using js instead.

If first content to load is not specified, site should load the first item in the menu. This feature is broken.

Add documentation on theme creation to the wiki. Include,

• Folder and file placement
• Required areas of the html template
• Optional areas of the html template
• Steem module templates
• Special links to module content loading, from links outside the #menuArea.

It would be good to have a separate javascript file instead of using script tags in theme.html files.

Currently, the box-shadow is defined in the palettes. This creates a compatibility issue with themes that do not want to use box-shadow.

We need generic box-shadow classes that can be applied to elements in HTML templates instead.

The urls of the social media links currently hardcoded into some themes should be defined in the config.json.

This task should include:

• Adding the default values to the config.json. These should be the blockpress links.
• Adding support to simple theme.
• Adding support to anton theme.
• Adding support to dana theme.
• Adding support to hkjn theme.
• Also add support for link_url
• Also add support for email

The steemjs library has a deprecated default url for the steem API, which is no longer working.

Ensure all calls to the steem API are using the correct URL by implicitly setting it.

Theme templates and css files need specific names instead of 'template.html' and 'style.css'

Make hashtags found in user profile description into links.

If theme supports showing users posts on profile page, the hashtags should update this listing to show just the posts with the selected tag. If not, the tag should link to the normal post listing page.

Support permlinking.

This will come in two parts:

Part one

Load content based on query string:

• ?p=module\arg1\arg2\arg3\etc

Part two

• When a module updates the content, it should javascript to update the history object using pushState to add the correct permlink as the url

Metadata information for posts doesn't display very nice. Content area headers are too small. Both need readjustment.

Allow multiple BlockPress sites to run from a single installation, by allowing multiple domain specific config files. Suggested order of preference for loading config for https://example.domain.name:

• example.domain.name.config.json
• example.domain.config.json
• example.config.json
• local_config.json
• config.json <--- the default site settings when no user specified settings are defined.

There is a bug in responsive design for the simple theme. The flex-wrap property isn't working.

Lets make sure that our code is accessible for people with disabilities.

Probably need to turn modules into javascript object prototypes with commonly named functions to stop the href loading error that occasionally stops the menu from loading.

Maybe also need to ensure modules have loaded before creating the menu.

Call steem content functions directly in templates rather than using the steem_load function with an encoded json object as a parameter.

This will make it easier for theme creators to use.

Module should create two panel inside the contentArea, on the left a form, on the right a display of the generated config file.

• The form should contain all the necessary options contained in a typical config file.
• Changing any element in the form should automatically update the content.
• The site config should be saved in a global.
• A preview button should alter the site to use the new config settings.
• A 'Restore' button should always be added to the preview, that reloads the saved site config.

Add a section to the config.json that defines the first module to load. This can't be the link module, but rather a module that pulls in content.

Add an option to the profile template, enabled in default, to show the users recent posts on their profile page.

Loading blockpress when not in the webroot fails for three reasons, all of which should be easy enough to fix.

• Theme template fails to load because of url relative to root, and not blockpress folder.
• Theme css fails to load because of url relative to root, and not blockpress folder.
• Palette css fails to load because of url relative to root, and not blockpress folder.

Other template files specific to modules may also be affected. That too would need checking.

Palettes across Blockpress file system are misspelled 'palletes'. We need to correct that.