If you've just started I2P, the Active: numbers on the left should start to grow over the next few minutes and you'll see a "shared clients" local destination listed on the left (if not, see below). Once those show up, you can:
We've bundled some software to let you run your own eepsite - a
Jetty instance listening on
http://localhost:7658/. Simply place your files in
the eepsite/docroot/ directory (or place any standard JSP/Servlet .war
files under eepsite/webapps, or standard CGI script under eepsite/cgi-bin)
and they'll show up. After starting up an eepsite tunnel pointing at it, your eepsite
will be visible to others.
Detailed instructions for starting your eepsite are on
your temporary eepsite page.
Be patient - I2P may be slow to start the first time as it searches for peers. If, after 30 minutes, your Active: connected/recent count has less than 10 connected peers, you should open port 8887 on your firewall for better connectivity. If you cannot see any eepsites at all (even www.i2p), be sure your browser proxy is set to localhost port 4444. You may also want to review the information on the I2P website, post up messages to the I2P discussion forum, or swing by #i2p or #i2p-chat on IRC at irc.freenode.net, irc.postman.i2p or irc.freshcoffee.i2p (they're linked together).
As a note, you can change this page by editing the file "docs/readme.html"